Eidos

Experience / Event

@The-Virtual-Panda/wedding

A wedding planned as its run of show; The Big Picture (vision, guests, venue, budget), moments grouped by day, vendors grouped by category, and the timeline and day-of contacts on one page each.

2instalaciones en los últimos 30 días2instalaciones en total

Instalar

La raíz entera

npx eidosmd install @The-Virtual-Panda/wedding

Una colección, o una variant en una colección que ya tienes

npx eidosmd install @The-Virtual-Panda/wedding --collection The Big Picture
npx eidosmd install @The-Virtual-Panda/wedding --variant The Big Picture.guests
Fuente
The-Virtual-Panda/Eidos-Examples en GitHub
Etiqueta
wedding/v0.3.0
Ruta
wedding
Versión de Eidos
5.4.0
Nomenclatura
Title Case
Palabras clave
weddingeventplanningrun-of-showvendors
Publicado
20 de septiembre de 2026

Qué contiene

Colecciones

The Big Pictureframe

The big picture, four pages: what the day is for, who is coming, where it happens, and what it can cost. Every moment and vendor gets checked against these.

Variants

visionpredeterminadawhat the day is for, how it should feel, and what it is not

Template: templates/frame.vision.md

# {{title}}

_The big picture. Everything else in this folder gets checked against this page: if a moment or a vendor does not serve what is written here, ask why it is in._

## The Day

_A few sentences: who is getting married, where, when, and what kind of wedding this is. Say it the way you would say it to a friend._

## How It Should Feel

_The three or four words you would want guests using on the drive home. Every moment gets held up against these._

## Must-Haves

_The handful of things that are in no matter what: a person, a tradition, a song, a place. Be honest about which are the couple's and which are a parent's._

## Not This Wedding

_The wedding you are deliberately not having: the bigger one, the more traditional one, the one someone else expects. Writing it down here is what keeps the day from growing._
guestswho is coming, and what different kinds of guests will need

Template: templates/frame.guests.md

# {{title}}

_Who is coming, and how different kinds of guests will experience the day. Not the guest list (that is a spreadsheet). This is the shape of the crowd._

## Who Is Coming

_A paragraph or two: roughly how many, from where, how they know the couple._

## Kinds of Guests

_A short paragraph for each kind of guest who needs something different: the wedding party, the out-of-towners, the kids, the grandparents, the plus-ones who know nobody. Only add a kind if they will need something the others will not._

### Kind of guest

_What they are here for, and how their day goes: where they sit, when they arrive, what nobody will have told them._

### Kind of guest

_The next kind, and how their day is different._

## What Guests Will Need

_Step-free access, dietary needs, translation, travel help, childcare, a quiet room. Whatever the day has to provide so everyone above can actually be there._
venuethe places, how guests move between them, and the house rules

Template: templates/frame.venue.md

# {{title}}

_The places the day happens in, and the rules they come with. Every moment happens somewhere on this page._

## The Places

_Each place the day uses (ceremony, cocktails, reception, getting ready, the walk between) in a short paragraph: what it is, how many it holds, what it is like at the hour you will be using it._

## Getting Around

_How guests move from one place to the next and how long it takes. Where people will bunch up. Put a sketch in Files and link it here._

## House Rules

_Capacity, curfew, noise limits, power, parking, what happens if it rains. The venue's rules, and your plan for the one thing you cannot control._

## Getting There and Home

_Travel, hotels, shuttles, the last ride out. What a guest needs to know to arrive and to leave._
budgetthe money, the date, what matters most, and the hard limits

Template: templates/frame.budget.md

# {{title}}

_The money, the date, and what matters most. This is the page every quote gets read against._

## The Budget

_The total, and how it splits: what gets the most, what gets the least, what someone else is paying for. Update it as quotes come in. The total is the limit; the split is the decision._

## The Date and the Countdown

_The date, the season, and the deadlines on the way there: venue booked by, invitations out by, final numbers by. The dates vendors will hold you to._

## What Matters Most

_The two or three things money and attention go to first, in order, and what you would give up to protect them. This settles the argument when the budget says no._

## Hard Limits

_The lines you will not cross: a guest count, a debt, a Sunday. Keep it short._

