Deploy the v5 docs somewhere?
See original GitHub issueCurrently the following documentation links are available in the readme:
Documentation
I think it would be a great thing to have the v5 docs somewhere as well, even though it is still in beta. Currently, unless I am missing something, the only way to read the v5 docs is to:
git clone
npm install
npm run docs
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
react-router/v5.md at main - GitHub
This document is a comprehensive guide on how to upgrade your v4/5 app to v6 while hopefully being able to ship as often...
Read more >Deploying to remote servers with AppVeyor Deployment Agent
AppVeyor Deployment Agent (Deployment Agent) is a service running on remote server and helping to deploy select artifact as IIS website or Windows ......
Read more >Preview & Hosting - Gatsby
Documentation How-to Guides Docs. Preview & Hosting. Deploy and host your Gatsby site. Set up content preview using Gatsby Cloud.
Read more >The Transition Guide - DocBook V5.0
It describes differences between DocBook V4.x and V5.0 and provides some suggestions about how to edit and process DocBook V5.0 documents.
Read more >Distribution and Reproducibility - Snakemake - Read the Docs
Workflows set up in above structure can be easily used and combined via the Snakemake module system. Such deployment can even be automated...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah I want to keep v4 docs somewhere but currently there is no good way. @janmeier can we publish docs to another subdomain like
v4.squelizejs.com
?@snowyfox - You are very right!! I think this is very important to be fixed asap. You should open a new issue, can you do that? And mention this one?