📖✨:give the about page something to say - #1842
Open
DerekNonGeneric wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for gh-pages-openinf ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
DerekNonGeneric
force-pushed
the
feat/about-page
branch
2 times, most recently
from
August 21, 2026 05:52
7b8bd1e to
ea0f541
Compare
It was one sentence pointing at the vision statement, which is itself one paragraph. A quarter of the navigation was a doorway to a doorway. The page now opens on the question the work started from, the one the news post records, because the four verbs in it already carry the site: the description, the vision, and the home page's own heading all say them. Under it are four positions the repository can be checked against, which is the part an about page can do that a mission statement cannot. Dependencies as a cost. A licence chosen to fit what it covers, three ways, for source and samples and prose. Rules written down rather than held by whoever reviews you. Community documents kept in one place and mirrored out. It closes by saying the portal is in its infancy, which the docs index now demonstrates rather than claims: six of the nine handbook rules have no page under them, and the page says so. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5 Assisted-by: Claude-Code:claude-fable-5
DerekNonGeneric
force-pushed
the
feat/about-page
branch
from
August 21, 2026 21:13
ea0f541 to
94d4920
Compare
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
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.
/about/was one sentence pointing at/about/vision/, which is itself asingle 36-word paragraph mirrored from
OpenINF/.github. A quarter of thenavigation was a doorway to a doorway, and it was the last thin page on the
site.
What it says
It opens on the question the work started from, the one the news post records:
Those four verbs already carry the site —
siteDescription, the vision, andthe home page's own heading all say them. Framing them as a question rather
than a mission statement puts them back in the order they happened: the
question came first, and the tools to answer it did not exist.
Under it are four positions the repository can be checked against, which is
the part an about page can do that a mission statement cannot:
count, so it cannot go stale. The news post carries the current specifics.
BlueOak-1.0.0; samples 0BSD; prose share-alike. This is the most considered
thing in the repository and it has never been explained anywhere.
rather than the head of whoever reviews you.
OpenINF/.github,mirrored in at build, so they cannot drift.
It closes by saying the portal is in its infancy, which the docs index now
demonstrates rather than claims.
Nothing on it is about any maintainer.
Design
The head is a full-width pull-quote rather than the two-column grid the home
and docs pages share, with an abstract quotation mark in its own column. The
break from the shared head grid is deliberate: this page's centre of gravity
is the question, not a panel beside it. The commitments sit on a
$secondaryband, echoing the home page's own SDK section.
Checks
nps testpasses, all 17. Nine text pairs computed against composited colour:5.19:1 at the tightest, up to 13.97:1, every one clearing AA. Reasoned
through 1440, 1024, 820, and 390; all grids use counted columns, never
auto-fit.Found while building
_home.scssdefines.band,.section-head,.section-title, and.section-moreunprefixed, at (0,1,0). All three pages use those names, sothe home page's rules are in scope on
/docs/and/about/too. Nothing isvisibly wrong today — both other pages override every property home sets, which
I checked declaration by declaration — but it is latent, and a property added
to a bare rule later would land on three pages at once.
That strengthens the case for the shared-shell extraction already planned;
.wrapand themainreset now have three copies. Left alone here so therefactor stays a separate, reviewable change.
Separately: there is no root
LICENSEfile and nolicensefield inpackage.json. The@licensetags live in source headers only, so GitHub andnpm both read this repository as unlicensed. Awkward beside a page that makes
licensing a stated principle, and worth its own fix.