create-popular-site 0.10.0

package/templates/starter/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 Your Community. 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/starter/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>

package/templates/starter/src/content/events/first-meetup.md

@@ -0,0 +1,16 @@
+---
+title: "Our first meetup"
+date: 2026-08-06
+description: "Describe the event in a sentence or two."
+image: "/images/post-1.png"
+tags: ["meetup"]
+time: "6:00 PM – 8:00 PM"
+# References a venue page and a speaker profile: the event inherits the
+# venue's name, address and arrival notes, and shows Alex's bio card.
+venueRef: "community-hall"
+speakers: ["alex"]
+checkin: "Bring your registration email (print or phone) and photo ID."
+rsvp: "https://example.com/rsvp?event=first-meetup&src=site"
+---
+
+Describe the event. This one is dated in the future so it shows under **Upcoming**, events move to **Past** automatically after their date.

package/templates/starter/src/content/events/launch-night.md

@@ -0,0 +1,20 @@
+---
+title: "Our launch night"
+date: 2026-05-14
+description: "Our first evening together, with two short talks and lots of hellos."
+image: "/images/post-1.png"
+tags: ["meetup"]
+time: "6:00 PM – 8:00 PM"
+venueRef: "community-hall"
+# Multi-talk event: the talks[] array renders a Talks section with per-talk
+# recording and slides links, and each talk feeds the /talks/ archive.
+talks:
+  - title: "Why we started this community"
+    speaker: alex
+    recording: "https://example.com/watch/launch-night"
+    slides: "https://example.com/slides/launch-night.pdf"
+  - title: "What to expect at future meetups"
+    recording: "https://example.com/watch/what-to-expect"
+---
+
+A recap of our launch night. Both talks were recorded, catch up below.

package/templates/starter/src/content/organizers/sam.md

@@ -0,0 +1,7 @@
+---
+title: "Sam Example"
+weight: 10
+role: "Lead organizer"
+photo: "/images/organizer-1.png"
+description: "Replace with a short, friendly bio."
+---

package/templates/starter/src/content/pages/about.mdx

@@ -0,0 +1,22 @@
+---
+title: "About us"
+eyebrow: "About us"
+lead: "One sentence about your community."
+---
+
+import FAQ from 'astro-theme-popular/components/FAQ.astro';
+import FAQItem from 'astro-theme-popular/components/FAQItem.astro';
+
+Write two or three warm paragraphs about your community: who it's for, what a gathering looks like, and that newcomers are always welcome.
+
+## Land acknowledgement
+
+Add your community's land acknowledgement or welcome statement here, or remove this section.
+
+## Common questions
+
+<FAQ>
+  <FAQItem q="Do I need experience to join?" open>No. Newcomers are exactly who this is for, come as you are.</FAQItem>
+  <FAQItem q="Is it free?">Yes. Events are free to attend.</FAQItem>
+  <FAQItem q="How do I find the room?">Check the event page for arrival notes (buzz codes, door instructions). If in doubt, ask an organizer when you arrive.</FAQItem>
+</FAQ>

package/templates/starter/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. Your Community 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/starter/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
+
+Your Community 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/starter/src/content/pages/speak.md

