Skip to content

Conversation

@bjohansebas
Copy link
Member

closes #1556

@netlify
Copy link

netlify bot commented Jan 27, 2025

Deploy Preview for expressjscom-preview ready!

Name Link
🔨 Latest commit 7e5cb84
🔍 Latest deploy log https://app.netlify.com/sites/expressjscom-preview/deploys/679a48297299f60008f85d69
😎 Deploy Preview https://deploy-preview-1740--expressjscom-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@bjohansebas bjohansebas requested review from a team January 27, 2025 21:05
Copy link
Member

@wesleytodd wesleytodd left a 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.

@chrisdel101
Copy link
Contributor

Do you still require another reviewer? Or are you good to go?

@bjohansebas
Copy link
Member Author

@chrisdel101 I am making some changes to set up the redirects

@bjohansebas
Copy link
Member Author

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?

Copy link
Contributor

@chrisdel101 chrisdel101 left a 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.

@jonchurch
Copy link
Member

jonchurch commented Jan 29, 2025

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

Copy link
Member

@jonchurch jonchurch left a 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.

@jonchurch
Copy link
Member

jonchurch commented Jan 29, 2025

I've enabled branch protections on the 2x branch (via rulesets, for anyone in the future looking for this in github settings)
image

@bjohansebas
Copy link
Member Author

Yep, it's not the redirection I would like to have, but it's the only one allowed by GitHub Pages and Jekyll.

@bjohansebas bjohansebas merged commit 2b3c9f1 into gh-pages Jan 29, 2025
8 checks passed
@bjohansebas bjohansebas deleted the remove-express-v2 branch January 29, 2025 17:43
chrisdel101 pushed a commit to chrisdel101/expressjs.com that referenced this pull request Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove express v2 docs

5 participants