Blue Block Company Deck

Supply the topic or approved outline, audience, desired count, intended action, language and verified figures, standards and dates. Add supplied imagery and clarify real team identities/contact details. Mark assumptions or demonstration data explicitly rather than inheriting the sample’s pilot counts or six-week program claims.

Choose Blue Block Company, Evergreen White, Plum White or Slate White and plan the story using the ten archetypes. Retain white pages with accent panels, Newsreader sentence-case titles and Inter Tight body. Use the current serif design rather than copying the older all-caps catalog wording.

Keep one takeaway per page, three or fewer blocks, thirty percent empty and the short word budgets. Use the 12-column grid with 77px side margins and 26px gutters, content from approximately y79 to y634 on the 1280×720 frame. Titles are about 47px, cover about 95px and body about 15–17px. Split excess content or move it to notes; do not shrink it to fit.

Use square-corner framed photos on offset accent/stone blocks, with no photo overlap or cards floating over pictures. Sibling cards share style and size, highlighting at most one. Keep content-page chrome to the small brand mark; avoid footers/folios/tag clutter, while preserving any necessary factual disclosure in a concise note or notes as appropriate.

Choose suitable library reuse, generate only missing images or regenerate the set, with approved user pictures first. Nine local catalog pictures are bundled; list/embed IDs through the Node helper with checksum checks. They are fictional/illustrative assets, not documentary evidence of your team. Use a different picture for each semantic page and match the kit’s source aspect (16:9 scenes, square headshots) while checking the actual frame crop.

For authorized new imagery, the package documents built-in generation or an optional paid FAL helper with FAL_KEY and Node. The latter records a returned task ID and uses submit/status/fetch without automatic failure retries. Account availability/charges may apply. Keep each person’s face distinct and preserve readable slide text outside images; list unfilled frames if suitable imagery is unavailable.

Populate recipes and replace fictional names, claims, numbers, chart labels and contacts. Compose/build/check with Python 3 and the expected count/style kit; Node is for media helpers. Embed assets, preserve font/icon notices and keep file size within the package limit. The current core assembly uses bundled runtime assets, not the older mandatory-Node export workflow.

Open over local HTTP and inspect every page for grid alignment, photo crops, legible numbers, wrapping and contrast. Test Edit/E, text/picture/order changes, notes, undo/redo, Save and reopening the HTML. The four presets are generation choices, not an editor theme picker. Export requested PPTX/PDF, run the PPTX check and inspect notes/text/fonts/rendered layers in the target application before sharing.