golem15/summercms
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(19.4.1): record deck, contact, repo and plan decisions (D-20..D-23)

Browse Source
This commit is contained in:
Jakub Zych
2026-10-20 02:45:43 +02:00
parent 1200346bdd
commit 7d62b90775
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.planning/phases/19.4.1-early-public-demo-on-demo-summercms-io/19.4.1-CONTEXT.md
View File

@@ -19,7 +19,7 @@ Not in this phase: the chat family (Phase 20), a live OIDC "log in with" relying
- **D-01:** Inserted as 19.4.1, after 19.4 and before 19.5-19.7. Phase 20 narrows to adding the chat family to this live demo.
- **D-02:** Hosted on rome (`ssh debian@10.8.3.118 -p 2222`, passwordless sudo), next to summercms.io and bm, following `sm-summercmsio-app/DEPLOY.md` (nginx, supervisor, PostgreSQL 15 database and role of its own, TLS via certbot, a `DEPLOY.md` with build, upload, release, rollback). The DNS record for `demo.summercms.io` is created by the user.
- **D-03:** `sm-demo-app` gets a git.golem15.com remote, and its `go.mod` requires tagged versions of the framework and every shared plugin, so a release build compiles without `go.work`. Plugins without a suitable tag get one (additive changes are patch tags, potentially breaking ones minor) — **Reversibility:** one-way — pushed Go module tags are cached by proxies and cannot be reused.
- **D-04:** `/backend` is refused by nginx. The site carries a "want to see the backend? contact Golem15" call to action that opens a contact form on the `golem15.feedback` plugin (submissions land in its admin and by mail).
- **D-04:** `/backend` is refused by nginx. The site carries a "want to see the backend? contact Golem15" call to action that opens a contact form on the `golem15.feedback` plugin (submissions land in its admin and as G15Office tasks; no mail is sent — decided 2026-10-20 after research found the plugin never mails).
### Accounts, registration and reset
- **D-05:** Frontend registration is open, as in bm. No demo credentials are shown anywhere on the site.
@@ -40,6 +40,10 @@ Not in this phase: the chat family (Phase 20), a live OIDC "log in with" relying
- **D-16:** The roadmap deck is generated by `demo:seed` from the framework's `.planning/ROADMAP.md` (phases done and next) plus a curated feature list with links to the demo pages and the docs. The OIDC provider is shown on slides with screenshots and no links. The deck stays current with each deploy.
- **D-17:** The demo runs its own Centrifugo instance on rome (own secrets and namespace) for speaker and remote sync through `lighthouse`, separate from bm's.
- **D-19:** The roadmap deck has a "Cooperation with pxpx" slide: work Golem15 does not plan to do itself but that would make migrating pxpx's OctoberCMS applications straightforward. It lists (1) GraphQL compatible with Lighthouse PHP, which most pxpx applications use, and (2) migrating and supporting legacy WordPress applications through `tide` (recording the old site and replaying against the port). The slide is curated content in `demo:seed` (neither item is on ROADMAP.md), in English and Polish, with no links.
- **D-20:** The deck is the user's main presentation at an orientation meeting on 2026-10-21, so it is its own short plan, executed **first**, and must be presentable that day before the Nuxt port and the deploy land (from bm's existing presentation viewer or a local run; the plan picks the cheapest reliable path and ends with a human check of the deck). It must be properly done, not a stub. Sections, in order: (1) the roadmap (phases done and next, from ROADMAP.md, client names filtered); (2) features of the framework and the shared plugins; (3) migration from PHP showcases (WinterCMS/OctoberCMS apps ported plugin by plugin, frontend unchanged; `tide` parity record and replay; the OIDC provider as screenshots); (4) the pxpx cooperation slide (D-19); (5) the future of the framework: an MCP-controlled CMF (content, admin and scaffolding driven by AI agents through MCP). English and Polish. The generator lives in `demo:seed` so later plans and deploys reuse it.
- **D-21:** `sm-demo-app` and `vue-demo-app` are private repositories on git.golem15.com.
- **D-22:** Only the site half of the reload-on-deploy todo is done here (vue-demo-app); the admin half (boardwalk, framework tag) stays open with a progress note.
- **D-23:** Five plans: 01 roadmap/sales deck seed (D-16, D-19, D-20), 02 release and live tracer (tags, module-mode go.mod, deploy, repos, first deploy with banner and backend call to action), 03 accounts, tour, EN/PL and journal, 04 presentations port, quizzes and own Centrifugo, 05 unit tests and live verification.
- **D-18:** Quizzes need a login: a registered user takes a seeded quiz and sees score and past attempts; anonymous visitors see the quiz list and a "register to take it" prompt.
### Claude's Discretion