You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, you can search on Google for a Node.js API and get extremely outdated documentation with no path to reach the current docs. I just searched "node fs readfile" on Google to get the docs page, and the top result is Node.js v6 docs, which somehow do have more recent docs in the dropdown but not the most recent docs - the latest available are v9 docs.
I think having the historical docs is extremely important, but IMO this is an extremely suboptimal experience that can very easily confuse users and be deeply frustrating.
Ideally, we'd:
Have all links in search engines be the latest docs
Allow slugs to redirect to specific versions, but not expose those to search engines
Allow access to all historical docs from latest
The text was updated successfully, but these errors were encountered:
The issue is that API docs have no sitemap.xml and their pages are not correctly indexed. I'm not sure this should be under this repository or node/node since that's where the API docs live.
Ideally, we'd:
I'm not sure where you're suggesting these things to be added? 🤔
Enter your suggestions in details:
Currently, you can search on Google for a Node.js API and get extremely outdated documentation with no path to reach the current docs. I just searched "node fs readfile" on Google to get the docs page, and the top result is Node.js v6 docs, which somehow do have more recent docs in the dropdown but not the most recent docs - the latest available are v9 docs.
I think having the historical docs is extremely important, but IMO this is an extremely suboptimal experience that can very easily confuse users and be deeply frustrating.
Ideally, we'd:
The text was updated successfully, but these errors were encountered: