-
-
Notifications
You must be signed in to change notification settings - Fork 2k
docs: remove express v2 #1740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: remove express v2 #1740
Conversation
✅ Deploy Preview for expressjscom-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
wesleytodd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good, but as we discussed in the issue, it would be nice to have some docs on how to access them in case someone is looking.
|
Do you still require another reviewer? Or are you good to go? |
|
@chrisdel101 I am making some changes to set up the redirects |
d948c14 to
cf22434
Compare
|
I have applied the redirects on the pages that were from Express v2 and modified the 2x branch so that only version 2 is there. Additionally, in the README, I included some instructions on how to preview the content. By the way, @expressjs/express-tc can you add protection to the 2x branch so that it can only be read and not modified? |
chrisdel101
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
The only thing is whether we want the links to 2x branch left in on version support page, since it might be hard to find the 2x branch, but I assume you removed those to discourage people from even going there.
cf22434 to
7e5cb84
Compare
|
For a big PR like this, prefer to push regular commits and then squash at merge. That way during review it's simpler to know what has changed since last review. Based on your comment @bjohansebas the latest force push update was the redirects, but it's hard to tell with this many changed files |
jonchurch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't actually get a true 301 out of Jekyll and Github pages here (or any static site builder) for what it's worth. Will be a 200 to load the page from CDN then a meta redir using JS (or the meta-http tag) on the loaded page itself.
Im okay with that for now, since we are also removing the Nav link from the site itself.
To fix that we'd need a page rule at Cloudflare, which requires additional config that Im not really convinced we want to maintain there.
|
Yep, it's not the redirection I would like to have, but it's the only one allowed by GitHub Pages and Jekyll. |

closes #1556