create-popular-site 0.10.0

package/templates/foodie/src/content/pages/code-of-conduct.mdx

@@ -0,0 +1,38 @@
+---
+title: "Code of Conduct"
+eyebrow: "Code of Conduct"
+lead: "Everyone is welcome, and everyone is safe. This applies to all our events, online spaces and channels."
+---
+
+import Callout from 'astro-theme-popular/components/Callout.astro';
+
+## The short version
+
+Be kind. Be respectful. Assume good faith. Lucky Town Foodie Club is a community of people with a wide range of backgrounds and experience, and we're here to enjoy this together. Harassment and exclusionary behaviour are never acceptable.
+
+## Expected behaviour
+
+- Be welcoming, friendly and patient, especially with newcomers.
+- Be considerate in your speech and actions, and respectful of differing viewpoints.
+- Assume the person you're talking to knows things you don't, and vice versa.
+- Give others space and time to speak; make room for quieter voices.
+
+## Unacceptable behaviour
+
+- Harassment, intimidation, or discrimination in any form.
+- Offensive comments related to gender, gender identity, sexual orientation, disability, physical appearance, race, ethnicity, religion or experience level.
+- Unwelcome sexual attention, or deliberate intimidation, stalking or following.
+- Sustained disruption of sessions or other events.
+- Photographing or recording someone without their consent.
+
+<Callout tone="warn" title="Reporting">
+If you experience or witness behaviour that makes you feel unsafe, tell any organizer at the event, or email **hello@example.com**. Reports are taken seriously and handled with discretion, and we will always protect the privacy of the person reporting.
+</Callout>
+
+## Consequences
+
+Organizers may take any action they deem appropriate, up to and including warning the person, asking them to leave the event, or barring them from future events. Organizers have full authority to protect the safety and comfort of the community.
+
+---
+
+*This Code of Conduct is adapted from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) (CC-BY 3.0) and the [Geek Feminism anti-harassment policy template](https://geekfeminism.fandom.com/wiki/Community_anti-harassment/Policy) (CC0). Adapt it to your community, it's part of the theme's example content.*

package/templates/foodie/src/content/pages/get-involved.mdx

@@ -0,0 +1,27 @@
+---
+title: "Get involved"
+eyebrow: "Get involved"
+lead: "Our community runs on people who step up, to host a session, to offer a space, to sponsor, and simply to show up. Here's how you can help."
+---
+
+## Host a session
+
+We're always looking for members to lead a session! No experience necessary. Whether it's your first time or your fiftieth, we welcome you, and we'll help you prepare, rehearse, or even co-host.
+
+Sessions run 20–30 minutes; show & tell spots are just five. Bring anything our community would love.
+
+<a class="g-btn g-btn--primary" href="mailto:hello@example.com?subject=Session%20idea"><i class="fa-solid fa-hand-sparkles" aria-hidden="true"></i> Suggest a session</a>
+
+## Offer a venue
+
+Have a room for 20–40 people, near transit, with step-free access? You can host our next gathering. Community halls, cafés and workplaces make wonderful hosts. See the [venue checklist](/handbook/) for what we look for.
+
+We'll bring the community and the program; you bring the room. We always thank our hosts publicly by name.
+
+<a class="g-btn g-btn--outline" href="mailto:hello@example.com?subject=Venue"><i class="fa-solid fa-location-dot" aria-hidden="true"></i> Get in touch</a>
+
+## Sponsor & support
+
+Lucky Town Foodie Club is free to attend and runs on in-kind support. Sponsors can provide space, food or supplies, and are thanked by name with a link at the event and in our recap.
+
+<a class="g-btn g-btn--primary" href="https://example.com/donate"><i class="fa-solid fa-heart" aria-hidden="true"></i> Support the club</a>

package/templates/foodie/src/content/pages/speak.md

@@ -0,0 +1,23 @@
+---
+title: "Cook with us"
+eyebrow: "Call for cooks"
+lead: "Got a dish, a technique, or a story to share? We would love to have you lead a night."
+---
+
+You do not need to be a professional, and your dish does not need to be fancy. Some of our best nights came from someone showing us the one thing they make really well.
+
+## What we look for
+
+Something you are excited to share: a family recipe, a technique, a cheap-and-cheerful weeknight win. First-time demos are especially welcome.
+
+## Quick demos welcome
+
+Not ready for a full session? A ten-minute "here is how I do this" is a great way to dip a toe in.
+
+## We will help you prep
+
+Tell us roughly what you want to cover and an organizer will help you plan the shopping, the timing, and the kit. You will not be figuring it out alone.
+
+## Put your hand up
+
+Send us your idea through our [sign-up form](https://example.com/cfp), or [say hi in the chat](https://example.com/chat) and we can talk it through.

package/templates/foodie/src/content/pages/start.md

@@ -0,0 +1,25 @@
+---
+title: "Start here"
+eyebrow: "New here?"
+lead: "Coming to your first night? Here is everything you need to feel at home before you walk in, with or without a dish."
+---
+
+New faces are the whole point. You do not need to be a good cook, and you do not need to bring anything, come hungry and curious.
+
+## What a typical night looks like
+
+We spread everything out on the big table, do quick hellos, then eat and talk for as long as the plates hold out. Sometimes there is a short demo, always there are seconds.
+
+## Bring a dish, or don't
+
+A pot of something is welcome but never required. Plenty of people come empty-handed their first few times and just help wash up. That counts.
+
+## Who to look for on arrival
+
+Find an organizer near the kitchen, they are expecting you and happy to introduce you around. If you are not sure who that is, ask anyone stirring something.
+
+## You can just eat
+
+There is no pressure to cook, present, or know your way around a chef's knife. Watching, and eating, from the side is a completely normal way to start.
+
+When you are ready for more, [say hi in the chat](https://example.com/chat).

package/templates/kdrama/popular.config.ts

@@ -0,0 +1,226 @@
+/** Popular: theme configuration (KDrama Fan Club demo). See README for all options. */
+
+export const SITE = {
+  title: "KDrama Fan Club",
+  tagline: "A fictional fan club, demo content for the Popular theme",
+  description: "A fan club for K-drama lovers, new and obsessed. (This is a made-up club, example content demonstrating the Popular theme.)",
+  brandName: "KDrama",
+  brandSub: "Fan Club",
+  logo: '/images/logo.png',
+  favicon: '/images/logo.png',
+  ogImage: '/images/hero.png',
+  locale: 'en-US',
+  landAcknowledgement: "Add your community's land acknowledgement or welcome statement here, this demo keeps it as a placeholder.",
+  // Enable the /talks/ archive of past-event recordings and slides.
+  talks: true,
+  // Append the "Your name here?" invite card to the speakers list, linking to
+  // /speak/.
+  speakers: { invite: true },
+};
+
+/* UI strings. Translate your site by editing these values; keys map 1:1 to
+   the Hugo theme's i18n/en.toml (see PARITY.md). */
+export const STRINGS: Record<string, string> = {
+  skipToContent: 'Skip to content',
+  primaryNav: 'Primary',
+  toggleMenu: 'Toggle menu',
+  nextMeetup: 'Next meetup',
+  venueTba: 'Venue to be announced',
+  eventCancelled: 'Cancelled',
+  rsvp: 'RSVP',
+  rsvpExternal: 'RSVP on Luma',
+  allEvents: 'All events',
+  allSpeakers: 'All speakers',
+  allVenues: 'All venues',
+  allOrganizers: 'All organizers',
+  comingUp: 'Coming up',
+  upcomingEvents: 'Upcoming events',
+  upcomingLead: 'Save your seat early, space is limited and our rooms fill up.',
+  noUpcomingEvents: 'Nothing on the calendar right now, follow us to hear when the next one lands.',
+  lookingBack: 'Looking back',
+  pastEvents: 'Past events',
+  venueWanted: 'Venue wanted',
+  confirmed: 'Confirmed',
+  fromTheBlog: 'From the blog',
+  latestFromCommunity: 'Latest from our community',
+  readTheBlog: 'Read the blog',
+  allPosts: 'All posts',
+  filterLabel: 'Filter:',
+  filterAll: 'All',
+  subscribeRss: 'Subscribe via RSS',
+  subscribeCalendar: 'Subscribe to calendar',
+  watchRecording: 'Watch',
+  viewSlides: 'Slides',
+  hasRecording: 'Recording available',
+  talks: 'Talks',
+  talksLead: 'Every talk from our past events, with recordings and slides where we have them.',
+  learnMore: 'Learn more',
+  joinChat: 'Join the chat',
+  speakerInviteTitle: 'Your name here?',
+  speakerInviteBody: 'We are always looking for new voices. Lightning talks welcome, and we will help you prepare.',
+  subscribeRssTitle: 'Follow new posts in any feed reader',
+  noPosts: 'No posts yet, check back soon.',
+  ourSpeaker: 'Our speaker',
+  minRead: '{n} min read',
+  authorsBy: 'By',
+  listSeparator: ', ',
+  listSeparatorFinal: ' & ',
+  posts: 'Posts',
+  guest: 'Guest',
+  website: 'Website',
+  previewLabel: 'Preview',
+  previewBanner: 'This is a preview. Nothing here is published yet.',
+  checklist: 'Checklist',
+  copyCode: 'Copy code',
+  checklistDone: 'done',
+  writtenBy: 'Written by {name}',
+  eyebrowBlog: 'Blog',
+  eyebrowEvents: 'Events',
+  eyebrowAuthor: 'Author',
+  eyebrowDocs: 'Docs',
+  eyebrowTag: 'Tag',
+  taggedCount: '{n} post(s) tagged {tag}',
+  speakers: 'Speakers',
+  eyebrowSpeaker: 'Speaker',
+  eyebrowOrganizer: 'Organizer',
+  sessionsBy: 'Sessions by {name}',
+  eyebrowVenue: 'Venue',
+  gettingThere: 'Getting there & access',
+  wheelchairAccessible: 'Wheelchair accessible',
+  transit: 'Transit',
+  parking: 'Parking',
+  venueEvents: 'Events held here',
+  beforeYouArrive: 'Before you arrive',
+  postNavigation: 'More posts',
+  newerPost: 'Newer post',
+  olderPost: 'Older post',
+  paginationLabel: 'Pagination',
+  paginationPrev: 'Previous',
+  paginationNext: 'Next',
+};
+
+/* List pagination size. Mirrors Hugo's [pagination] pagerSize (see PARITY.md). */
+export const PAGINATION = { pageSize: 3 };
+
+/* Renameable content sections: point post-author bylines or the homepage
+   team grid at a differently-named collection (must exist in your
+   content.config.ts). Defaults are the theme's own section names.
+   Hugo parity: [params.sections] (see PARITY.md). */
+export const SECTIONS_MAP = {
+  authors: 'authors',
+  team: 'organizers',
+};
+
+export const BRAND: Record<string, string> = {
+  primary: "#4f46e5",
+  primaryHover: "#4338ca",
+  primaryActive: "#3730a3",
+  secondary: "#3730a3",
+  accent: "#b45309",
+  ink: '#142a36',
+  surfaceWash: "#e2e4f7",
+  surfaceWashSoft: "#f0f1fb",
+  surfaceInk: '#142a36',
+  fontSans: 'Inter, system-ui, sans-serif',
+  fontDisplay: 'Quantico, Inter, sans-serif',
+};
+
+export const NAV: {
+  label: string;
+  href: string;
+  children?: { label: string; href: string }[];
+}[] = [
+  {
+    label: 'About',
+    href: '/about/',
+    children: [
+      { label: 'About us', href: '/about/' },
+      { label: 'Organizers', href: '/organizers/' },
+    ],
+  },
+  { label: 'Blog', href: '/blog/' },
+  { label: 'Events', href: '/events/' },
+  { label: 'Talks', href: '/talks/' },
+  { label: 'Speak with us', href: '/speak/' },
+  { label: 'Handbook', href: '/handbook/' },
+];
+
+export const CTA = { label: 'RSVP', url: 'https://example.com/rsvp', icon: 'fa-solid fa-calendar' };
+
+export const SOCIAL = [
+  { label: 'Instagram', icon: 'fa-brands fa-instagram', url: 'https://example.com' },
+  { label: 'Mastodon', icon: 'fa-brands fa-mastodon', url: 'https://example.com' },
+  { label: 'RSS', icon: 'fa-solid fa-rss', url: '/rss.xml' },
+  { label: 'Email', icon: 'fa-solid fa-envelope', url: 'mailto:hello@example.com' },
+];
+
+export const FOOTER = {
+  tagline: "Watch · Swoon · Debate, an Astro demo site for the Popular theme",
+  credit: { label: 'Popular. An Astro theme by Mariatta.', url: 'https://popular.mariatta.ca/' },
+  columns: [
+    { title: 'Community', links: [
+      { label: 'About us', href: '/about/' },
+      { label: 'Blog', href: '/blog/' },
+      { label: 'Code of Conduct', href: '/code-of-conduct/' },
+    ]},
+    { title: 'Get involved', links: [
+      { label: 'Host a session', href: '/get-involved/' },
+      { label: 'Offer a venue', href: '/get-involved/' },
+      { label: 'Organizers', href: '/organizers/' },
+    ]},
+    { title: 'Organizers', links: [
+      { label: 'Organizer Handbook', href: '/handbook/' },
+      { label: 'Meetup Runbooks', href: '/runbooks/' },
+    ]},
+  ],
+};
+
+/** Support box at the bottom of blog posts, null hides it. */
+export const SUPPORT = null;
+
+/** Section list-page headers. */
+export const SECTIONS = {
+  blog: { eyebrow: 'Blog', title: 'From our community', lead: "Recaps and spotlights from KDrama Fan Club, example posts showing the theme's blog." },
+  events: { eyebrow: 'Events', title: 'Upcoming gatherings & announcements', lead: 'All events are free, and newcomers are always welcome.' },
+  organizers: { eyebrow: 'The team', title: 'Organizers', lead: "KDrama Fan Club is run entirely by volunteers. Want to help? We'd love to have you." },
+  speakers: { eyebrow: 'Speakers', title: 'Speakers', lead: 'Everyone who has taken the mic (or the quiz cards) at one of our nights.' },
+  venues: { eyebrow: 'Venues', title: 'Venues', lead: 'The rooms (and screens) that host us.' },
+};
+
+export const HOME = {
+  hero: {
+    eyebrow: "Watch · Swoon · Debate",
+    title: "A fan club for K-drama lovers, new and obsessed",
+    lead: "Watch parties, trivia nights and OST singalongs. Whether you've seen every episode of Vincenzo twice or you're wondering where to start, we saved you a seat.",
+    image: '/images/hero.png',
+    ctas: [
+      { label: 'RSVP', url: 'https://example.com/rsvp', icon: 'fa-solid fa-calendar', variant: 'primary' },
+      { label: 'About us', url: '/about/', variant: 'outline' },
+    ],
+  },
+  stats: [{ value: "2021", label: "club founded" }, { value: "All", label: "fans welcome" }, { value: "Free", label: "to attend" }, { value: "Monthly", label: "watch parties" }],
+  featuresHead: { eyebrow: 'What we do', title: "What KDrama Fan Club is all about", lead: 'No experience necessary, come as you are.' },
+  features: [
+    { icon: "fa-solid fa-tv", title: "Watch parties", body: "Big screen, subtitles on, communal gasping encouraged. We pick a series and watch the openers together." },
+    { icon: "fa-solid fa-circle-question", title: "Trivia nights", body: "From courtroom scenes to whale facts, test your knowledge of the dramas we all pretend we didn't binge in one weekend." },
+    { icon: "fa-solid fa-music", title: "OST nights & karaoke", body: "The soundtracks deserve their own evening. Bring your ballad voice." },
+  ],
+  testimonialsHead: { eyebrow: 'Kind words', title: 'What members say' },
+  testimonials: [
+    { quote: "I showed up alone to my first watch party. By the finale I had a whole couch.", name: "Dani", role: "Watch-party regular" },
+    { quote: "Trivia night taught me more about whales than school ever did.", name: "Sam", role: "Team Whale Facts" },
+    { quote: "I've cried in public four times this year. Highly recommend.", name: "Mina", role: "Ballad enthusiast" },
+  ],
+  getInvolved: {
+    eyebrow: 'Community',
+    title: "Come for one episode, stay for sixteen",
+    lead: "Host a watch party, suggest a series, or offer us a screening room.",
+    ctas: [
+      { label: 'Get involved', url: '/get-involved/', variant: 'primary' },
+      { label: 'Read the handbook', url: '/handbook/', variant: 'outline' },
+    ],
+  },
+};
+
+/** Demo-only switcher bar. Adopters: set to null (or delete the demo bar usage). */
+export const DEMO_BAR = null;

package/templates/kdrama/src/content/authors/hana.md

@@ -0,0 +1,7 @@
+---
+title: "Hana Kim"
+role: "Lead organizer"
+photo: "/images/organizer-1.png"
+bio: "Curates the watch-party calendar and writes the spoiler policy. Will make you a starter list on request."
+website: "https://example.com"
+---

package/templates/kdrama/src/content/blog/attorney-woo-trivia-recap.md

@@ -0,0 +1,14 @@
+---
+title: "Trivia recap: whales, law, and Extraordinary Attorney Woo"
+date: 2026-04-17
+author: "Priya"
+description: "Team Gimbap takes the crown, and the whale-fact tiebreaker."
+image: "/images/post-2.png"
+tags: ["trivia", "recap"]
+---
+
+Five teams, fifty questions, and a tiebreaker that came down to cetacean trivia, exactly as the show would have wanted.
+
+Congratulations to Team Gimbap, whose victory lap included a spot-on revolving-door demonstration.
+
+The full question set is in the club chat for anyone who wants a rematch at home.

package/templates/kdrama/src/content/blog/castaway-diva-feelings.md

@@ -0,0 +1,14 @@
+---
+title: "Castaway Diva finale: feelings, tissues, and one big singalong"
+date: 2026-05-12
+author: "Hana"
+description: "Our loudest, teariest watch party to date."
+image: "/images/post-3.png"
+tags: ["watch-party", "recap"]
+---
+
+We knew the finale would get us. We did not know the whole room would sing.
+
+Thank you to everyone who brought snacks, tissues and their whole heart. Special shout-out to the member who made playlist cards for everyone to take home.
+
+Where this show ranks in our all-time list is now the club's most contested debate, bring your arguments to the next social.

package/templates/kdrama/src/content/blog/crush-1988-me.md

@@ -0,0 +1,14 @@
+---
+title: "Crush (1988 me): the night Reply 1988 took the club hostage"
+date: 2026-03-20
+authors: ["hana"]
+description: "One neighbourhood, five families, and a whole club arguing about first loves."
+image: "/images/post-3.png"
+tags: ["watch-party", "recap"]
+---
+
+We put on episode one of Reply 1988 "just to see the opening". Three hours later nobody had moved, and someone had adopted the entire Ssangmun-dong neighbourhood as their own family.
+
+The first-crush debate got serious fast: hands were raised, sides were chosen, and the Junghwan vs. Taek question has been tabled for its own dedicated meetup because we ran out of evening before we ran out of opinions.
+
+If you missed it: we're continuing with two episodes a week, the snack roster is in the club chat, and yes, 1988 you would have had a crush too.

package/templates/kdrama/src/content/blog/karaoke-night-in-photos.mdx

@@ -0,0 +1,24 @@
+---
+title: "OST karaoke night in photos"
+date: 2026-06-30
+authors: ["hana"]
+description: "The brave, the ballads and the group finale: karaoke night in pictures."
+image: "/images/post-2.png"
+tags: ["recap", "photos", "community"]
+---
+
+import Gallery from 'astro-theme-popular/components/Gallery.astro';
+import Photo from 'astro-theme-popular/components/Photo.astro';
+import Pullquote from 'astro-theme-popular/components/Pullquote.astro';
+
+Listening first, then the brave took the mic. Here is [OST karaoke night](/events/ost-karaoke/), in pictures.
+
+<Gallery>
+  <Photo src="/images/post-1.png" alt="The room during the opening ballad, lights low" caption="Lights down for the opening ballad." />
+  <Photo src="/images/post-2.png" alt="A member mid-performance at the mic" caption="A first-timer taking on a Goblin OST." />
+  <Photo src="/images/post-3.png" alt="The whole group on their feet for the finale" caption="The finale: everyone up, nobody on key." />
+</Gallery>
+
+<Pullquote cite="A first-time singer">I came to watch and left having sung a duet. No regrets.</Pullquote>
+
+Thanks to everyone who sang, swayed, or held a phone light. Photos we missed? Send them over and we will add them to the album.

package/templates/kdrama/src/content/blog/vincenzo-recap.md

@@ -0,0 +1,14 @@
+---
+title: "Watch party recap: Vincenzo, and a room full of new fans"
+date: 2026-06-20
+authors: ["hana"]
+description: "Two episodes in, half the room had already planned their weekend binge."
+image: "/images/post-1.png"
+tags: ["watch-party", "recap"]
+---
+
+We introduced twelve newcomers to Vincenzo and by the end of episode two, every one of them was asking how many episodes were left, the good version of that question.
+
+The communal gasp at the end of episode one remains one of our all-time top five club moments.
+
+Next up in the rewatch calendar: your nominations, due at trivia night.

package/templates/kdrama/src/content/docs/handbook.mdx

@@ -0,0 +1,127 @@
+---
+weight: 10
+title: "Organizer Handbook"
+eyebrow: "Organizer handbook"
+lead: "Everything you need to run a great meetup. This is the playbook we hand to every organizer and volunteer, the principles and expectations behind a good event. For the step-by-step checklists, see the Runbooks."
+---
+
+import Callout from 'astro-theme-popular/components/Callout.astro';
+
+## Welcome & how to use this
+
+Thank you for helping run KDrama Fan Club. Organizing is a team effort, and you are never expected to do it alone. This handbook is the *why* and *what*, the principles and expectations. The [Runbooks](/runbooks/) are the *how*, tick-box checklists you follow the week of an event.
+
+<Callout tone="info" title="Our north star">
+Every decision comes back to one question: *will this help someone who has never been to a meetup feel welcome here?* If yes, we're on the right track.
+</Callout>
+
+Keep this handbook open in a browser tab during planning. Share it freely with new volunteers, nothing here is secret.
+
+## Roles & responsibilities
+
+We keep roles lightweight. One person can wear several hats, and hats rotate so no one burns out.
+
+- **Lead organizer**: owns the calendar, confirms each event, and is the final point of contact.
+- **Venue coordinator**: sources and confirms the space, checks accessibility, and is the on-site contact for the host.
+- **Session wrangler**: finds and briefs session hosts, collects intros and titles, and looks after them on the night.
+- **Comms lead**: creates the event page, writes announcements, and posts recaps across our channels.
+- **Welcome host**: the friendly face at the door: greets arrivals and makes sure no newcomer stands alone.
+
+<Callout tone="tip" title="Two-deep rule">
+Aim for at least two organizers at every event. If one person is unwell or stuck in traffic, the meetup still happens.
+</Callout>
+
+## Meeting cadence & format
+
+We aim for one gathering a month, usually a weekday evening from 6:00 to 8:30 PM. Formats rotate to keep things fresh and to serve everyone:
+
+- **Session night**: one or two hosts lead a topic, with time for questions. The easiest format to run.
+- **Hands-on night**: everyone participates and makes something. Needs helpers roaming the room.
+- **Show & tell**: five-minute shares, great for first-timers.
+- **Social**: a lower-effort month to just connect the community.
+
+A dependable rhythm matters more than a perfect one. If a month is quiet, run a small social rather than skipping entirely.
+
+## Choosing a venue
+
+A good venue is the single biggest lever on how welcoming an event feels. Look for:
+
+- Capacity for 20–40 people, seated, with room to mingle.
+- Step-free access and an accessible washroom, this is non-negotiable.
+- A screen or space suited to your format, and any equipment your sessions need.
+- Within a short walk of transit or with easy parking.
+- A host contact who can let us in, and stay or delegate a key holder.
+
+<Callout tone="warn" title="Always visit first">
+Confirm the room, the setup and the accessible entrance in person (or via a trusted host) before you announce the event. Surprises on the night are stressful for everyone.
+</Callout>
+
+## Finding session hosts
+
+Great hosts are all around us, including in our own audience. We actively lower the bar to leading a session:
+
+- Invite first-timers and offer to co-host or rehearse with them.
+- Keep an ongoing list of members who've mentioned a topic they love.
+- Ask past attendees what they'd like to learn, then find someone to lead it.
+- Reach out to neighbouring community groups for cross-promotion.
+- Always confirm a title, a 2–3 sentence intro, and a photo for promotion.
+
+What we tell every new host: *no experience necessary. Whether it's your first time leading a session or your fiftieth, we welcome you, and we'll help you prepare.*
+
+## Promotion & communications
+
+Consistency beats cleverness. Post early, post again, and always include the essentials: what, when, where, and how to RSVP.
+
+- Create the event on your RSVP platform as the single source of truth.
+- Announce ~2 weeks out, remind ~3 days out, and post a "tonight!" nudge on the day.
+- Cross-post to your usual channels.
+- Use a consistent poster template so every announcement looks unmistakably yours.
+- Write a short recap within a week, photos (with consent) and a thank-you to hosts.
+
+## Budget & sponsorship
+
+Our events are free to attend and run on a shoestring. Most costs are covered in-kind by venue hosts.
+
+- Typical costs: light snacks and drinks. Venues and equipment are usually donated.
+- Ask sponsors for in-kind support (space, food, supplies) before cash.
+- Thank every sponsor publicly, by name, with a link.
+- Keep a simple shared spreadsheet of what was spent and who paid.
+- Never require payment or personal financial details from attendees.
+
+## Safety & Code of Conduct
+
+Every event runs under our [Code of Conduct](/code-of-conduct/). As an organizer you are also a first responder for it.
+
+- Open every event with a brief, warm reminder of the Code of Conduct.
+- Make sure attendees know which organizers to approach with a concern.
+- Take every report seriously, listen without judgement, and protect the reporter's privacy.
+- You can ask anyone to leave whose behaviour makes others unsafe, you have that authority.
+- Debrief with a co-organizer after any incident and log what happened privately.
+
+<Callout tone="warn" title="When in doubt, prioritize safety">
+It is always better to pause an activity, remove a disruptive person, or end early than to let a harmful situation continue. The community will back you.
+</Callout>
+
+## Day-of logistics
+
+The [Day-of runbook](/runbooks/) has the full checklist. In short:
+
+- Arrive 45–60 minutes early to set up the space and the welcome table.
+- Put up simple signage from the entrance to the room.
+- Greet every person as they arrive; hand newcomers a friendly hello, not a form.
+- Start within 10 minutes of the hour; keep sessions to time so people catch transit home.
+- Take a few photos for the recap, always ask before photographing anyone.
+
+## After the event
+
+The event isn't over when the room empties. A tidy wrap-up keeps hosts happy and the community informed.
+
+- Leave the venue cleaner than you found it and thank the host in person.
+- Send thank-you notes to hosts and sponsors within 48 hours.
+- Publish a recap post with photos and shout-outs within a week.
+- Note what worked and what didn't in the shared organizer log.
+- Lock in a date for next month before momentum fades.
+
+<Callout tone="tip" title="Better late than never">
+If a recap slips, publish it anyway. Our community would rather read a late recap than none at all.
+</Callout>

package/templates/kdrama/src/content/docs/runbooks.mdx

@@ -0,0 +1,57 @@
+---
+weight: 20
+title: "Meetup Runbooks"
+eyebrow: "Runbooks"
+lead: "Six short checklists that take you from an empty calendar slot to a published recap. Your progress is saved in your browser, so you can close the tab and pick up where you left off. Start about three weeks before the event."
+---
+
+import Callout from 'astro-theme-popular/components/Callout.astro';
+import Checklist from 'astro-theme-popular/components/Checklist.astro';
+
+## 1 · Book a venue
+
+Lock the room before anything else, the date depends on it. See the handbook's [venue criteria](/handbook/) for what makes a good space.
+
+<Checklist id="rb-venue" items={["Shortlist 2–3 possible venues from our host contacts.","Confirm capacity (20–40), step-free access and an accessible washroom.","Confirm the equipment and setup your format needs.","Agree the date, start/end time and who holds the key.","Visit or verify the room in person.","Get the host's day-of phone number and building access details.","Send the host a written confirmation with date, time and headcount."]} />
+
+## 2 · Line up a session host
+
+A confirmed venue makes it easy to invite a host. Remember: first-timers welcome, offer to help them prepare.
+
+<Checklist id="rb-host" items={["Invite a session host (or two), check our list of members with topics they love.","Confirm the session title and format (talk / hands-on / show & tell).","Collect a 2–3 sentence intro and a photo for promotion.","Share the run of show and expected attendance.","For hands-on nights: confirm any supplies or prep to tell attendees in advance.","Offer a rehearsal or co-hosting to first-timers.","Send a calendar invite with venue address and arrival time."]} />
+
+<Callout tone="info" title="No host this month?">
+Run a show & tell or a social. A dependable rhythm matters more than a packed agenda.
+</Callout>
+
+## 3 · Set up the event page
+
+Your RSVP platform is the single source of truth. Create the event once all the details are firm.
+
+<Checklist id="rb-page" items={["Create the event with title, date and time.","Write a short, warm description: what, who it's for, and that everyone is welcome.","Add the venue address and accessibility notes.","Set a sensible capacity matching the room.","Add the host's name, session title and intro.","Upload the event image.","Turn on a waitlist and a reminder email."]} />
+
+## 4 · Promote the event
+
+Post early, remind often. Use the [communications guidance](/handbook/) for channels and timing.
+
+<Checklist id="rb-promote" items={["Announce ~2 weeks out across your channels.","Make the poster with your template.","Post a reminder ~3 days before with the RSVP link.","Post a \"tonight!\" nudge on the day of the event.","Thank confirmed sponsors/hosts in the announcements.","Ask the session host to share the event with their network."]} />
+
+## 5 · Day-of run of show
+
+Arrive early, set a warm tone, and keep to time so everyone catches transit home.
+
+<Checklist id="rb-dayof" items={["Arrive 45–60 minutes early; set up the room and test any equipment.","Set up the welcome table and put up signage from the entrance.","Lay out snacks and drinks.","Greet every arrival; give newcomers a warm, personal hello.","Open with a brief Code of Conduct reminder and housekeeping.","Introduce the session host; keep things to time.","Take a few photos, always ask consent first.","Thank everyone, announce next month's date, and close up safely."]} />
+
+<Callout tone="warn" title="Safety first, always">
+You have the authority to pause an activity or ask someone to leave if behaviour makes others unsafe. See the [Code of Conduct](/code-of-conduct/).
+</Callout>
+
+## 6 · Post-event recap
+
+A tidy wrap-up keeps hosts happy and the community in the loop.
+
+<Checklist id="rb-recap" items={["Leave the venue cleaner than you found it; thank the host in person.","Send thank-you notes to hosts and sponsors within 48 hours.","Pick a few consented photos for the recap.","Write and publish a short recap post with shout-outs.","Log what worked and what didn't in the organizer notes.","Confirm next month's date and venue."]} />
+
+<Callout tone="tip" title="Better late than never">
+If the recap slips, publish it anyway, our community would rather read a late one than none at all.
+</Callout>