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

docs(17): shorten the COVERAGE.md opt-out reason and state the goal as a user story

Browse Source
This commit is contained in:
Jakub Zych
2026-10-19 00:13:45 +02:00
parent eb7e39d335
commit 59f57819cc
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.planning/ROADMAP.md
View File

@@ -1065,7 +1065,7 @@ Plans:
### Phase 17: Blog companions
**Goal:** The sitemap, menu and FAQ plugins run on SummerCMS as shared `sm-*-plugin` repos, so a blog site can manage its menus, FAQs and sitemap in the admin again instead of hardcoding them in the Nuxt app.
**Goal:** As a blog site editor, I want to manage menus, FAQs and the sitemap in the SummerCMS admin through the shared sitemap, menu and FAQ plugins, so that they are no longer hardcoded in the Nuxt app.
**Mode:** mvp
**Depends on:** Phase 15, Phase 16
**Repos:** `sm-sitemap-plugin`, `sm-menu-plugin`, `sm-faq-plugin` (new, under `git.golem15.com/golem15/`, see `.planning/notes/core-plugins-own-repos.md`); `summercms.go` for the menu-item type registry; `sm-journal-plugin` for an additive registration of its item types; `sm-grzybyfunkcjonalne-app` to move its FAQ and menu into the plugins

2
.planning/phases/17-blog-companions/COVERAGE.md
View File

@@ -1 +1 @@
No external API integration: this phase ports internal WinterCMS plugins (sitemap, menu, FAQ) to SummerCMS and publishes its own read APIs (/_menu/api/v1, /_faq/api/v1, /sitemap.xml) consumed by first-party Nuxt layers; no third-party service, SDK or remote API is called.
No external API integration: ports the internal sitemap, menu and FAQ plugins and serves first-party read APIs (/_menu, /_faq, /sitemap.xml) to our own Nuxt layers; no third-party service is called.