Skip to content

Move the website deployment to another platform #1851

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

Open
bjohansebas opened this issue Mar 30, 2025 · 0 comments
Open

Move the website deployment to another platform #1851

bjohansebas opened this issue Mar 30, 2025 · 0 comments

Comments

@bjohansebas
Copy link
Member

As we continue improving the way we present our content and making changes—adding or removing entire pages—it would be useful to apply proper redirects for pages that have been removed. Currently, redirects are handled inefficiently, as they are performed by the page itself after it has already loaded, rather than being true redirects.

We could set up redirects through Cloudflare by adding rules, but the documentation team does not have access to that, and there is already an expressed interest in not maintaining those rules there (see #1740 (review)).

I propose that we move to another deployment platform. We could request this from the foundation, as other projects like Webpack and Node.js do, or migrate to Netlify, which is already linked to the repository.

Additionally, this would be important for the website redesign, whether we stick with Jekyll or migrate. While Jekyll does not support it, other documentation generators allow dynamic OG images (see #1564). This is a plus for showcasing the modern Express website on social media. With GitHub Pages, this wouldn't be possible since those images are generated on the server side.

cc: @expressjs/docs-wg @expressjs/express-tc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant