Add links to API documentation from "Developers" and "Learn & Discover"

We add the links from Developers only for now, will then work on a more
elaborated page for documentation that will cover also cog, libwpe and
the FDO backend, but for now this should be good enough.

about/index.md

@@ -195,6 +195,7 @@ answer these and more questions.
 
 * [Supported Hardware](/about/supported-hardware.html)
 * [Architecture](/about/architecture.html)
+* [API Documentation](/developers/#api-documentation)
 * [Release Schedule](/release/schedule)
 * [Frequently Asked Questions](/about/faq.html)
 

developers/index.md

@@ -31,6 +31,23 @@ h2 {
 
 <div>
 
+## [API Documentation](#)
+
+API documentation for the **latest stable release** is available here:
+
+<ul class="arrows">
+<li><a href="https://wpewebkit.org/reference/stable/wpe-webkit-2.0/">WPEWebKit 2.0 API documentation</a></li>
+<li><a href="https://wpewebkit.org/reference/stable/wpe-javascriptcore-2.0/">WPEJavaScriptCore 2.0 API documentation</a></li>
+<li><a href="https://wpewebkit.org/reference/stable/wpe-web-extension-2.0/">WPEWebExtension 2.0 API documentation</a></li>
+<li><a href="https://wpewebkit.org/reference/stable/wpe-webkit-1.1/">WPEWebKit 1.1 API documentation (deprecated)</a></li>
+<li><a href="https://wpewebkit.org/reference/stable/wpe-javascriptcore-1.1/">WPEJavaScriptCore 1.1 API documentation (deprecated)</a></li>
+<li><a href="https://wpewebkit.org/reference/stable/wpe-web-extension-1.1/">WPEWebExtension 1.1 API documentation (deprecated)</a></li>
+</ul>
+
+</div>
+
+<div class="dotsep">
+
 ## [WPE Builds](/about/builds.html)
 
 While there are several simple ways for developers to experiment with and explore WPE, none are tuned for performance. Generally, shipping products for embedded systems are performance-tuned custom builds. To make this easier, there is also [meta-webkit](https://github.com/Igalia/meta-webkit), which provides build recipes, WebKit based runtimes, and browsers for use with OpenEmbedded and/or Yocto.