forked from Qortal/q-blog
greenflame089
42 lines
2.3 KiB
Markdown
42 lines
2.3 KiB
Markdown
# Q-Blog 1.0 — PRFAQ
|
||
|
||
_Generated 2025-08-16 23:27Z_
|
||
|
||
## Press Release (Narrative)
|
||
|
||
Today we announce **Q-Blog 1.0**, a modern, accessible writing workspace that makes it effortless to publish under multiple blogs with a single name, and to collaborate safely through **Shared Blogs**. Q-Blog pairs a focused editor with strong correctness, accessibility, and testability so writers can publish confidently, teams can coordinate, and readers can trust what they see.
|
||
|
||
Key highlights:
|
||
|
||
- **Multiple blogs per name** — Organize topics cleanly without creating new accounts.
|
||
- **Shared blogs** — Invite editors and authors with role-based permissions.
|
||
- **Inclusive by design** — Keyboard-ready, screen-reader friendly, respectful of motion/contrast preferences.
|
||
- **Resilient** — Deterministic saves, offline tolerance for drafts, clear recoveries on failure.
|
||
- **Transparent** — Human-readable release notes and an upgrade guide.
|
||
|
||
## FAQ
|
||
|
||
**What is Q-Blog? Who is it for?**
|
||
A content creation app for individuals and teams who want a fast, accessible, and reliable blogging workflow.
|
||
|
||
**How is it different?**
|
||
Strong quality bar (tests, a11y), multi-blog under one name, and safe collaboration via shared blogs—all while keeping the UI simple.
|
||
|
||
**Why multiple blogs per name?**
|
||
Writers often publish in distinct domains (e.g., dev notes vs. essays). Separate blogs keep audiences clear without fragmenting identity.
|
||
|
||
**How do Shared Blogs work?**
|
||
Blog owners can invite collaborators and assign roles (**Owner**, **Editor**, **Author**). Permissions are enforced server-side; the UI mirrors capabilities but never trusts the client alone.
|
||
|
||
**What about accessibility?**
|
||
We commit to keyboard-only journeys, semantic landmarks, focus management, descriptive names/labels, and honoring user preferences for motion and contrast.
|
||
|
||
**How do you keep content safe?**
|
||
Rich text is sanitized on save and render (allowlist). Permissions gate every write. Observability captures issues without leaking personal data.
|
||
|
||
**How do you measure success?**
|
||
Reliability (save success rate), accessibility (keyboard checks + automated audits), performance (Web Vitals), and usability (zero “dead-end” flows).
|
||
|
||
**What’s in 1.0?**
|
||
Multi-blog per name, Shared Blogs, resilient editor workflows, accessibility baseline, docs, and a clear release process.
|