feat: fetch blog mappings from live admin API with static fallback#256
Open
Hale730 wants to merge 2 commits into
Open
feat: fetch blog mappings from live admin API with static fallback#256Hale730 wants to merge 2 commits into
Hale730 wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the blog loader to fetch pillar/tag/author mappings from the
research-manage-content admin tool's API instead of the static
blog-mappings.tsfile.Why
The static
blog-mappings.tsfile requires a code change + PR every timea new post needs to be categorized. The admin tool has a live D1 database
where mappings can be updated via UI, with AI auto-categorization on new posts.
How
At build time,
blog.tsnow tries to fetch from:https://research-manage-blog.pcx-team.workers.dev/api/blog/mappingsThe endpoint is protected by Cloudflare Access. Two env vars are required:
CF_ACCESS_CLIENT_IDCF_ACCESS_CLIENT_SECRETIf either var is not set, or the request fails for any reason, it falls back
to the existing static
blog-mappings.tsautomatically — so contributorswithout credentials can still build the site normally.
A
.env.examplehas been added documenting the required vars.What I deliberately didn't do
This PR doesn't remove
blog-mappings.ts— it stays as the fallback.It can be cleaned up later once the admin tool is fully deployed and stable.
Dependencies
The admin tool MRs need to be merged and deployed before the API path is live.
Until then, all builds will use the static fallback.