Run of Showmoment

One page per moment of the day, grouped by day, in the order it happens.

Agrupada por Days

Variants

fullpredeterminadathe full plan for a moment

Template: templates/moment.full.md

# {{title}}

## What This Is For

_Why this moment is part of the day: what it does for the couple and the guests that nothing else does. A short paragraph. If this changes a lot, it is probably a different moment._

### Taking for Granted

_The things you are assuming and have not confirmed: the venue allows it, the right people will be there, the moment before ends on time. Write them down so a guess does not get planned around as if it were settled._

## Still to Decide

_What you do not know yet and need answered. Kept near the top so nothing gets buried. When something is decided, it moves down into the plan._

## How It Goes

_Step by step, in order: what happens, who makes it happen, what it needs. Number the steps so anyone can point at one, and keep each one short. This is the run of show for this moment; the planner reads it first._

1. <!-- the first thing that happens, and who makes it happen -->

## What Guests Take Away

_What a guest has seen, felt, eaten, or been told by the end. If it is not written here, this moment is not promising it._

## Not Part of This

_What this moment deliberately does not do, and which moment does it instead. This is the section that keeps moments from bleeding into each other; a moment without it always runs long._

## Who Is On

_The wedding party and family with a part to play, and the vendors delivering it. Link vendors, `[Photographer](../../Vendors/Photo/Photographer.md)`, rather than just naming them._

## What It Needs

_Space, sound, lighting, power, props, timing, a rain plan. What has to be in place before step one._

## Notes and Decisions

_Notes: the reading, the song, the reminder. Decisions: one line each, with the date, never deleted, so nobody reopens a settled question in month eleven._

<!-- 2026-05-02: Moved speeches before dinner so the kitchen has a fixed serve time. (Planner) -->
rougha rough version: what it is for, what is still to decide, how it goes; grow into full

Template: templates/moment.rough.md

# {{title}}

## What This Is For

_Why this moment is part of the day, in a short paragraph. Grow it into the full version once it has a time and a place._

### Taking for Granted

_What you are assuming and have not confirmed. A rough plan always has some; writing them down is half the point._

## Still to Decide

_What you do not know yet._

## How It Goes

_The steps, in order, numbered. Keep each one short._

1. <!-- the first thing that happens -->

## Not Part of This

_What this moment does not do, and which moment does. Write this first, not last._

Vendorsvendor

One page per vendor, grouped by category: what you are getting, when, and on what terms.

Agrupada por Categories

Variants

fullpredeterminadaa booked vendor: what you are getting, their day, the deal

Template: templates/vendor.full.md

# {{title}}

## What They Are For

_The part of the day this vendor carries, and why them. A short paragraph. If this changes a lot, you are hiring for a different job._

### Taking for Granted

_What you are assuming about them and have not confirmed: they know the venue, the quote includes travel, they bring their own power. Write it down so it does not get planned around as if it were agreed._

## Still to Decide

_What you do not know yet, from them or from you. Kept near the top so it gets asked._

## What You Are Getting

_Exactly what they deliver, as a numbered list you could tick off on the day. If it is not written here, it is not promised, whatever was said on the phone. Put the menu, the shot list, or the set list in Files and link it._

1. <!-- the first thing they deliver, and by when -->

## Their Day

_When they arrive, set up, deliver, and pack out, lined up against the moments that need them. The planner checks this against every moment's steps._

## The Deal

_The quote, the deposit, when the rest is due, what happens if you cancel, whether they are insured. What is signed, and where the contract lives (link it from Files)._

## Not Their Job

_What they do not do and who does it: the cake but not the stand, the photos but not the album. The gaps between vendors are where a wedding day goes wrong; this is where you find them._

## What They Need From You

_A final headcount, a floor plan, a power outlet, the DJ's timing. Anything they need from you or from another vendor before they can deliver. Link the moments and vendors rather than naming them._

## Notes and Decisions

_Notes: the contact, the portfolio, the tasting notes. Decisions: one line each, dated, never deleted._

<!-- 2026-04-18: Went with the second quote; the first did not include staff. (Couple) -->
quotea vendor you are considering: what they would do and what they quoted; grow into full when booked

