Content review findings: timeline accuracy, placeholder CTAs, markup, and language

[miharp]

Findings from a full review of the site's content for language and accuracy, cross-checked against openvox-docs, the OpenVox release history, and the public record. Grouped by priority.

Factual accuracy

• Timeline names the wrong first release. what-is-openvox.html says "May 2025 — OpenVox 8.19.0 ships — The fork's first public release lands." The first OpenVox release was 8.11, announced January 21, 2025 (Vox Pupuli announcement, LWN coverage), with tags flowing steadily from 8.12.0 (Feb 20, 2025). 8.19.0 shipped May 30, 2025 — likely conflated because GitHub Releases only begin at 8.19.0. The "Early 2025: Puppet access locks down" item ordering should be revisited alongside the fix, since the first release predates it.
• Fork-timing dates worth confirming. The timeline dates the community mirror to October 2024 and the move to Vox Pupuli to November 2024; contemporary coverage describes the intent-to-fork announcement as December 2024. Not necessarily wrong (internal moves precede announcements) — needs confirmation from someone who was there.

All other timeline items (2005 founding, PE in Feb 2011, Vox Pupuli in 2014, $150M total funding June 2018, Perforce acquisition April 2022, 25-node EULA cap) check out, and all six product descriptions are consistent with the docs.

Placeholder CTAs (highest user impact)

• Ten href="#" buttons lead nowhere: Get Started / Installation Guide / Join the Community buttons on index.html (3), what-is-openvox.html (1), why-openvox.html (3), and openvox-vs-ansible.html (3). Suggested targets: the docs getting-started page (https://docs.openvoxproject.org/openvox/latest/getting_started.html) for Get Started/Installation Guide, and the Slack signup / voxpupuli.org/connect links (as used on get-support.html) for Join the Community.

Markup

• Mismatched tag pair on every product page breadcrumb: _layouts/product.html line 7 has <span aria-current="page">{{ page.name }}</a> — opens <span>, closes </a>.
• Sponsor logo alt text: 7 of 9 sponsor logos on get-support.html have empty alt attributes. They're meaningful content (company identification), and the site publishes a VPAT, so they should carry the company names. CI currently runs html-proofer with --ignore-empty-alt; that flag could be dropped once fixed.

Language and consistency

• Breadcrumb "Why Openvox" on why-openvox.html → "Why OpenVox" (brand casing).
• openvox-vs-ansible.html: "agentless via Bolt" → "OpenBolt" (the site's own product name; matches docs terminology conventions).
• get-support.html: "For free, peer support, join…" → "For free peer support, join…" (stray comma).
• VPAT wording: "OpenVox does not include any functional performance criteria" (§1194.31) is a category error — the criteria apply to products; "does not meet the requirements of this section" (§1194.25) reads as a compliance failure where it means the section doesn't apply; "Javascript" → "JavaScript". Also worth deciding how the VPAT scopes "OpenVox": §1194.22 says there are no web-based features, but OpenVoxDB ships a web performance dashboard.
• "open source" vs "open-source" used inconsistently across pages; the Google developer style guide (followed by openvox-docs) uses no hyphen.

Written with AI assistance (Claude Code); reviewed and verified by me.

[miharp]

Verification note on the second accuracy item ("fork-timing dates worth confirming"): GitHub metadata confirms the site is correct as written — the openvox repo was created 2024-10-17 (the October 2024 community mirror) and the OpenVoxProject org on 2024-11-14 (the November 2024 move to Vox Pupuli). The December 2024 date in press coverage was the wider intent-to-fork publicity, not the actual move. That checkbox can be ticked with no site change.

Written with AI assistance (Claude Code); reviewed and verified by me.

[miharp]

One more finding from the browser review pass: the site has no favicon — every page logs a 404 for /favicon.ico. Browsers fall back to a blank tab icon. The header already has an inline SVG logo that could be adapted (as an .ico/.png set or an SVG favicon linked from the default layout).

Written with AI assistance (Claude Code); reviewed and verified by me.

[miharp]

Progress summary — every actionable item now has a PR, all with green checks:

• Placeholder CTAs → Wire up placeholder CTA buttons to real destinations #15. All eleven href="#" buttons wired up (the review count of ten missed the sitewide header Get Started button): Get Started → the ecosystem getting-started guide, Installation Guide → the install prerequisites page, Join the Community → the ecosystem community page. get-support keeps its direct Slack link intentionally.
• Timeline first release → Correct the timeline's first-release entry #16. "May 2025 — OpenVox 8.19.0" corrected to "January 2025 — OpenVox 8.11" per the announcement.
• Fork-timing dates → confirmed correct as written (see verification comment above); no change needed.
• Breadcrumb markup, brand casing, OpenBolt naming, get-support comma, VPAT wording, open source hyphenation → Fix breadcrumb markup and language issues from content review #17.
• Sponsor-logo alt text → resolved as working as intended in Fix breadcrumb markup and language issues from content review #17: the empty alts on the seven linked cards are correct per W3C functional-images guidance (the links already carry the company name as text; adding alt text caused double announcements). The CI --ignore-empty-alt flag is now commented to record this.

Still open, needing maintainer judgment:

• VPAT §1194.22 scoping: whether OpenVoxDB's web dashboard counts as a web-based feature for the "no web-based features" claim.
• Favicon: every page 404s on /favicon.ico (comment above).

Written with AI assistance (Claude Code); reviewed and verified by me.