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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: