6

I'm not 100% sure about this, but I think that the documentation feature is available only for the mothership website. I randomly clicked on a few websites in here and none of them have this feature. My bet (read hope) is that when this feature gets out of beta it will be available for some websites in the SE network. But to answer your question, no, nobody ...


6

Do you find it complex too? No, I think the documentation is very clear, but you should not read it from the beginning to the end at one time, just use it as a handbook. Do you think a newbie can understand it well? Yes. In case you are interested in "How the plugins work?" you can find the answer in the documentation and you can understand it. ...


3

Sorry, have been away for a full month :D The Documentation site is a separate site within the StackExchange network and is not only a sub-site for StackOverflow (although it is located there). It can facilitate documentation on all kinds of topics (as you can see) from big names like PHP/.NET/SQL/Java to "never-heard-of-it" stuff like Jekyll/lodash/zeromq. ...


3

The best thing would be to either create an issue on github https://github.com/magento/devdocs/issues and then maybe try to fix it yourself. Looking at the source the footer is actually commented out <?php include(__ROOT__ . 'footer.php'); ?> but the actual page https://github.com/magento/devdocs/blob/develop/guides/m1x/api/soap/catalog/...


2

http://devdocs.magento.com/guides/m1x/magefordev/mage-for-dev-1.html


2

We're working on some replacement content, but there will not be a 1:1 replacement. In the future the Magento 2 docs will be a good replacement.


2

I wish I could but I haven't committed to the Area 51 proposal :( Plus when I click the suggested link I get a 404 Couldn't find the related Area 51 proposal using the search. Anyway, yes that's a great idea I 100% approve even if I can't support your tag request.


1

In my opinion purpose of edit should be to make post more easier to read and understand, without harming the post. After edit the intent of post should be same as before. One should not edit any post to add his/her comment or answer to the post. To make post more easier you can correct it grammatically, also if added code is having very bad formatting you ...


1

From my experience there doesn't seem to be a specific format and its up to the judgment of the user. If the edit applies to the original post being edited than I believe it makes sense to clearly state the edit and a brief explanation as too why. This way people coming to the site/question can more easily see the relevant information and they won't need to ...


1

Please check the page now. I fixed the "Edit this page on GitHub" link to go to the correct file. I also commented out the footer.


Only top voted, non community-wiki answers of a minimum length are eligible