@@ -0,0 +1,23 @@
+---
+title: "Speak with us"
+eyebrow: "Call for speakers"
+lead: "Got something to share? We would love to have you on the schedule."
+---
+
+You do not need to be a professional speaker, and your topic does not need to be groundbreaking. Some of our best sessions have come from people talking about something they learned last month.
+
+## What we look for
+
+A talk that teaches, sparks a conversation, or shows the room something you are excited about. First-time speakers are especially welcome, this is a friendly place to start.
+
+## Lightning talks welcome
+
+Not ready for a full session? A five-minute lightning talk is a great way to dip a toe in. Bring one idea, one demo, or one story.
+
+## We will help with your slides
+
+Tell us roughly what you want to cover and an organizer will help you shape it: an outline, a practice run, feedback on your slides, whatever is useful. You will not be left to figure it out alone.
+
+## Propose a talk
+
+Send us your idea through our [call for speakers form](https://example.com/cfp). Not sure yet? [Say hello in the chat](https://example.com/chat) and we can talk it through.

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

@@ -0,0 +1,25 @@
+---
+title: "Start here"
+eyebrow: "New here?"
+lead: "Coming to your first event? Here is everything you need to feel at home before you walk in."
+---
+
+New faces are the whole point. You do not need to know anyone, and you do not need to be an expert, come as you are.
+
+## What a typical evening looks like
+
+Doors open a little before the start time so there is room to arrive, grab a drink, and settle in. We usually open with quick welcomes, run the main session, then leave plenty of time to talk afterwards. Nothing is mandatory: stay for all of it or slip out when you need to.
+
+## Join the chat first
+
+Most of the community lives in our group chat between events. Joining before you arrive is the easiest way to break the ice: say hello, ask what to expect, and you will already recognise a few names in the room. There is a "Join the chat" link in the header and footer once it is set up.
+
+## Who to look for on arrival
+
+Look for an organizer near the door, they are expecting you and happy to make introductions. If you are not sure who that is, ask anyone; regulars are used to helping newcomers find their feet.
+
+## You can just watch
+
+There is no pressure to speak, present, or perform. Plenty of people come for a few events just to listen before they say much at all. Watching quietly from the back is a completely normal way to start, and you are welcome to do exactly that.
+
+When you are ready for more, [say hello in the chat](https://example.com/chat) or [read the FAQ](/about/).

package/templates/starter/src/content/speakers/alex.md

@@ -0,0 +1,7 @@
+---
+title: "Alex Example"
+role: "Guest speaker"
+photo: "/images/organizer-1.png"
+bio: "Replace with a short speaker bio. This card appears on events Alex speaks at, and on their profile page."
+website: "https://example.com"
+---

package/templates/starter/src/content/venues/community-hall.md

@@ -0,0 +1,13 @@
+---
+title: "Community Hall"
+address: "123 Your Street"
+notes: "Buzz 204 at the side door; the elevator to level 2 is past the mailboxes."
+accessibility: "Step-free access via the main entrance; accessible washroom on site."
+wheelchair: true
+transit: "Two blocks from Central station; bus 12 stops outside."
+parking: "Free street parking after 6pm; a paid lot is next door."
+access: "Gender-neutral washrooms on level 2. A quiet room is available on request. Fragrance-free space; please skip strong scents. Kids welcome, there's a play corner at the back."
+website: "https://example.com"
+---
+
+Describe the venue: the room, the vibe, anything a first-time visitor should know. Events that set `venueRef: "community-hall"` inherit this venue's name, address and arrival notes automatically.

package/templates/superfan/popular.config.ts

@@ -0,0 +1,235 @@
+/** Popular: theme configuration (Truly Madly Riley, personal-site demo).
+ *  Shows the theme running a personal site for one person instead of a
+ *  community: the blog is a news feed, events are speaking appearances,
+ *  and there is no organizers section at all. Riley is fictional.
+ *  See README for all options. */
+
+export const SITE = {
+  title: "Truly Madly Riley",
+  tagline: "A fictional superfan's personal site, demo content for the Popular theme",
+  description: "Riley's corner of the internet: Darren Hayes fandom, vinyl news, and the occasional conference talk. (Riley is a made-up person, this is example content demonstrating the Popular theme as a personal site.)",
+  brandName: "Truly Madly",
+  brandSub: "Riley",
+  logo: '/images/logo.svg',
+  favicon: '/images/logo.svg',
+  ogImage: '/images/hero.svg',
+  locale: 'en-US',
+  customCSS: ['https://fonts.googleapis.com/css2?family=Cinzel+Decorative:wght@700&family=Cinzel:wght@700&display=swap'],
+  landAcknowledgement: "Fan-made and gloriously unofficial: this site is a love letter, not affiliated with anyone it adores.",
+};
+
+/* UI strings. The key set matches the Hugo theme's i18n/en.toml (see
+   PARITY.md); the values here are re-voiced for a personal site, which is
+   also how you'd translate the theme. */
+export const STRINGS: Record<string, string> = {
+  skipToContent: 'Skip to content',
+  primaryNav: 'Primary',
+  toggleMenu: 'Toggle menu',
+  nextMeetup: 'Next appearance',
+  venueTba: 'Venue to be announced',
+  eventCancelled: 'Cancelled',
+  rsvp: 'Details',
+  rsvpExternal: 'Event details',
+  allEvents: 'All appearances',
+  allSpeakers: 'All speakers',
+  allVenues: 'All venues',
+  allOrganizers: 'All organizers',
+  comingUp: 'On the calendar',
+  upcomingEvents: 'Upcoming appearances',
+  upcomingLead: 'Podcasts, panels, popups and the occasional conference. Come say hi after.',
+  noUpcomingEvents: 'Nothing booked right now. Invite me to your thing, or your karaoke night.',
+  lookingBack: 'Looking back',
+  pastEvents: 'Past appearances',
+  venueWanted: 'Venue wanted',
+  confirmed: 'Confirmed',
+  fromTheBlog: 'From the blog',
+  latestFromCommunity: 'Latest news & obsessions',
+  readTheBlog: 'Read the news',
+  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: 'News',
+  eyebrowEvents: 'Appearances',
+  eyebrowAuthor: 'Author',
+  eyebrowDocs: 'Guides',
+  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',
+};
+
+/* Celestial gold on midnight: burnished gold with dark button text,
+   silk-cream ink, deep cosmos surfaces. Uses the dark-palette brand keys. */
+export const BRAND: Record<string, string> = {
+  primary: '#C3A364',        // burnished gold: buttons & main branding
+  primaryHover: '#D9BA7B',   // brighter champagne gold on hover
+  primaryActive: '#A1834C',  // deeper metallic gold when active
+  secondary: '#E6C687',      // soft champagne shimmer
+  accent: '#F3E5AB',         // radiant stardust cream
+  ink: '#F4F1EA',            // silk-cream headings on the dark backgrounds
+  link: '#D9BA7B',           // prose links need light gold on midnight
+  linkHover: '#F3E5AB',
+  surfaceWash: '#121B2D',    // midnight-blue hero / section wash
+  surfaceWashSoft: '#141F36',
+  surfaceInk: '#0A0E1A',     // deep cosmos footer bands
+  surfacePage: '#0A0E1A',    // the page itself goes dark
+  surfaceCard: '#121B2D',
+  surfaceTertiary: '#0F1626',
+  textBody: '#D9D4C5',
+  textMuted: '#A39D8A',
+  textOnBrand: '#0A0E1A',    // dark text on gold buttons, not white
+  borderSubtle: '#26304A',
+  fontSans: 'Inter, system-ui, sans-serif',
+  fontDisplay: '"Cinzel Decorative", "Cinzel", Inter, sans-serif',
+};
+
+export const NAV: {
+  label: string;
+  href: string;
+  children?: { label: string; href: string }[];
+}[] = [
+  { label: 'About', href: '/about/' },
+  { label: 'News', href: '/blog/' },
+  { label: 'Appearances', href: '/events/' },
+  { label: 'Listening guide', href: '/listening-guide/' },
+];
+
+export const CTA = { label: 'Say hi', url: 'mailto:hello@example.com', icon: 'fa-solid fa-envelope' };
+
+export const SOCIAL = [
+  { label: 'Mastodon', icon: 'fa-brands fa-mastodon', url: 'https://example.com' },
+  { label: 'Instagram', icon: 'fa-brands fa-instagram', 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: "Truly, madly, deeply a fan site, an Astro demo site for the Popular theme",
+  credit: { label: 'Popular. An Astro theme by Mariatta.', url: 'https://popular.mariatta.ca/' },
+  columns: [
+    { title: 'Site', links: [
+      { label: 'About', href: '/about/' },
+      { label: 'News', href: '/blog/' },
+      { label: 'Appearances', href: '/events/' },
+    ]},
+    { title: 'Fan stuff', links: [
+      { label: 'Listening guide', href: '/listening-guide/' },
+      { label: 'Concert prep', href: '/concert-prep/' },
+    ]},
+    { title: 'Say hi', links: [
+      { label: 'Email', href: 'mailto:hello@example.com' },
+      { label: 'Mastodon', href: 'https://example.com' },
+    ]},
+  ],
+};
+
+/** Support box at the bottom of blog posts; a personal site's tip jar. */
+export const SUPPORT = {
+  badge: 'Enjoying the blog?',
+  text: 'This site is a one-person labour of love (and of one particular discography). If a post made your day, you can toss a coin in the tip jar or just tell me your favourite b-side.',
+  ctas: [
+    { label: 'Tip jar', url: 'https://example.com/tips', variant: 'primary' },
+    { label: 'Say hi', url: 'mailto:hello@example.com', variant: 'outline' },
+  ],
+};
+
+/** Section list-page headers. */
+export const SECTIONS = {
+  blog: { eyebrow: 'News', title: 'News & obsessions', lead: 'Site news, vinyl arrivals, concert diaries and essays nobody asked for.' },
+  events: { eyebrow: 'Appearances', title: 'Appearances & collabs', lead: "Fandom, pop history and why Affirmation still slaps: I'll talk about it anywhere with a microphone." },
+  organizers: { eyebrow: 'The team', title: 'Organizers', lead: 'It is just me here.' },
+  speakers: { eyebrow: 'Speakers', title: 'Speakers', lead: 'Everyone who has taken the mic at one of our gatherings.' },
+  venues: { eyebrow: 'Venues', title: 'Venues', lead: 'The rooms that host us.' },
+};
+
+export const HOME = {
+  hero: {
+    eyebrow: "Truly · Madly · Deeply",
+    title: "Hi, I'm Riley: full-time Darren Hayes superfan",
+    lead: "Writer, vinyl collector, occasional conference speaker, and the person your friends warned you about if you mention Savage Garden within earshot. This is my corner of the internet.",
+    image: '/images/hero.svg',
+    ctas: [
+      { label: 'About me', url: '/about/', icon: 'fa-solid fa-heart', variant: 'primary' },
+      { label: 'Read the news', url: '/blog/', variant: 'outline' },
+    ],
+  },
+  stats: [{ value: "1997", label: "fan since" }, { value: "27", label: "concerts attended" }, { value: "2", label: "cassette copies of Affirmation" }, { value: "5", label: "karaoke trophies" }],
+  featuresHead: { eyebrow: 'What I do here', title: "One person, three hobbies, one discography", lead: 'The site is personal; the enthusiasm is universal.' },
+  features: [
+    { icon: "fa-solid fa-pen-nib", title: "Write", body: "News updates, concert diaries and essays on two decades of pop history." },
+    { icon: "fa-solid fa-record-vinyl", title: "Collect", body: "Vinyl, cassettes, tour programmes, and one very treasured signed setlist." },
+    { icon: "fa-solid fa-microphone-lines", title: "Talk", body: "Panels and podcasts about fandom, nostalgia and why b-sides matter." },
+  ],
+  testimonialsHead: { eyebrow: 'Kind words', title: 'What people say about the blog' },
+  testimonials: [
+    { quote: "Riley once explained the entire Savage Garden discography to me at a bus stop. I missed my bus on purpose.", name: "Priya", role: "Friend, converted fan" },
+    { quote: "The listening guide got me from zero to crying at Two Beds and a Coffee Machine in a weekend.", name: "Marcus", role: "Reader" },
+    { quote: "I came for the vinyl photos and stayed for the footnotes.", name: "June", role: "Newsletter subscriber" },
+  ],
+  getInvolved: {
+    eyebrow: 'Say hi',
+    title: "Tell me your favourite b-side",
+    lead: "Invite me to your podcast, trade vinyl doubles, or just argue amiably about track sequencing.",
+    ctas: [
+      { label: 'Email me', url: 'mailto:hello@example.com', variant: 'primary' },
+      { label: 'Upcoming appearances', url: '/events/', variant: 'outline' },
+    ],
+  },
+};
+
+/** Demo-only switcher bar. Adopters: set to null (or delete the demo bar usage). */
+export const DEMO_BAR = null;

package/templates/superfan/public/images/chart.svg

@@ -0,0 +1,13 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1600 900" role="img" aria-label="A gold bar chart ranking five eras, the tallest crowned with a star">
+  <rect width="1600" height="900" fill="#0F1626"/>
+  <g fill="#C3A364">
+    <rect x="300" y="480" width="140" height="270" rx="14" opacity="0.55"/>
+    <rect x="520" y="380" width="140" height="370" rx="14" opacity="0.7"/>
+    <rect x="740" y="250" width="140" height="500" rx="14"/>
+    <rect x="960" y="420" width="140" height="330" rx="14" opacity="0.7"/>
+    <rect x="1180" y="540" width="140" height="210" rx="14" opacity="0.55"/>
+  </g>
+  <path fill="#F3E5AB" d="M810,120 L826,164 L873,166 L836,195 L849,240 L810,214 L771,240 L784,195 L747,166 L794,164 Z"/>
+  <path d="M240,750 L1380,750" stroke="#26304A" stroke-width="4"/>
+  <circle cx="220" cy="180" r="3" fill="#F3E5AB"/><circle cx="1400" cy="240" r="3.5" fill="#F3E5AB"/><circle cx="1300" cy="130" r="2.5" fill="#F3E5AB"/>
+</svg>