acg-website: forum re-themed to v2 brand + todo update
Point the community-forum submodule at the new ACG "Signal" Flarum theme (68c6ab2) and mark the forum re-theme done in the website TODO. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -16,9 +16,10 @@
|
||||
- [x] Independence line + radio-authority woven into About.
|
||||
- [x] Polish pass — contact FAQ two-column, pricing "everything else" full-width tables, mobile overflow fix.
|
||||
- [x] Committed to repo (`2e52b29c`).
|
||||
- [x] **Forum (community.azcomputerguru.com / Flarum 1.8.14 on IX) re-themed to match v2** — ACG "Signal" brand (bone/orange/Anton/mono, brutalist chrome, dark hero band, legible reading area) applied via Flarum core `custom_less`; verified live through Cloudflare. AGY: "reads as the same brand and property." Theme in submodule `community-forum` (`68c6ab2`), settings backed up. Follow-ups: user profile/settings interior pages got no bespoke polish; per-tag/avatar colors kept as functional wayfinding (revisit if Mike wants them brand-neutralized).
|
||||
|
||||
## In progress / next
|
||||
- [ ] **Forum (community.azcomputerguru.com) — re-theme to match v2.** It's a **Flarum** forum, linked from the homepage Dispatch Board ("Read all field reports"). Current `theme-v2.less` is an off-brand dark GitHub/Discord style (Lexend, layered grays) — needs a new v2-matching theme (Anton/Hanken/JetBrains Mono, signal-orange, bone/ink, brutalist, adapted for forum density/readability). DB creds in vault `services/flarum-community.sops.yaml`; origin likely IX (root SSH). *Awaiting go + how the theme is applied (Flarum admin custom LESS vs file).*
|
||||
- Nothing actively in progress. Next up is the go-live backlog below.
|
||||
|
||||
## Backlog — toward go-live on azcomputerguru.com
|
||||
- [ ] Real AI image finals for remaining slots (see `v2/IMAGE-SPEC.md`) — blocked on Grok image-gen cooperating.
|
||||
|
||||
Submodule projects/community-forum updated: a84804b791...68c6ab225e
Reference in New Issue
Block a user