flamenet.io is a Y2K portal and this site was a modern one-column landing
page, so the two read as unrelated products that happen to share a name.
The messenger now renders as a channel of that portal.
What changed
Public/portal.css (new, 798 lines) is a port of wp-content/themes/flamenet-2001/style.css from the flamenet repo. Not a
shared file: the two stacks are separate, and a cross-stack stylesheet
would make this server's appearance depend on a WordPress box. The chrome
now has to be changed in both places, and the file header says so.
layout.leaf carries the portal chrome: utility bar, a channel masthead
with FlameNet above the channel name, the portal's tab strip with
Messenger as the current tab, three columns, portal footer. The masthead
search box searches flamenet.io, which has something to search.
Burgundy throughout, because the theme's own colour map already assigns
burgundy to messages.
Public/landing.css is removed and the asset fingerprint follows portal.css. The dead nav-toggle block goes from landing.js.
Page bodies are restyled by class, not rewritten
Every page body is a .band holding a .wrap, so the heading becomes the
coloured header bar and the eyebrow becomes the tag strip above it. The nine
pages generated from docs are untouched, and no approved copy moved.
LandingContext gains a section slug so the rail can mark the current
page. StatusContext, DonateContext and ReleasesContext have their own
inits, so they set it after construction beside canonical and origin.
Also in here
Drops the "new in the app", "good to know" and "how it works" sections from
both landing pages, and the hero button that pointed at the last of them.
Verified
swift build clean.
All 20 PublicPagesTests pass, including the Spanish chrome parity check
(13 new chrome strings, all with counterparts) and the layout link check.
All 19 routes return 200 on a local instance, both languages included.
Stacks correctly at 375px; the rail flows into rows rather than a wall.
Open question
"Developers" now appears in the rail twice, once as an item pointing at the
landing overview and once as a group heading over Source/Spec/Security/Audit/
Self-host. One of them should probably go.
flamenet.io is a Y2K portal and this site was a modern one-column landing
page, so the two read as unrelated products that happen to share a name.
The messenger now renders as a channel of that portal.
## What changed
- `Public/portal.css` (new, 798 lines) is a port of
`wp-content/themes/flamenet-2001/style.css` from the flamenet repo. Not a
shared file: the two stacks are separate, and a cross-stack stylesheet
would make this server's appearance depend on a WordPress box. The chrome
now has to be changed in both places, and the file header says so.
- `layout.leaf` carries the portal chrome: utility bar, a channel masthead
with FlameNet above the channel name, the portal's tab strip with
Messenger as the current tab, three columns, portal footer. The masthead
search box searches flamenet.io, which has something to search.
- Burgundy throughout, because the theme's own colour map already assigns
burgundy to messages.
- `Public/landing.css` is removed and the asset fingerprint follows
`portal.css`. The dead nav-toggle block goes from `landing.js`.
## Page bodies are restyled by class, not rewritten
Every page body is a `.band` holding a `.wrap`, so the heading becomes the
coloured header bar and the eyebrow becomes the tag strip above it. The nine
pages generated from docs are untouched, and no approved copy moved.
`LandingContext` gains a `section` slug so the rail can mark the current
page. `StatusContext`, `DonateContext` and `ReleasesContext` have their own
inits, so they set it after construction beside `canonical` and `origin`.
## Also in here
Drops the "new in the app", "good to know" and "how it works" sections from
both landing pages, and the hero button that pointed at the last of them.
## Verified
- `swift build` clean.
- All 20 `PublicPagesTests` pass, including the Spanish chrome parity check
(13 new chrome strings, all with counterparts) and the layout link check.
- All 19 routes return 200 on a local instance, both languages included.
- Stacks correctly at 375px; the rail flows into rows rather than a wall.
## Open question
"Developers" now appears in the rail twice, once as an item pointing at the
landing overview and once as a group heading over Source/Spec/Security/Audit/
Self-host. One of them should probably go.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
added 1 commit
<ul><li>fb2ba4dd - Close the div messages.leaf left open, and drop the masthead logo</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/138/diffs?diff_id=2021943119&start_sha=89ed78f40307674562bf1f2c1b12e28a7c69e127)
added 1 commit
<ul><li>0835fe83 - Fix the mobile rail and contain tables in the generated pages</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/138/diffs?diff_id=2021945789&start_sha=fb2ba4dd127f337cee58d179144750100edff84e)
added 1 commit
<ul><li>c0a4ccca - Say on every page that Messenger is a separate app</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/138/diffs?diff_id=2021949725&start_sha=0835fe834b3d157803f04da9b7112918c1a77bbc)
added 1 commit
<ul><li>5827a537 - Drop the duplicate Developers from the rail</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/138/diffs?diff_id=2021952296&start_sha=c0a4cccae232b62d5b863d07c244315da6d8ac79)
paulhitt
(Migrated from gitlab.com)
scheduled this pull request to auto merge when all checks succeed 2026-09-12 16:15:28 +00:00
aborted the automatic merge because the source branch was updated. Learn more.
aborted the automatic merge because the source branch was updated. [Learn more](https://gitlab.com/help/ci/pipelines/merge_trains.md#merge-request-dropped-from-the-merge-train).
added 5 commits
<ul><li>5827a537...5a13cfca - 3 commits from branch <code>main</code></li><li>b3a2f9b9 - Merge 0.18 into the portal re-theme, keeping the removed sections out</li><li>232f2d5f - Take the e2e harness that reads the stylesheet off the page</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/138/diffs?diff_id=2021974682&start_sha=5827a53736e8cbae47f335cb18dc04da363f5134)
paulhitt
(Migrated from gitlab.com)
scheduled this pull request to auto merge when all checks succeed 2026-09-12 16:58:01 +00:00
paulhitt
(Migrated from gitlab.com)
merged commit 032f222abb into main2026-09-12 17:41:09 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
flamenet.io is a Y2K portal and this site was a modern one-column landing
page, so the two read as unrelated products that happen to share a name.
The messenger now renders as a channel of that portal.
What changed
Public/portal.css(new, 798 lines) is a port ofwp-content/themes/flamenet-2001/style.cssfrom the flamenet repo. Not ashared file: the two stacks are separate, and a cross-stack stylesheet
would make this server's appearance depend on a WordPress box. The chrome
now has to be changed in both places, and the file header says so.
layout.leafcarries the portal chrome: utility bar, a channel mastheadwith FlameNet above the channel name, the portal's tab strip with
Messenger as the current tab, three columns, portal footer. The masthead
search box searches flamenet.io, which has something to search.
burgundy to messages.
Public/landing.cssis removed and the asset fingerprint followsportal.css. The dead nav-toggle block goes fromlanding.js.Page bodies are restyled by class, not rewritten
Every page body is a
.bandholding a.wrap, so the heading becomes thecoloured header bar and the eyebrow becomes the tag strip above it. The nine
pages generated from docs are untouched, and no approved copy moved.
LandingContextgains asectionslug so the rail can mark the currentpage.
StatusContext,DonateContextandReleasesContexthave their owninits, so they set it after construction beside
canonicalandorigin.Also in here
Drops the "new in the app", "good to know" and "how it works" sections from
both landing pages, and the hero button that pointed at the last of them.
Verified
swift buildclean.PublicPagesTestspass, including the Spanish chrome parity check(13 new chrome strings, all with counterparts) and the layout link check.
Open question
"Developers" now appears in the rail twice, once as an item pointing at the
landing overview and once as a group heading over Source/Spec/Security/Audit/
Self-host. One of them should probably go.
🤖 Generated with Claude Code
mentioned in merge request flamenet!9
added 1 commit
fb2ba4dd- Close the div messages.leaf left open, and drop the masthead logoCompare with previous version
added 1 commit
0835fe83- Fix the mobile rail and contain tables in the generated pagesCompare with previous version
added 1 commit
c0a4ccca- Say on every page that Messenger is a separate appCompare with previous version
added 1 commit
5827a537- Drop the duplicate Developers from the railCompare with previous version
aborted the automatic merge because the source branch was updated. Learn more.
added 5 commits
mainb3a2f9b9- Merge 0.18 into the portal re-theme, keeping the removed sections out232f2d5f- Take the e2e harness that reads the stylesheet off the pageCompare with previous version
mentioned in commit
032f222abb