feat(site): show the spec version each adopter feed declares - #44
Merged
Conversation
The directory said nothing about which version of the spec a feed speaks, which is exactly what someone deciding whether to consume it wants to know before subscribing. The daily health check already measures it, so the card now carries an "OTE 0.3" pill next to the feed preview link. The version is joined into the cards from docs/data/feed-health.json by feed URL, not written back into adopters.json: that registry is hand-curated and edited by the registration PRs, and a bot writing a derived field into it every morning would collide with its only intended author. If feed-health.json is missing the cards render as before, without badges. Wording is deliberately affirmative — every published version stays supported and feeds are validated against the one they declare, so the badge states what a feed speaks, not that it is behind. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Follow-up to #43: the health check now knows which spec version every feed declares, and the directory shows it.
Each adopter card gets an
OTE 0.3pill next to Preview feed →, with a tooltip explaining that every published version stays supported and feeds are validated against the one they declare. Affirmative on purpose: the badge says what a feed speaks, not that it is behind.The version is not written into
adopters.json. That registry is hand-curated and its intended author is the registration PR; a daily bot writing a derived field into it would collide with that and noise up its diffs. The site joinsadopters.jsonwithdata/feed-health.jsonby feed URL at render time instead. If the health file is missing, cards render exactly as before, without badges.Verified in the browser against the local site: Community Builders shows
OTE 0.3, eventos.wikiOTE 0.4; consumer and supporter cards are unchanged.npm run validatepasses.🤖 Generated with Claude Code