Redesign the "Open source" home section, add Trust Center + SBOM FAQ - #3250
Merged
vpetersson merged 2 commits intoAug 5, 2026
Merged
Conversation
The section was a lone max-w-3xl wall of gray body text with no visual element,
so it did not blend with the rest of the home page (every other section is a
max-w-7xl layout with cards, chips, and a supporting element). Rework it into
the site's own visual language while keeping the SEO copy and keywords:
- Two-column layout at max-w-7xl: narrative prose on the left, a supporting
"Why teams choose Anthias" facts card on the right (free/open source,
self-hosted, no per-screen fees, runs on Pi 2-5 and x86, REST API), using the
same purple icon-chip motif as the "What Anthias does" cards.
- Section header now matches the others (h2 + zinc-500 lead subhead).
- The use cases become a row of brand-purple pills ("Where teams use it") so
the menu-board / wayfinding / dashboard / retail / schools / churches
keywords stay, in a designed element instead of a paragraph.
- Adds a Trust Center link (trust.screenly.io/product/anthias) to the footer
Resources column.
Reuses existing tokens/classes only (bg-bg-light, bg-brand-purple/10,
text-brand-purple, feature-card icon chips); no new CSS. US English, no em
dashes. Built locally with hugo, no errors.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
Claude-Session: https://claude.ai/code/session_01KnaHskk4LSYZKggBdBZZwc
Adds an Operations FAQ: "Is there a software bill of materials (SBOM) for Anthias?" It confirms Anthias publishes an SBOM and links to the Trust Center (trust.screenly.io/product/anthias) to view and download it. Flows into the FAQPage structured data automatically. US English, no em dashes. Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_01KnaHskk4LSYZKggBdBZZwc
vpetersson-bot
changed the title
|
vpetersson
approved these changes
Aug 5, 2026
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
2 participants
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.
Why
The "Open source digital signage you control" section was a lone
max-w-3xlwall of gray body text with no visual element, so it did not blend with the rest of the home page (every other section is amax-w-7xllayout with cards, chips, and a supporting element). It needed a redesign in the site's own visual language with a supporting UI element for balance.What
Home page section redesign
max-w-7xl: narrative prose on the left, and a supporting "Why teams choose Anthias" facts card on the right (free/open source, self-hosted, no per-screen fees, runs on Pi 2-5 and x86, REST API), using the same purple icon-chip motif as the "What Anthias does" cards.h2+zinc-500lead subhead).Trust Center
trust.screenly.io/product/anthias) to the footer Resources column.All SEO copy and keywords are preserved, just restructured. Reuses existing tokens and classes only (
bg-bg-light,bg-brand-purple/10,text-brand-purple, the feature-card icon chips) — no new CSS. US English, no em dashes.Verification
Built locally with Hugo (
--gc --minify), no errors. Confirmed the facts card, use-case pills, two-column grid, the Trust Center footer link, and the SBOM FAQ (visible answer + structured data) all render correctly.