Change Details

After agreeing on the requirements of the Developer Hub infrastructure, we need to agree on the technology selection to fulfill these requirements. Current proposal After several discussions during the #MWDS15, it looks like we have agreement on the basic technology selections: * The landing page of the Developer Hub, the basic content structure, showcases, tutorials, and other types of "manual writing" docs would be all powered by MediaWiki, specifically in an own namespace with an own skin in mediawiki.org. * The API reference documentation from each software component would be provided by the appropriate tool for each component. At least in this first phase, we would not seek any uniformity of tools, and neither we would require API docs to be imported to wiki pages. Links from the hub to the api docs and vice versa should make everything easy to find. Having a common search covering all these spaces would be nice, but left for a later stage, or for the personal initiative of someone willing to work specifically in this problem.

After agreeing on the requirements of the Developer Hub infrastructure, we need to agree on the technology selection to fulfill these requirements. Current proposal After several discussions during the #MWDS15, it looks like we have agreement on the basic technology selections: * The landing page of the Developer Hub, the basic content structure, showcases, tutorials, and other types of "manual writing" docs would be all powered by MediaWiki, specifically in an own namespace with an own skin in mediawiki.org. * The API reference documentation from each software component would be provided by the appropriate tool for each component. At least in this first phase, we would not seek any uniformity of tools, and neither we would require API docs to be imported to wiki pages. Links from the hub to the api docs and vice versa should make everything easy to find. Having a common search covering all these spaces would be nice, but left for a later stage, or for the personal initiative of someone willing to work specifically in this problem. .

After agreeing on the requirements of the Developer Hub infrastructure, we need to agree on the technology selection to fulfill these requirements. Current proposal After several discussions during the #MWDS15, it looks like we have agreement on the basic technology selections: * The landing page of the Developer Hub, the basic content structure, showcases, tutorials, and other types of "manual writing" docs would be all powered by MediaWiki, specifically in an own namespace with an own skin in mediawiki.org. * The API reference documentation from each software component would be provided by the appropriate tool for each component. At least in this first phase, we would not seek any uniformity of tools, and neither we would require API docs to be imported to wiki pages. Links from the hub to the api docs and vice versa should make everything easy to find. Having a common search covering all these spaces would be nice, but left for a later stage, or for the personal initiative of someone willing to work specifically in this problem. .