Private Pro category · 8 compositions
Blogs
Editorial indexes, featured stories, topic browsing, and article discovery. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 8 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Featured field note
Topic shelf
Article river
Research digest
Release journal
Reading queue
Category contract
- Purpose
- Editorial indexes, featured stories, topic browsing, and article discovery.
- Declared dependencies
- gummy-card, gummy-badge, gummy-pagination
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Blogs blocks
Choose a blog composition according to the discovery task: highlight one timely story, browse a topic, scan a chronological archive, or continue from a featured article. A useful index exposes authorship, publication context, and enough summary to make each destination predictable.
Connect cards and filters to canonical article records rather than duplicating editorial data in the view. Preserve real dates, descriptive link text, pagination or archive navigation, image alternatives, and a stable layout when a story lacks artwork. Do not invent readership or popularity signals.
Test the empty archive, a single result, long titles, multiple authors, corrected articles, and removed imagery. Check that structured metadata matches the visible byline and date, topic links remain crawlable, and keyboard users can traverse the index without repetitive or ambiguous destinations.
Define the canonical article fields, editorial owner, correction policy, archive ordering, pagination model, and image fallback before styling the index. Include examples at the shortest and longest supported lengths. Implementation should not infer publication status from the presence of a draft title, and search results should never expose scheduled or withdrawn material.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.