4 ms·
I would like to see a “framework of opinions” somewhere. 0 actual software, just documentation for standard JS and browser APIs organized in a way resembling fr
by graypegg 2y ago
I would like to see a “framework of opinions” somewhere. 0 actual software, just documentation for standard JS and browser APIs organized in a way resembling framework documentation.
The current style of web platform documentation tends to resemble a big list of objects, or the most basic and slowest introduction to web development possible.
Something in-between, with chapters like “templating” or “data fetching” that focused on some opinionated but framework less structure, would be nice.
- davidmurdoch 2y agoThat would be incredibly interesting. I'm sure it would be one of the most polarizing "frameworks" though.
- throwaway2037 2y agoThis is a cool idea. If I read it correctly, are you suggesting that MDN create a parallel doc tree, like "web apps", that introduces HTML/CSS/JS with the specific aim of building vanilla web apps? I am sure that it would be popular.
- graypegg 2y agoYeah! Though a similar tone to framework documentation, so it would have to declare some opinions on things (Templating must use the <template> element and custom elements, data fetching outside of the initial load must use fetch(), etc) and the surrounding glue code you have to use to compose all of these APIs together is described to you. (rather than just describing the APIs, like most of MDN's docs) I think there's easily enough API surface area to cover every part of a front-end web application without any dependencies.