This wasn't a problem for a long time, because frameworks (and therefore guides) did only inherit from either the Browser JS documentation OR the Node.js documentation. (e.g. vue would inherit from javascript - express would inherit from node).
But with all the meta/fullstack frameworks being created, we need a better solution. Frameworks like nextjs should be able to inherit hand-picked parts from javascript, and parts from node. And maybe other runtimes in the future as well?
Solution Brainstorm
The sky is the limit. Maybe we need to combine node and browser javascript and take it from there? We definitely need some brainstorming on this.
(Whatever we do, we definitely need to make sure that pages do not 404 afterwards, but are properly redirected.)
Problem Statement
Right now, we have a lot of different platforms (often, but not always the platform relates directly to languages):
Some of those platforms have dedicated guides. We created those for frameworks (and sometimes other libraries):
With JavaScript we keep running into difficulties. For JS, two different platforms have been created:
This wasn't a problem for a long time, because frameworks (and therefore guides) did only inherit from either the Browser JS documentation OR the Node.js documentation. (e.g.
vue
would inherit fromjavascript
-express
would inherit fromnode
).But with all the meta/fullstack frameworks being created, we need a better solution. Frameworks like
nextjs
should be able to inherit hand-picked parts fromjavascript
, and parts fromnode
. And maybe other runtimes in the future as well?Solution Brainstorm
The sky is the limit. Maybe we need to combine node and browser javascript and take it from there? We definitely need some brainstorming on this.
(Whatever we do, we definitely need to make sure that pages do not 404 afterwards, but are properly redirected.)