Every package's README badge points at a docs URL that has never resolved

Found while checking TestShards.jl's documentation after the fleet migration.

Every package in this organisation carries a badge and documentation links of the form

https://codes.sota-shimozono.com/<Package>.jl/stable/

That URL returns 404 for every package, and always has. The domain is a CNAME on
sotashimozono/sotashimozono.github.io, a personal Zola portfolio site whose content is
content/works — it has no mechanism to host package documentation, and GitHub Pages cannot
proxy another repository's site under a subpath.

Meanwhile the docs themselves are fine. Each package's Documentation.yml builds and pushes a
complete gh-pages branch, and where Pages is enabled they are served correctly:


`qatlashub.github.io/QAtlas.jl/stable/`	200
`qatlashub.github.io/TestShards.jl/stable/`	200 — after enabling Pages, which had never been on
`qatlashub.github.io/Pinax.jl/stable/`	404 — Pages on, but no `stable/` published
`codes.sota-shimozono.com/<any>/stable/`	404

So there are two separate things: some repositories have Pages off or incomplete, and all of
them advertise an address that no configuration serves.

The branded domain is possible, just not this one

An organisation Pages site with a custom domain also serves that organisation's project sites
under it — <domain>/<repo>/ — so a QAtlasHub/QAtlasHub.github.io with, say,
qatlas.sota-shimozono.com would make the existing badge shape work for every package at once.
It cannot be codes. itself: a domain belongs to one Pages site, and that one is the personal
site's.

Meanwhile

Repointing the badges at qatlashub.github.io/<Package>.jl/stable/ makes them correct today with
no infrastructure. Done for TestShards.jl in QAtlasHub/TestShards.jl#61; the rest are untouched
pending a decision on the domain.

Re-measured 2026-09-10. Still live in seven repositories, and the diagnosis is stronger than "never resolved": the host is sinkholed, not merely 404.

$ getent hosts codes.sota-shimozono.com
198.135.184.22  sinkhole.paloaltonetworks.com

$ curl -o /dev/null -w '%{http_code}' https://codes.sota-shimozono.com/QAtlas.jl/stable/
000

Where it still is — README hits

still carrying it	already on `qatlashub.github.io`
QAtlas.jl (3), AbstractQAtlas.jl (2), Archeion.jl (2), DataVault.jl (2), ParamIO.jl (2), doiget (2), .github (1)	ExperimentalAPI.jl (12), TestShards.jl (9), Pinax.jl (1), SweepRunner.jl (1)

…and the second half, which decides what to point them AT

repo	`/stable/`	`/dev/`
QAtlas.jl, TestShards.jl, DataVault.jl, ParamIO.jl	200	200
Pinax.jl, ExperimentalAPI.jl, AbstractQAtlas.jl, Archeion.jl, SweepRunner.jl	404	200

So this is not one edit repeated seven times. Four repos can go straight to /stable/; the others 404 there and need /dev/ until a tag exists. AbstractQAtlas.jl is registered in General and its /stable/ still 404s, which is a separate finding — registration alone does not publish stable, TagBot has to have run.

Related, and already fixed

The same domain was the default preview-base in docs-preview.yml, so five of seven repositories using that workflow posted a dead preview link on every pull request. Fixed in #26 (ask the Pages API where the site is) and #27 (gh api's 404 body was landing in the URL). That half is done; this one is not.

[noblock]

docs: the README's documentation links point at a host that does not …

Hermes の整理（自動。何も変更していません）

状態: 2026-10-15 時点の再測定。2026-09-10 のコメントから状況が変わっている。

codes.sota-shimozono.com は sinkhole ではなくなった（DNS は sotashimozono.github.io への CNAME、ルート / は 200）。ただし /<Package>/stable/ は 404 のまま（QAtlas.jl, TestShards.jl, AbstractQAtlas.jl で確認）。sotashimozono/sotashimozono.github.io の Pages cname が codes.sota-shimozono.com なので、原因は本文の診断どおり「個人サイトが 1 つのドメインを占有している」と読める。
qatlashub.github.io/<P>/stable/ は 200: QAtlas, TestShards, DataVault, ParamIO, Pinax, ExperimentalAPI, Archeion, SweepRunner。404 は AbstractQAtlas.jl のみ（/dev/ は 200）。9/10 の表で 404 だった Pinax, ExperimentalAPI, Archeion, SweepRunner は解消した。
AbstractQAtlas.jl は release v0.7.17（2026-09-15）後も Documentation.yml が success だが、gh-pages のルートに stable が無い（dev, previews, versions.js, v0.* のみ）。原因は要確認（Documenter の devurl/stable 設定、または tag build の deploy 設定）。
codes.sota-shimozono.com を含むファイル（code search。網羅性は保証されない）: QAtlas.jl（README, docs/make.jl, Documentation.yml ほか）、AbstractQAtlas.jl / DataVault.jl / ParamIO.jl（docs/make.jl）、doiget（site/）、Pinax.jl（test/test_readme.jl）。.github の README には現在ヒットなし。
選択肢にあった QAtlasHub/QAtlasHub.github.io は作成済みだが、中身は LICENSE のみで Pages は qatlashub.github.io 配信（cname なし）。

次の一手: (1) 各 repo の docs リンクを qatlashub.github.io/<P>/stable/ に揃える（AbstractQAtlas のみ /dev/）、または (2) org Pages サイトに別サブドメインを割り当てる、のどちらかを決める。AbstractQAtlas の stable 欠落は別件として追う。

関連: ITensorPartitionFunctions.jl#5（同じ codes. URL を README に持つ。ただし private repo）。

Navigation Menu

Repository navigation

Every package's README badge points at a docs URL that has never resolved #23

The branded domain is possible, just not this one

Meanwhile

Where it still is — README hits

…and the second half, which decides what to point them AT

Related, and already fixed

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Every package's README badge points at a docs URL that has never resolved #23

Description

The branded domain is possible, just not this one

Meanwhile

Activity

sotashimozono commented on Sep 10, 2026

Where it still is — README hits

…and the second half, which decides what to point them AT

Related, and already fixed

sotashimozono commented on Oct 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions