Reusable HTML Spec

THUMBNAIL PIPELINE v1.1

A deterministic generation spec for center-band thumbnails using a fixed template workflow. This version removes fixed political copy and fixed typography, and narrows the standard to the one required consistency: a fully usable 16:9 thumbnail core that can be vertically cropped in Photoshop by changing height.

Core Objective

Generate thumbnails that place all meaningful content inside a true 16:9 horizontal band, leaving all outer vertical space disposable. The only required consistency is that the output remains fully usable for vertical crop adjustment in Photoshop by changing height while preserving the horizontal 16:9 content area.

Band constrained Crop-safe 16:9 core No wasted vertical dependency Template-first layout Readable at small scale

Non-Negotiable Rules

1. ALL meaningful pixels must exist inside the center band.
2. NO critical text or objects may cross the band edge.
3. TOP and BOTTOM zones are dead space.
4. Output must remain fully usable after vertical crop adjustment by height.
5. Text is optional.
6. Font choice is flexible.
7. Composition must preserve a complete 16:9 thumbnail core.
8. Output must align with the template without manual repositioning.

Template Geometry Model

Canvas Height = H
Canvas Width  = W

Band Height = user template center band
Band Width  = full template width used by composition

Active zone:
Y in [band_top, band_bottom]
X in [safe_left, safe_right]

Everything outside active zone = ignorable / black / empty

Message Policy

- No fixed message list in the global standard.
- Accept user-supplied headline, subhead, or no text at all.
- If no text is supplied, prioritize image-only urgency composition.
- Never hardcode campaign copy into the reusable standard.
- The standard governs geometry, usability, and crop behavior only.
Selection rule: this document is general-purpose. It does not prescribe specific messaging. It only enforces structural thumbnail compliance.

Text Rendering Flexibility

Typeface policy:
- Font choice may vary by campaign, mood, or topic.
- Do not enforce one house font.
- Permit serif, sans, condensed, ultra-bold, tabloid, or broadcast styles.

Text policy:
- Text is optional.
- If used, it must remain fully inside the 16:9 band.
- Readability at thumbnail scale is mandatory.
- Prefer fewer words when visual density is high.

Styling policy:
- Stroke, glow, shadow, or flat text are all allowed.
- Variation is encouraged.
- Consistency requirement applies to geometry, not typography.

Visual Subject Library

- generic silhouettes of power figures
- data streams / binary fields
- server racks / glowing networks
- locks / broken encryption motifs
- warning panels / cracked interfaces
- city grids / transmission overlays
- glowing cubes / data cores / folders
- money stacks only when visually useful

Composition Rules

  1. All essential imagery must sit entirely inside the horizontal band.
  2. Anything above or below the band must be safely discardable.
  3. Optimize for a final 16:9 crop controlled only by vertical height adjustment.
  4. Fill the band with horizontal energy, not vertical stacking.
  5. Foreground object + midground tension + background system layer is recommended, but not mandatory.
  6. Do not return multi-panel sheets, concept boards, or collages when the intended output is one usable thumbnail.
  7. Typography and visual style may vary; geometry may not.

Color System

Primary palette:
- Red     #FF2A2A
- Orange  #FF7A00
- Yellow  #FFD400

Secondary palette:
- Deep blue  #0A1A3A
- Black      #000000
- White      #FFFFFF

Rule:
Warm = threat / urgency / power
Cool = data / systems / surveillance
Contrast must remain high

Validation Checklist

Before returning final output:

[ ] 16:9 core content fully usable
[ ] Vertical crop can be adjusted by height only
[ ] All text fully inside band (if text exists)
[ ] Main subject fully inside band
[ ] Top/bottom zones safely discardable
[ ] Readable at thumbnail scale
[ ] No multi-panel layout unless explicitly requested

If any item fails: regenerate

Execution Logic

INPUT:
- Template image
- Optional headline override
- Optional visual direction

PROCESS:
1. Read template geometry from uploaded reference.
2. Detect exact center band position and usable width.
3. Build a single thumbnail scene around the band.
4. Ensure all critical content survives a 16:9 crop controlled by height.
5. Keep top/bottom visually empty or discardable.
6. Apply any chosen typography without forcing a standard font.
7. Validate against checklist.
8. Return only if fully compliant.

OUTPUT:
- One usable thumbnail image
- Fully compatible with the fixed template workflow
- Safe for Photoshop vertical crop adjustment by height only

Revision Protocol

Revise this file over time as a living spec. Keep the structure stable and append observations after testing.

Revision log template:

Date:
Test input:
Output result:
What failed:
What succeeded:
Rule update:
Next version:
Failure pattern to avoid: returning concept sheets, collages, or multiple thumbnail ideas in a single image. The pipeline is successful only when it returns one band-compliant asset at a time.