editorial-card-screenshot

Editorial Card Screenshot

Overview

Turn source text into a compact, high-contrast HTML information card that follows the user's editorial prompt, then render a screenshot in one of the supported aspect ratios. The goal is not just density but editorial quality: clear hierarchy, strong visual anchors, and screenshot-stable rendering without accidental cropping or dead space.

Always preserve three output stages unless the user explicitly asks to skip one:

1. Write one sentence judging the information density as high, medium, or low.
2. Output the complete HTML with embedded CSS.
3. Self-check that body text remains readable on mobile.

Workflow

1. Analyze Content Density

Choose layout strategy from the content itself:

• Use "big-character" composition when content is sparse and a single phrase, number, or hook can carry the page.
• Use a two-column or three-column editorial grid when content is dense and needs stronger hierarchy.
• Use oversized numbers, heavy rules, tinted blocks, and pull-quote scale to avoid dead space.
• Do not force dense content into evenly weighted tiles. Build primary blocks, secondary blocks, and lighter supporting blocks.
• Match structure to content type:
  • Ranking / recommendation content: allow asymmetric hero + structured list.
  • Tutorial / analysis / interpretation content: group into overview, core judgment, interpretation, boundary, and conclusion.

Before compressing content, first change the layout skeleton.

• Ratio changes should primarily change reading path, hierarchy, and module arrangement.
• Do not treat ratio changes as a reason to delete content by default.
• Only compress, group, or summarize when the current ratio cannot hold the content clearly after layout has already been restructured.

2. Apply the Stored Editorial Rules

Use these defaults unless the user overrides them:

• Import Google Fonts:

  <link href="https://fonts.googleapis.com/css2?family=Noto+Serif+SC:wght@700;900&family=Noto+Sans+SC:wght@400;500;700&family=Oswald:wght@500;700&family=Inter:wght@400;600;700&display=swap" rel="stylesheet">
  

• Keep body text at 18px to 20px on a 900px-wide composition.
• Keep meta/tag text at 13px minimum.
• Use compact spacing: container padding 40px to 50px, component gaps 30px to 40px, line-height 1.5 to 1.6.
• Add visual weight with 4px to 6px accent rules, subtle gray planes, and 4% noise overlays.
• Favor #f5f3ed or similar warm-paper backgrounds unless the user supplies another palette.
• Preserve breathing room. Do not shrink outer margins so much that the card loses composure.
• For title zones, prefer larger line-height and clearer separation from subtitle / summary blocks.
• In dense right-side modules, reduce font weight slightly so the page stays clear without feeling heavy.
• Use stronger internal structure inside blocks: subheads, bullets, numbered lines, compare rows, or secondary labels.
• Avoid equal-weight boxes when the card is dense. At least one module should feel visually heavier than the others.
• Avoid making every module use the exact same visual language. Differentiate at least one or two areas through tone, scale, background treatment, or typographic weight.
• Default to a calm editorial mode with selective highlights. If the user asks for stronger expression, you may push toward:
  • Bold: more cover-like, stronger anchors, larger weak-background text, heavier accents.
  • Refined: lighter contrast, quieter accents, more restrained paper-like atmosphere.
  • Hybrid: the recommended default when style is not specified; refined overall with a few bold anchor moments.
• Keep Google Fonts imports, but always provide local fallback stacks so the rendered PNG stays structurally stable when remote fonts fail to load.
• If the user explicitly provides a title, use that exact title as the main headline by default. Only compress or reinterpret it when the user asks or when the ratio cannot hold it clearly after layout changes.
• Put interpretation, summary, and framing in the subtitle / deck / summary fields instead of silently rewriting the main title.
• Do not hard-code personal signatures, creator avatars, or account handles into reusable cards unless the user explicitly asks for branding.