forked from Qortal/q-blog
greenflame089
29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
# ADR 0005 — Allow Multiple Blogs per Name (Plan A)
|
||
|
||
Date: 2025-08-21
|
||
Status: Accepted
|
||
|
||
## Context
|
||
|
||
The product contract states a **Name** can own multiple **Blogs**. The UI currently assumes one blog per name (single “My Blog” button; `/{name}` → single blog).
|
||
|
||
## Decision
|
||
|
||
- Introduce a **User Blogs** page at `/{name}/blogs` listing all blogs for a Name.
|
||
- Change `/{name}` behavior to **smart redirect**:
|
||
- If exactly one blog → redirect to that blog’s posts route.
|
||
- Else → show `/{name}/blogs`.
|
||
- Replace “My Blog” button with a **“My Blogs” dropdown** listing all blogs and a “Create new” action.
|
||
- Keep existing blog-scoped routes; no schema changes.
|
||
|
||
## Consequences
|
||
|
||
- Minimal code churn; consistent with routing & scoping contracts.
|
||
- Slight change in navigation expectations for multi-blog Names (mitigated by redirect rule).
|
||
- Adds one new page and augments header menu; no backend migration.
|
||
|
||
## Alternatives Considered
|
||
|
||
- **Ultra-minimal**: only a dropdown; no new page. Rejected to avoid discoverability issues.
|
||
- **Always list page**: `/{name}` → blogs list even for single blog. Rejected for extra click in common case.
|