Template: templates/vendor.quote.md

# {{title}}

## What They Would Be For

_The part of the day they would carry, and why they are on the shortlist. Once they are booked, grow this into the full version; if they are not, mark it `Cut`._

## Still to Ask

_Availability, the real total, what the quote leaves out. Kept near the top so the next call has an agenda._

## What They Quoted

_The number and the conditions. Enough to compare with the other quotes in this category._

## Not Included

_What they do not do, as far as you know. The gap you would need another vendor for._

Otras carpetas

  • Files Contracts, floor plans, playlists, and photos the pages link to.

Roles

Familyroles/family.md
# Family

## Who they are

A parent, someone chipping in, a grandparent with opinions. Cares about the guests, the feel, the traditions, and often the cost. Gets a say; does not get the decision.

## How to respond

- **Vocabulary & depth:** plain, everyday language: who will be there, what will happen, what it will be like. No vendor deals, no run sheets, unless they ask.
- **Decisions:** advisory. They may own a Must-Have in the Vision; everything else is the couple's call. Do not invite them to redesign a moment.
- **Surface / hide:** lead with the Vision, the Guests page, and the one-line summaries of the moments; the Budget only for the parts they are paying for. Keep Still to Decide, The Deal, and the Decisions out of it.
- **Focus:** whether the day looks after the guests they care about, and whether the traditions they hold dear are in or out, and why.

## Calibration

Usually some **experience with the scope** and no interest in how it is put together. Summarize, talk about the feel, and say plainly what is settled.
Framework Ownerroles/framework-owner.md
# Framework Owner

## Who they are

The couple. It is their day: they decide what it is for, how it should feel, what is in, and what is out. Everyone else in this folder is here to help them think clearly, and nobody's preference overrides theirs, whoever is paying.

## How to respond

- **Vocabulary & depth:** talk about the day the way they do: moments, guests, vendors, how it should feel. Put the decision in front of them, not the logistics behind it, unless they ask. Plenty of couples are their own planner; if they want the schedule and the numbers, give them the schedule and the numbers.
- **Decisions:** all theirs. Lay out the options and what each one costs; never settle something in Still to Decide, cut a moment, or pick a vendor for them. Push hardest on Not This Wedding in the Vision and on Not Part of This in every moment.
- **Surface / hide:** lead with what a choice means for how the day feels, the budget, and the timeline; keep contracts and run sheets behind a link.
- **Focus:** the Vision, the Budget, what has been left out on purpose, and whether each moment still says what they meant.

## Calibration

**Experience with the scope:** a couple planning their first big event needs more of the shape of a wedding day explained; one who has run events needs less. **Technical capacity** here means how comfortable they are with budgets, contracts, and schedules; meet them where they are.
Guestroles/guest.md
# Guest

## Who they are

Someone invited. Not planning the day; there to enjoy it. Reads to know what to expect, and reacts.

## How to respond

- **Vocabulary & depth:** plain language about what will happen and what they need to do: where to be, when, what to wear, how to get there. Nothing about how it is being put together.
- **Decisions:** none. Ask what they need and what they are unsure about; do not invite them into the planning.
- **Surface / hide:** lead with Getting There and Home on the Venue page, each moment's What Guests Take Away and its `starts`, and anything a guest has to act on (dietary, travel). Keep vendors, cost, Still to Decide, Decisions, and anything marked `Cut` out of it.
- **Focus:** would they know where to go and when, and does the day sound like one they would want to be at.

## Calibration

**Technical capacity** does not apply. **Experience with the scope** is a guest's own: assume none, and set the day up before answering.
Plannerroles/planner.md
# Planner

## Who they are

Holds the whole day in their head. Reads every moment's steps and every vendor's day to find the clashes, the gaps, and the things nobody has booked. Owns the run of show as a document, never the decisions inside it.

## How to respond

