chore(docs): switch documentation deployment target#9905
Conversation
grega
changed the title
grega
changed the title
github-actions
Bot
added
PR: chore
|
@maribethb has the context here @lizschwab, so feel free to pass on the review if you prefer! |
grega
force-pushed
the
chore/switch-docs-deployment-target
branch
from
68f5492 to
f4b45f9
Compare
github-actions
Bot
added
PR: chore
|
|
||
| # Strip .md/.mdx extensions if someone lands on the raw filename | ||
| /reference/*.md /reference/:splat 302 | ||
| /reference/*.mdx /reference/:splat 302 |
There was a problem hiding this comment.
I used 302 throughout as I'm generally hesitant about applying truly permanent redirects with 301 (not that all user-agents necessarily stick to the spec here, though some will certainly cache it with no expiry).
That said, the .md and .mdx redirects feel in particular like a 301 would be fine.
There was a problem hiding this comment.
I think 301 is probably fine, but I'm happy to make sure everything is set up correctly before we start claiming that our redirects are permanent!
|
|
||
| # Strip .md/.mdx extensions if someone lands on the raw filename | ||
| /reference/*.md /reference/:splat 302 | ||
| /reference/*.mdx /reference/:splat 302 |
There was a problem hiding this comment.
I think 301 is probably fine, but I'm happy to make sure everything is set up correctly before we start claiming that our redirects are permanent!
3 participants
The basics
The details
Proposed Changes
Switches documentation deployment target from GitHub Pages to Cloudflare Pages.
Preview build: https://blockly-docs.pages.dev
Reason for Changes
Ensures that the existing GH Pages workflow can continue to run without needing modification (ie. without needing to figure out how to deploy both sets of assets to GH Pages without overwriting each other).
Prior to running this workflow for the first time, two secrets will need adding to this repository:
CLOUDFLARE_ACCOUNT_IDCLOUDFLARE_API_TOKENI can provide values for each.