Field Notes Deck

Introduce an outdoor-learning program through movement, observation, shared practice and reflection. Field Notes Deck adapts sports-editorial photography into a presentation with white pages, sage cards, rounded image windows and frosted captions. Its example weekend is a fictional program concept; the actual sequence, count and practical details come from your approved brief.

What you get

  • Twelve optional page roles: opening, welcome, setting, activities, experience, formats, team, itinerary, workshop, field kit, reflection and closing. Select, combine, reorder or extend them to meet the exact requested count rather than make every program a twelve-page weekend.
  • A compact outdoor editorial system with licensed Inter type, sky-blue/natural-green photography, thin capsules, sage/forest accents, subtle glass captions and black circular arrow cues. Signature compositions include the notched cycling hero, three-column welcome, court/runner split, four facility cards, sculptural ring, program cards and a guide strip with a central invitation.
  • Thirty-four local catalog pictures for thirty-four example image slots, including independent small avatars, sport/activity scenes, facilitators, outdoor planning and equipment. Many pictures are topic-specific to tennis, golf, running, cycling or sport facilities. The fictional guides and program counts are not real staff, booking availability, endorsements or participant evidence.
  • A page-specific art ledger tracking subject, aspect, placement, palette, prompt and saved result, with independent artwork for each use. Itinerary, workshop, kit and reflection compositions extend the same style; they do not supply verified program logistics or operate a booking service.
  • A standalone HTML presentation with editable content, notes, viewing, thumbnails, presentation mode and print styling. The package supplies recipes/runtime, Python composition/build/check tools and Node media helpers. Requested PPTX keeps text/notes editable and photos separate, with complex artwork/glass/backgrounds rendered; PDF gives one 16:9 page per slide.

Before you choose

Read the itinerary beside the kit and guide pages. The activity sequence should agree with the practical brief, and a sport photograph should not promise a session that the program does not provide. Keep reflection grounded in what participants actually did rather than example outcome claims.

Good fit

  • A presenter is explaining an outdoor-learning weekend or program and needs activities, people, practical preparation and reflection in one sequence.
  • A team wants a consistent, refined visual language across sport settings, program options, guide roles and an itinerary.
  • A creator can provide a clear audience, approved messages and practical source material and wants an agreed presentation length.

Not for

  • Copying protected reference artwork, source identities, logos, recognizable celebrity faces or characters.
  • Automatic research or verification of program results, participant counts, availability, prices or endorsements.
  • A fully operational booking/service website or a PowerPoint where every visual treatment is a native editable shape.
  • Using fictional sports facilities, guides or activity photos as proof that your own program offers those people, locations or services.

How to use

You say/field-notes-deck Create a twelve-page outdoor-learning weekend deck with sky-blue sports photographs, sage cards and frosted overlays.
  1. Provide topic, audience, purpose, approved messages/source material, language and exact count. Add actual activities, itinerary, guide roles, practical requirements and program details where relevant. Agree a missing count from the content and speaking time, counting cover/close within the total unless specified otherwise.

  2. Plan useful roles from the twelve recipes, adapting them to the group rather than padding the story. Preserve white/sage/forest hierarchy, restrained Inter type and natural sports photography. The themes reference describes one authored visual system, not multiple named alternatives or an editor theme picker.

  3. Create an art ledger for the selected slots. Choose suitable library reuse, reuse with generated gaps or regenerate-all, with approved user assets first. Thirty-four local images are available, but sport-specific scenes must fit the actual program. Keep each small avatar distinct; fictional guide labels remain presentation content rather than verified identities.

  4. Match the kit’s 16:9 heroes/kit scenes, 3:4 activity/portrait windows, 4:3 experience/itinerary scenes and square avatars to their actual crops. Use every photographic asset once; a recrop/recolor is still the same source. Maintain complete faces/bodies and clear small-avatar crops. Preserve editable text/icons around images, including the itinerary timeline and reflection prompts.

  5. Embed catalog IDs with the checksum-verifying Node helper. Authorized new imagery may use a built-in tool or optional paid FAL route with FAL_KEY; record returned task IDs for status/fetch without automatic failure retries. Costs/account limits may apply. Use suitable existing material or list labeled gaps when generation is unavailable; the narrative can be reviewed before optional imagery is added.

  6. Replace fictional program names, counts, guide roles, invitations, prices, endorsements and notes with approved material or explicit demo labels. Do not let a program card or arrow imply a working booking action. Compose/build/check with Python 3 and the expected count/style kit; Node serves media helpers. Keep final fonts/media embedded and preserve the font notice.

  7. Open over local HTTP and inspect each 1280×720 page for small labels, glass-caption contrast, hero notch/crops, unique artwork, spacing and actual page total. Confirm thumbnails/notes match the sequence, and test Edit/E, text/images/order, object changes, undo/redo, Save and reopening the saved HTML.

  8. Export requested PPTX/PDF, run check-pptx.py and inspect text/notes, glass/image layers and actual fonts in PowerPoint, Keynote or WPS. Report real findings and unfinished slots; the visual style does not verify program outcomes or logistics.

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