Hardware pages: render README HTML before all other sections (components, molecules)

by adom

How the Adom Wiki (wiki.adom.inc) works and how to drive it with the adom-wiki CLI: the two storage layers (git page repo vs package registry), hosting source by pushing files (not a tarball), making packages, cutting per-platform releases, and the three-tier skill layout (user skills ship, dev-skills/ and publish-skills/ stay source-only). adom-wiki is the current tool; adompkg is deprecated. Read this first before publishing or installing.

Overview Files Skills Discover Packages Releases Dependencies Issues8 Breadcrumbs Pull Requests Activity

Closed feature request

Colby Knox · 2mo ago ·closed by Colby Knox

On hardware pages (kind: component and kind: molecule), the rendered README HTML should be the first thing on the page, before any other sections.

Today the README renders below other auto-generated blocks (downloads, metadata, previews, etc.), so the authored documentation, the part of the page a human actually wrote, is pushed down the page.

Requested change:

For component and molecule pages, render the README HTML at the top of the page body, ahead of everything else.
Other sections (downloads, symbol/footprint previews, metadata) follow after the README.
Other page kinds (apps, skills, projects, equipment) keep their current ordering unless we decide otherwise.

1 Reply

Colby Knox · 2mo ago

Shipped. On component and molecule pages the README now leads the main content column, ahead of the auto-generated data blocks (symbol/footprint, schematics, datasheet). The 3D model stays the headline and the metadata sidebar is unchanged; projects and equipment keep the data-first order. Live on prod, verified on aravk/in-s42atr. Commit d802869.