This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Whilst we don't want to try to comprehensively cover all server-side technologies, it would be foolish to ignore them completely. We should therefore have a series of quick pages to explain the basics of server-side languages, which quickly point to external resources for more detail.
Could the same be said for frameworks and libraries? Primarily thinking towards JavaScript here. They are really useful to developers, but trying to cover them would probably cause the same mess server-side languages would.
Yeah, probably. Since JS libraries are part of the client-side, I would be happy for them to be included in as in depth a fashion as people are prepared to spend the time writing up, but since they already have dedicated communities and powerful doc resources, they are of a lesser priority than the pure open standards.
I'm reducing the priority on this one since we aren't really targeting these so it isn't a high priority. There is a page up but the actual language pages haven't been made so we need to figure out what should go in there besides links out to the languages homepages. I am thinking we should (using PHP as an example): 1) Link to the homepage of the project. 2) Link to known good and trusted resources for more information about the language. 3) Link to known support areas for the languages. (##php in IRC for example.) Any thoughts on that?
Reverting this bug's platform to All, as experience happens on all platforms.
Page is in place here [1]. Still needs work, but the basics are there. [1] http://docs.webplatform.org/wiki/server-side_languages