docs(www): point the website, docs and badges back at GitHub (#35)
* docs(www): point the website, docs and badges back at GitHub
GitHub is the release destination again, so every user-facing reference to the
self-hosted Gitea instance now points at github.com/AdrianBonpin:
- www: nav + footer links, Download / Releases buttons, 'View on GitHub' and
'Star on GitHub' CTAs, landing.js download fallback label, the repo
preconnect/dns-prefetch hints, and the ROADMAP link (Gitea's
src/branch/prod path becomes GitHub's blob/prod)
- www/src/lib/seo.test.ts: matching structured-data fixtures
- README: shields.io badge and the tap prose
- ROADMAP: Homebrew tap URL
Deliberately left pointing at Gitea (they are the fallback, not destinations):
.gitea/workflows/release.yml and scripts/release-mac.sh use git.ranio.xyz as
an API host, so rewriting those would break the fallback path.
* fix(www): update the stale FAQ count assertion
faq.test.ts asserted exactly 5 FAQ items but the list has had 6 since
bdf2bb5 (Release 0.7.15), so the www suite has been red since then. No CI
runs the www tests, which is why it went unnoticed. Found while verifying the
docs change above; unrelated to it.
This commit is contained in:
@@ -2,8 +2,8 @@ import { describe, it, expect } from "vitest";
|
||||
import { faqItems } from "./faq";
|
||||
|
||||
describe("faqItems", () => {
|
||||
it("has exactly 5 items", () => {
|
||||
expect(faqItems).toHaveLength(5);
|
||||
it("has exactly 6 items", () => {
|
||||
expect(faqItems).toHaveLength(6);
|
||||
});
|
||||
|
||||
it("every item has a non-empty question and answer", () => {
|
||||
|
||||
Reference in New Issue
Block a user