Skip to content

Downloads: restore the archive links, fold archived releases to the bottom - #900

Merged
wu-sheng merged 2 commits into
masterfrom
fix/downloads-archive-links
Aug 16, 2026
Merged

Downloads: restore the archive links, fold archived releases to the bottom#900
wu-sheng merged 2 commits into
masterfrom
fix/downloads-archive-links

Conversation

@wu-sheng

@wu-sheng wu-sheng commented Aug 16, 2026

Copy link
Copy Markdown
Member

Follow-up to #899, covering two things on the downloads page.

1. Restore the archive links the redesign dropped

The Archived Releases section did once have content. #431 (Apr 2022) added - type: Archive to releases.yml purely so the section got a nav chip — it deliberately had no list:, and the real content was a hardcoded block in downloads-block.html:

Older releases are not recommended for new users, because they are not maintained, but you still can find them(source codes and binaries) if you have specific reasons.

Find all SkyWalking releases in the Archive repository.

Archive incubating repository hosts older releases when SkyWalking was an incubator project.

The redesign (#844, May 2026) rewrote that shortcode and dropped the block, leaving the by-then-renamed Archived Releases entry orphaned. With no list: and no block, the chip and <h2> have been rendering above an empty grid ever since.

Restored as the category description so it is data-driven rather than hardcoded. Every other category has a null description, so exactly one note renders.

2. Fold archived releases, and move them below the Docker images

Most people on this page want something current, so an archived category no longer sits mid-page between Tools and Docker. It now renders last, after the Docker images, as a <details> shut by default showing just its title and a component count.

Categories opt in with archived: true in releases.yml — a property of the data, not a special case for one hardcoded section. The chip strip and the "Latest releases" aside follow the same flag: archived chips move after the Docker chip and are muted, and archived components no longer compete for a slot in the aside.

The card grid moved to layouts/partials/downloads-cards.html so the live and folded paths render identical markup.

Anchors keep working. A <details> containing the target of location.hash is opened on load and on hashchange, so /downloads/#BanyanDBJavaClient and the Archived Releases chip both land on an expanded section.

Verification

Local Hugo build, no errors.

Order, chips and body both:

Foundations, Agents, Operation, Database, Tools, DockerImages, ArchivedReleases
check result
<details> open by default no
summary "Archived Releases" + "1 component" (singular)
cards per section Foundations 4, Agents 13, Operation 4, Database 3, Tools 2, Docker 18, Archived 1 — unchanged by the partial extraction
dl-cat-note on page 1 (Archived Releases only)
restored links both return 200
"Latest releases" aside Java, Python, Go, NodeJS, Horizon UI — no archived entries
compiled CSS .dl-archived, [open] chevron rotation, .dl-chip--muted all present

Context: why the section had no components until now

No previously-archived repo ever had its own release artifacts to move here:

  • Rocketbot UI → Booster UI always carried sourceText: Included in the main repo release — no standalone downloads. When Booster UI was archived (c8b39b8, May 2026) its entry was simply replaced by Horizon UI.
  • Docker Files, Legacy UI, OAL Generator never had releases.yml entries at all.

The BanyanDB Java Client is the first retired component that shipped its own signed release, which is why #899 produced the section's first card.

#431 added "- type: Archive" to releases.yml purely so the section got a nav
chip, and put the actual content in a hardcoded container-archived block in
downloads-block.html: a note that older releases are unmaintained but still
downloadable, plus links to the ASF archive and the incubator archive.

The redesign (#844) rewrote downloads-block.html and dropped that block, but
left the now-renamed "Archived Releases" entry in releases.yml behind. Since
that entry has never had a list, the chip and the <h2> have rendered above an
empty grid ever since.

Restores the text as the category description so it is data-driven rather than
hardcoded, and renders any category description under its heading. Every other
category has a null description, so nothing else changes.
@netlify

netlify Bot commented Aug 16, 2026

Copy link
Copy Markdown

Deploy Preview for skywalking-website-preview failed.

Name Link
🔨 Latest commit fb2c311
🔍 Latest deploy log https://app.netlify.com/projects/skywalking-website-preview/deploys/6a81311b5bde7a00089ca760

Most people on the downloads page are looking for something current, so an
archived category no longer sits in the middle of the page: it renders last,
after the Docker images, as a <details> that is shut by default and shows
only its title and a component count until opened.

Categories opt in with `archived: true` in releases.yml, so this is a
property of the data rather than a special case for one hard-coded section.
The chip strip and the "Latest releases" aside follow the same flag — chips
for archived categories move after the Docker chip, and archived components
no longer compete for a slot in the aside.

The card grid moves to partials/downloads-cards.html so the live and folded
paths render identical markup.

Anchors keep working: a <details> holding the target of location.hash is
opened on load and on hashchange, so /downloads/#BanyanDBJavaClient and the
Archived Releases chip both land on an expanded section.
@wu-sheng wu-sheng changed the title Restore the archive links the redesign dropped from Archived Releases Downloads: restore the archive links, fold archived releases to the bottom Aug 16, 2026
@wu-sheng
wu-sheng merged commit 37b223b into master Aug 16, 2026
1 of 5 checks passed
@wu-sheng
wu-sheng deleted the fix/downloads-archive-links branch August 16, 2026 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant