Orbital Workshop Deck

Introduce a design-methods workshop through the question, working process, time plan and roles people need to follow. Orbital Workshop Deck uses golden circles, orange icon badges, aqua fields and circular photography to make that sequence approachable. Its people, planning bars and device studies are illustrative; the actual methods, timings and project evidence come from your brief.

What you get

  • Twelve optional compositions: circular worktable cover, three-column contents, three-icon agenda, portrait-led principle, two-question/photo page, grouped planning bars, paired process images, core-values field, split process essay, four role portraits, three device studies and centered closing with corner discs. Select, combine, reorder or extend them for the exact agreed count.
  • A cheerful round-geometry system with compact heavy sans-serif headings, light supporting copy, generous white space, large circular photo windows, colored corner discs and orange round badges. Warm workshop combines golden yellow #ffd166, orange #ff753b, aqua #9dd9d8, blue #0086bd, lilac #a392d9 and navy #27364b; Peach and ocean, Garden studio and Lavender lab are coordinated generation-time alternatives.
  • Fourteen catalog photographs include worktable hands, paper/print studies, a sticky-note discussion, fictional role portraits, wireframe review and night landscapes. The app/UX wireframe scene has a subject restriction. Keep portraits and process scenes illustrative rather than claiming real participants or research; editable device frames are presentation content, not a functioning app.
  • A generated self-contained 1280×720 HTML deck with navigation, overview/thumbnails, speaker notes, editing, presentation mode and print styling. Charts, line icons, words and device frames remain editable. The installation supplies recipes, references, catalog and build/media helpers; its generic schema fixture is not a finished custom workshop case.
  • Optional checked PPTX/PDF and separately requested full-page WebP previews. PowerPoint retains native text/notes and separate pictures, with backgrounds, SVG decoration and complex effects rendered. PDF printing gives one 16:9 page per slide. Actual recipient fonts, wrapping and exported pages still need inspection.

Before you choose

Test the workshop plan without its circles first: can participants tell what question they are exploring, how time is divided, who does what and which decision follows? Keep proposed activities and illustrative devices distinct from observed evidence, so a cheerful method diagram does not imply a validated process.

Good fit

  • A facilitator has a defined design question, practical methods and an audience who needs to follow the workshop sequence.
  • A team wants coherent pages for agenda, time allocation, process, values, roles and conceptual studies.
  • A presenter can supply a clear message, accurate source facts, language and desired length, then review the deck at full size.

Not for

  • Reproducing source artwork, identities, portraits, brands, logos or protected characters.
  • Automatic research or verification of a method’s effectiveness, workshop results or user-testing claims.
  • A working application or an all-native-shape PowerPoint requirement; device studies illustrate ideas and exported decoration may be images.

How to use

You say/orbital-workshop-deck Create a twelve-page design-methods workshop deck with warm circular compositions, aqua chapters and original photographs.
  1. Provide topic, audience, key messages/source material, language and exact slide count, including opening/closing unless agreed otherwise. If unspecified, agree length from the material and session duration. Identify which activities, timings and findings are confirmed and which are proposed.

  2. Plan a distinct job for each page: question, agenda, method, time plan, role or next decision. Choose one palette and select/extend the twelve optional recipes rather than forcing three devices or four roles into every brief. Replace example wording and planning-bar values; do not present planned allocation as a measured result.

  3. Prioritize supplied pictures, then choose suitable catalog reuse, generation for gaps or all-new art. Reuse is the fallback without a choice/tool. Log each page, subject, ratio, placement, palette, prompt and saved result. Use each pictorial source on one page only; crops, rotations and recolors do not create independent assets. Functional SVG primitives may repeat, with no artwork quota.

  4. Check the wireframe image’s app/UX restriction and choose process photos, portraits or landscapes only when they serve the topic. Preserve heads/hands in circular crops. Use kit slot ratios for new pictures through built-in generation or the FAL helper/FAL_KEY. FAL tasks cost separately: submit once then poll/fetch, without automatic paid replacement after failure. Disclose unresolved frames.

  5. Compose from the kit with new text, alt descriptions, images, icons, chart labels and values by node ID; remove unused objects. Python 3 handles compose/build/static checks; optional media helpers use Node. Resolve unfilled-image and leftover-example reports, verify the exact count and inline fonts/resources under the package’s 20 MB ceiling.

  6. Inspect every 1280×720 page over local HTTP for circle/badge proportions, title fit, photo uniqueness/crops, planning-bar meaning, device-frame legibility, contrast, bounds and notes/page consistency. Test text/block/order/layout/color edits, notes, undo/redo, Save/reopen and presentation mode. Correct issues and inspect again; static validation does not establish that a workshop or method works.

  7. Deliver page-view HTML with Edit/E and Save (Cmd/Ctrl+S) instructions: browser recovery is local, while Save writes portable edits. Set interface/content languages independently with framework CJK/RTL support. Create/check/inspect requested WebP previews/PPTX/PDF separately. Named palettes guide generation; the shared editor has no style-theme chooser, and embedded PPTX export replaces the retired mandatory Node/Chromium chain.

Requirements and costs

You bring
Presentation topic and audience · Key messages or source material · Desired slide count and language
Dependencies
A browser for presentation and verified print export · Node.js for local validation · A host image generation tool for fresh artwork · Chrome, Chromium or Edge plus Node.js 20 or newer — required only for PowerPoint export
Outside costs
Generating new artwork may incur a separate provider charge. The included original example can be viewed without image generation.
Publisher testing
v1.0.5 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT

FAQ

User reviews

—0 reviews

Select a star to share your experience.

No reviews yet. Ratings appear once readers share real experiences.

Similar Skills

View all skills