post-ai.systems

Rich Text

Rich Text Essence
Breakpoint

A long-form page uses one readable copy tier for paragraphs and lists, narrower supporting measures for hierarchy, and a wide tier for media and technical material.

A reading system with deliberate width tiers

A Wiki-published paragraph can carry enough context to explain a decision without turning every sentence into a separate block. The wider copy measure reduces unnecessary wrapping while the existing Rich Text side spacing continues to define the page field.

Supporting hierarchy remains narrower

Paragraphs and lists share the canonical copy measure. Headings, summaries, quotes, and subheadings may stay narrower so the article keeps a visible hierarchy, but none of those blocks extends beyond the paragraph column.

  • Semantic Markdown stays owned by Wiki while its visual measure stays owned by Portfolio Design System.
  • List indentation remains inside the same outer boundary as the paragraph copy column.
  • Images and code are the only blocks allowed to use the full width inside existing Rich Text spacing.

Meaning comes from the source content. Rhythm, hierarchy, and reading comfort come from the shared Rich Text contract.

Wide content fills the inner page field while preserving the image-to-caption relationship.
source content
  -> semantic block mapping
  -> readable copy or wide content tier
  -> rendered article and project story