docs: feature the 1.0 stable release across landing, docs, and social cards#134
Merged
Conversation
… cards Give the 1.0 milestone proper prominence on the marketing surface. Landing (landing/index.html): - Hero: 'selectools 1.0 — Production Stable' badge + '1.0: the public API is frozen and stable' subline - softwareVersion JSON-LD 0.27.2 -> 1.0.0; status bar + footer v0.27.2 -> v1.0.0 - Enterprise exhibits: dropped Python 3.9 from the version stack (now 3.10-3.13); stability markers refreshed to current counts (@stable 250, @beta 233, 485-symbol API) and caption 'Stable at 1.0' (was 'v1.0 on the horizon') - 'Is Selectools production-ready?' FAQ (visible + JSON-LD) now leads with the 1.0 frozen/stable guarantee - Examples count 111 -> 115 (status bar, button, footer) Docs/README: - docs/index.md: '1.0 — stable' success admonition - README: 1.0 stable callout under the tagline Social cards: - og-image.svg + og-card.html: 'v1.0 STABLE' badge (also fixed · -> · so the SVG is valid XML) All current-state version/status/count claims now reflect 1.0; historical 'What's New'/changelog blocks left as-is.
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.
Gives the 1.0 milestone proper prominence across the marketing surface (it had only landed in the CHANGELOG).
Landing (
landing/index.html)softwareVersionJSON-LD0.27.2→1.0.0; status bar + footerv0.27.2→v1.0.0@stable250,@beta233, 485-symbol API) with caption "Stable at 1.0" (was "v1.0 on the horizon")111→115(3 spots)Docs / README
docs/index.md: a "1.0 — stable" success admonition under the taglineREADME.md: a 1.0 stable callout under the tagline (complements the "What's New in v1.0" section)Social cards
og-image.svg+og-card.html: a "v1.0 · STABLE" badge (and fixed·→·so the SVG is valid XML)Current-state version/status/count claims now all reflect 1.0; historical "What's New"/changelog blocks were left as-is. Docs/static only — no source changes.