Yes, I agree with addressing back-end tech as a necessary part of web
development, and showing how it interacts with front-end tech, as
appropriate, especially in the Learning area. (Note that a certain other
popular site for learning web technology [**schools] has a whole section
on "server side" technology.)
Creating docs for technologies that already have docs, and communities
that support them, doesn't seem like an effective use of the energy of
this community. (Folks, please speak up if I'm wrong and there is
pent-up interest in doing this.)
We can certainly provide links to existing documentation for back-end
languages, like:
*
http://php.net/docs.php
*
https://docs.python.org/3/
*
https://dev.mysql.com/doc/
On 4/6/16 20:50, Eric Shepherd wrote:
> This is a discussion we've had a few times in recent years, and
> generally we've come to a consensus that while we might offer brief
> "here's the kind of thing you can do on the back-end" type articles, or
> demonstrating bits of back-end code in pursuit of demonstrating how
> front-end features work, actually providing in-depth coverage of the
> back-end languages, databases, and so forth is outside the scope of
> MDN's coverage.
>
> ------------------------------------------------------------------------
> *From:* Chaitanya Bhardwaj
> *Sent:* Wednesday, Apr 6, 2016 1:08:15 PM EDT
> *To:*
dev...@lists.mozilla.org
> *Subject:* [dev-mdc] Back-end Language reference and guide.
>
>> MDN has already made a good approach towards references for front-end
>> languages like HTML, CSS and Javascript. But web development does not ends
>> with these languages. As a result, back-end languages such as MySQL and PHP
>> should also be encouraged. Moreover, there are many users who are willing
>> MDN to support back-end languages too just like front-end, in their guide
>> and reference. Please take this topic into consideration.
--
Janet Swisher <mailto:
jREMOVE...@mozilla.com>
Mozilla Developer Network <
https://developer.mozilla.org>
MDN Community Manager