Thread:Project:Current issues/Adding a dev namespace for "Data and developer hub" articles/reply (6)

I've just been having a play with the proposed skin, and to be honest it leaves me a bit lost.
 * I couldn't find any way to get to a discussion page.
 * I eventually managed to find the edit/view history links, which are hidden away. Not sure I like the fact that editing/involvement is being discouraged in this way.
 * A lot of the features I am used to (edit section, add to watchlist, save as PDF, etc.) I couldn't find at all - I assume they have simply been removed to make things 'cleaner'.

Having had a play with the skin, my feeling is that there is possibly a third approach, which might satisfy the two different camps (the people who basically want a static website that is easy to use and navigate, aimed at third-party consumers of the API vs. the people who want editable online documentation, and for it all to be in one place).

My revised suggestion is the same as what I wrote in my previous post, except that the whole skin business is abandoned - the pages are part of mediawiki.org, and remain in the site skin in the same manner as all other pages on the site. Then, in addition to this, a separate site is set up, using a variant of the new skin, which pulls it data from the API namespace of MediaWiki and presents it in a static format that is very friendly to third-party consumers. The new skin would be broadly like the prototype, with a couple of changes:
 * There is no functionality related to editing, logging in, etc. except insomuch as is appropriate in relation to the next point
 * There is a clear notice (possibly as part of the header, or possibly as part of the slide-out menu) saying this content comes from mediawiki.org - "to edit, discuss or otherwise contribute to it click here".

Obviously, there are details to be worked-out, but what do you think of this approach?