Document content substrate: markdown SoR, markitect-tool, shard-wiki
Capture preferred layering (NetKingdom, Railiance, coulomb UI, markitect-tool as markdown lib, DB as cache). Treat markitect-main as legacy; evaluate shard-wiki as thin-slice content plane candidate.
This commit is contained in:
parent
bc78cd27fc
commit
27ba9206f7
3 changed files with 170 additions and 3 deletions
|
|
@ -119,8 +119,9 @@ capabilities but does not redefine the must set.
|
|||
|
||||
## Open product questions
|
||||
|
||||
1. **Visual** — cover image only, or gallery? Max size? Forgejo `assets/` vs object store?
|
||||
1. **Visual** — cover image only, or gallery? Max size? assets next to markdown vs object store?
|
||||
2. **Abstract** — rename `Space.description` → abstract in UI only, or schema rename?
|
||||
3. **Page body editing** — stage 1 keeps edit-in-Forgejo for body, app forms for Title/Abstract/Visual only? Or in-app markdown editor?
|
||||
3. **Page body editing** — stage 1: product forms for Title/Abstract/Visual + markdown body path; exact editor TBD.
|
||||
4. **Delete** — hard delete vs archive (`is_active`)?
|
||||
5. **Transfer cohort** — require public self-registration, or LLDAP bulk invite for stage 1?
|
||||
5. **Transfer cohort** — require public self-registration, or LLDAP bulk invite for stage 1?
|
||||
6. **Content substrate** — see `docs/architecture/2026-08-12-content-substrate-exploration.md` (markitect-tool + markdown SoR; evaluate shard-wiki thin slice vs folder/git store).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue