Skip to content

Commit 232cde2

Browse files
committed
fix(website): relabel install strip "Published to" → "Available on"
The homepage logos strip is filtered to push-mechanism channels, which includes Flatpak and Obsidian. Those are not published to a registry — the `.flatpak` and `.zip` bundles are built in CI and attached to a GitHub release, then installed from the file. So "Published to Flatpak/Obsidian" was inaccurate. "Available on" is correct for every channel in the strip (npm, PyPI, GitHub Releases, the Visual Studio Marketplace, Open VSX, Flatpak, Obsidian) regardless of whether mdsmith pushes to a registry or bundles into a release. Update the website/README.md reference to the strip to match.
1 parent 60104b4 commit 232cde2

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

website/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ release-channel docs, gated against drift in CI:
105105
`hugo.Data.channels` (the generated
106106
`website/data/channels.yaml`). It renders every channel
107107
with platform-tag filter chips.
108-
- **"Published to" strip** — the release-channel docs
108+
- **"Available on" strip** — the release-channel docs
109109
`../docs/development/release-channels/*.md`. Each
110110
carries a canonical `channelurl:` and an ordering
111111
`weight:`; `logos-strip.html` ranges the synced

website/layouts/partials/logos-strip.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<div class="logos">
22
<div class="container">
33
<div class="logos-strip">
4-
<span class="logos-label">Published to</span>
4+
<span class="logos-label">Available on</span>
55
{{- /* Sourced from the generated install data
66
(website/data/channels.yaml, produced by
77
`mdsmith-release sync-channels` from

0 commit comments

Comments
 (0)