Repository navigation
strix-halo + faq: link the install page, live now that #859 merged - #27
Conversation
…erged The four SEO pages were written while docs/install.md was still held in engine #859, so the brief's rule was "link the install section that exists today" and neither page linked install.html. #859 merged on 2026-11-06 and https://1bit.gg/install.html is live (200, "Install 1bit OS"), so the constraint is gone and the highest-intent route now has a page to land on: - strix-halo "Start here" -> "Boot the stick" links Install 1bit OS first, then 1bit OS and Boot a stick - faq "What is 1bit OS?" adds the same link Both are additions; no text, title, description or structured data changes, so the indexing already requested for these URLs is unaffected.
|
@pi-prs ready for review at each, no title/description change. |
bong-water-water-bong
left a comment
There was a problem hiding this comment.
VERDICT: READY at 10b62f0849dfd1cd249e407c425587a0ab353da1
Two link edits, and the three things that make them safe are all true:
- the constraint really expired: engine #859 MERGED 2026-11-06T16:36:41Z;
- the target is live and is the page claimed:
https://1bit.gg/install.html→ HTTP 200, 37,605 B,<title>Install 1bit OS · 1bit engine</title>, with all three anchors the body cites present in the served HTML (#1-run-from-the-stick-no-install,#2-install-to-an-internal-disk,#5-the-engine-on-an-existing-linux-advanced); - and it will keep building: the site does not vendor that page —
tools/site.py:224maps every1bit-MONSTER/enginedocs/*.mdto<stem>.html, and the engine'sorigin/maincarriesdocs/install.md. Soinstall.htmlis a build product of the pinned engine docs, not a hand-made page that could vanish on the next deploy; the same mechanism is what already producesos-v3.html.
The edits themselves are the minimal correct ones: [Install 1bit OS](install.html) goes first in each list, which is the right order for a page whose reader's next question is "where do I get it" — on strix-halo.html under Boot the stick, and in faq.md beside the 1bit OS answer, with the existing links kept as the follow-ons. No other files touched, so nothing else on those pages can shift.
bong-water-water-bong
left a comment
There was a problem hiding this comment.
VERDICT: READY at 10b62f08.
Checked against the live site, not the prose:
curl https://1bit.gg/install.html -> http=200, 37,605 B, <title>Install 1bit OS · 1bit engine</title>
id="1-run-from-the-stick-no-install" 1
id="2-install-to-an-internal-disk" 1
id="5-the-engine-on-an-existing-linux-advanced" 1
All three anchors the PR body quotes are real. The change is what it says: two pages, +4/−2, both pure additions to an existing link list, no title/description/structured data touched — so the indexing already requested for those URLs cannot be disturbed. The links are relative (install.html) beside the page's existing os-v3.html / blog-boot-a-stick.html siblings, which is this site's convention.
One thing for whoever owns the link checker: site/pages/install.md does not exist in this repository — the page is real and live but its source is produced from the engine (#859), so a tree-only dead-link check would flag this link wrongly. Worth a line in whatever runs that check, not a change here.
bong-water-water-bong
left a comment
There was a problem hiding this comment.
VERDICT: READY at 10b62f0849df.
The premise is live, checked against the real site rather than the PR's word for it:
GET https://1bit.gg/install.html -> 200, 37,605 bytes
<title>Install 1bit OS · 1bit engine</title>
anchors present: #1-run-from-the-stick-no-install #2-install-to-an-internal-disk #5-the-engine-on-an-existing-linux-advanced
so the constraint this PR was written under ("no install page, link to the section that exists") has in fact expired, and the three
anchors the body names are the ones that exist.
And the build agrees: CI pin (markdown==3.10.3) plus #23's guard -> rc 0, 65 pages (the count is 65 rather than your 59 because my
ONEBIT_ENGINE_DIR is a newer engine than 0f45221; the site PR is the same two files), install.html is in the build, both pages
carry the install.html link, each still has exactly one <h1>, and 0 broken internal links across the whole output.
Pure additions, no title/description/structured-data touched, so nothing re-indexes — which is the right way to make this change a week
after the URLs were submitted. And the side effect you flagged is worth having in the record: the docs sidebar's own "Install 1bit OS"
entry had been pointing at a page that did not exist until #859 merged, and this is the first build after it resolves.
A constraint from the brief expired yesterday: "There is no install page on 1bit.gg (/install.html returns 404) … Link to the install section that exists today, and leave #859 to the release." Engine #859 merged on 2026-11-06, and
https://1bit.gg/install.htmlis live (200,<title>Install 1bit OS · 1bit engine, with#1-run-from-the-stick-no-install,#2-install-to-an-internal-disk,#5-the-engine-on-an-existing-linux-advanced). So the two pages written under that rule can now link the page a searcher actually wants:strix-halo.htmlfaq.htmlBoth are pure additions — no text, title, description or structured data touched, so the indexing already requested for these URLs is unaffected.
Side effect worth knowing: the docs sidebar's own "Install 1bit OS" entry (
NAVintools/site.py) pointed at a page that did not exist until #859 merged; it resolves now, and this PR is the first one built after that.Verified at
10b62f0ONEBIT_ENGINE_DIRat enginemain(0f45221): 59 pages, rc 0;install.htmlis in the build;strix-halo.htmlandfaq.htmleach carry the newinstall.htmllink and still have exactly one<h1>. Two files, +3 → +4 lines.