- **Vocabulary & depth:** timing, order, headcount, cost, and what is booked, in plain words. Skip the couple's reasons unless they change the schedule.
- **Decisions:** none of the day's are theirs. They spot two moments that overlap, a vendor whose day does not match a step, a cost creeping past the Budget, and bring each one to the couple. Inside a moment's steps, the order and the timing are theirs to propose.
- **Surface / hide:** lead with `status` (what is Planned, Booked, Confirmed), `starts` and `duration` across the moments, every vendor's Their Day and What You Are Getting, and anything in Still to Decide that is holding up a booking. Leave the feel and the prose alone.
- **Focus:** the run of show as a whole: does every moment have a place, a time, and its vendors, and does it all add up to the Budget.

This folder holds what the day is, not the to-do list: no tasks, no assignees, no checklists, on purpose. Read progress from `status` and the dated Decisions; keep the checklist in whatever tool the couple already uses and link it.

## Calibration

Usually plenty of **experience with the scope** and moderate **technical capacity**. Work from the properties and the steps; the Vision and the Budget are context.
Vendorroles/vendor.md
# Vendor

## Who they are

Delivers one part of the day: the food, the photos, the music, the flowers. Reads their own page to know what they promised, and the moments they are on for to know when and where.

## How to respond

- **Vocabulary & depth:** their trade's words and the day's timing. Nothing about the overall budget, other vendors' deals, or the couple's reasons.
- **Decisions:** none about the day. How they deliver is theirs; what they deliver, and when, was agreed with the couple and is written in What You Are Getting.
- **Surface / hide:** lead with their What You Are Getting, Their Day, What They Need From You, and the steps in each moment that name them. Keep other vendors' deals, the Budget, and everyone else's Decisions out of it.
- **Focus:** what they promised versus what a moment's steps assume, and anything they need that nobody has arranged.

## Calibration

Deep **experience with the scope** in their own trade and little in the rest of the day; set up only the moments they touch. **Technical capacity** does not apply; talk logistics.

Documentos de nivel superior

  • Start Here Start Here.md where to start: what this is, and where things are
  • The Timeline The Timeline.md the whole day on one page, hour by hour
  • Day-Of Contacts Day-Of Contacts.md every number the planner needs on the day, on one page

Propiedades personalizadas

statusTexttodas las coleccionesWhere this stands: Idea, Planned, Booked, Confirmed, Done, or Cut. (Idea | Planned | Booked | Confirmed | Done | Cut)
date_createdDatetodas las coleccionesYYYY-MM-DD. Set once.
date_modifiedDatetodas las coleccionesYYYY-MM-DD. The last change.
tagsListtodas las coleccionesFree tags.
dayobligatoriaTextRun of ShowWhich day this moment happens on. Matches its sub-folder.
needsListRun of Show, VendorsMoments or vendors that have to be in place first, as links.
categoryobligatoriaTextVendorsWhich kind of vendor (catering, photo, music). Matches the sub-folder.
startsDate & timeRun of ShowWhen it starts on the day.
durationNumberRun of ShowHow long it runs, in minutes.
costNumberVendorsWhat they quoted, all in.

Start Here

El primer documento de nivel superior, tal como lo escribió el autor en esta etiqueta, marcadores de posición incluidos. Los enlaces abren la fuente.

{{Product}}

Start here. This folder is the one place that says what the wedding day is: every moment, every vendor, what is decided and what is not. It stays true whether or not anything is booked yet.

{{One line: whose wedding, when, and what kind of day it is.}}

Where things are

  • The Big Picture: four pages: what the day is for, who is coming, where it happens, and what it can cost. Everything else gets checked against them.
  • Run of Show: one page per moment of the day (the ceremony, cocktail hour, the first dance, the send-off), grouped by day, in the order it happens.
  • Vendors: one page per vendor, grouped by category: what you are getting, when, and on what terms.
  • Files: contracts, floor plans, playlists, and photos the pages link to.

The one-page docs

How to use it

A moment’s page says what the moment is: why it is in the day, how it goes step by step, and what guests take away. A vendor’s page says what they have promised: what you are getting, their day, the deal, and where their job ends and the next vendor’s begins. Neither is a to-do list. Write the page before you book, and keep it true after: a moment you drop stays here, marked Cut, so nobody reopens it in month eleven.

Built on Eidos. The page types, the properties each page carries, and the roles live in .eidos/; eidos check keeps it honest.