create-ginko 0.4.0 → 0.6.0

package/templates/events/DESIGN.md

@@ -0,0 +1,197 @@
+# Design system
+
+The rules behind this site's look. Read them before you change colours, type or components, so the site stays
+consistent and accessible (WCAG 2.2 AA, light and dark). The same system runs every Ginko template; only the accent
+and the fonts differ.
+
+## Principles
+
+- A quiet, neutral base; your content and photos carry the character. One accent colour.
+- Hierarchy from size and weight, not colour. One primary button per view. No gradients, glass, blur or decorative
+  shadows. Separate with a 1px border or a background, never both.
+- Phone first. Every page works at 320 px wide with no horizontal scroll; touch targets are at least 44 px.
+- Only tokens. Tailwind's default palette, type scale, radii and shadows are switched off, so `bg-red-500` or
+  `text-2xl` do nothing. A new value is a new token in the CSS and a row in this file, in the same change.
+
+## Where things live
+
+| What | File |
+|---|---|
+| Your accent and fonts | `app/assets/css/main.css` (`--brand`, `--brand-foreground`, `--font-body`, optional `--font-heading`); the light accent again as `seo.color` in `ginko.config.ts` (share cards) |
+| Neutral colours, type scale, spacing, radii, shadow, focus, motion | `app/assets/css/tokens.css` (shared by all templates; do not edit) |
+| Name, logo, navigation, footer links, profiles | `app/app.config.ts` |
+| Components | `app/components/ui/` (shadcn-vue), `app/components/site/`, `app/components/block/` |
+
+`tokens.css` and the components are copied from the Ginko repository (`templates/_features/`). You can change them in
+your own site; in the Ginko repository, change the source there instead.
+
+## Colours
+
+shadcn names, so shadcn-vue components work unchanged. Light / dark:
+
+| Token | Light | Dark | Use |
+|---|---|---|---|
+| `--background` | `#ffffff` | `#0b0b0c` | page |
+| `--foreground` | `#18181b` | `#f4f4f5` | text (17.7:1 / 17.0:1) |
+| `--muted` | `#f4f4f5` | `#18181b` | footer, notice bar, image placeholders |
+| `--muted-foreground` | `#52525b` | `#a1a1aa` | secondary text (7.7:1 / 7.9:1) |
+| `--accent` | `#f4f4f5` | `#27272a` | hover of quiet controls |
+| `--border` | `#e4e4e7` | `#27272a` | dividers, never text |
+| `--input` | `#8a8a93` | `#71717a` | borders of controls (3:1 non-text) |
+| `--primary` | `--brand` | `--brand` | primary button, links in text, focus ring |
+| `--primary-foreground` | `--brand-foreground` | `--brand-foreground` | text on the accent |
+| `--ring` | = `--primary` | = `--primary` | focus |
+| `--success` / `--warning` / `--destructive` | `#15803d` / `#a16207` / `#b42318` | `#4ade80` / `#facc15` / `#f87171` | status text, always with an icon or a word |
+| `--scrim` | zinc-950 at 60 % | black at 72 % | behind the nav sheet and dialogs; the lightbox is opaque dark `--background`, so no page text shows behind a photo |
+
+**Your accent.** `--brand` and `--brand-foreground` in `main.css`, once in `:root` (light) and once in `.dark`. The
+values and their contrast are written next to them. Rules: text on the accent ≥ 4.5:1; the accent on the background
+≥ 4.5:1 in both modes, because links in text use it; in dark mode use a light tint of the accent. Set the light value
+as `seo.color` in `ginko.config.ts` too: it fills the share cards. The accents of the Ginko templates:
+
+| Template | Light | Text on it | Dark | Text on it | Headings |
+|---|---|---|---|---|---|
+| starter | `#18181b` | `#ffffff` | `#f4f4f5` | `#18181b` | Inter |
+| blog | `#4f46e5` | `#ffffff` | `#a5b4fc` | `#1e1b4b` | Inter |
+| portfolio | `#1c1917` | `#ffffff` | `#f5f5f4` | `#1c1917` | Instrument Serif, `text-h3` 22–28 px |
+| company | `#0369a1` | `#ffffff` | `#7dd3fc` | `#082f49` | Inter |
+| saas | `#6d28d9` | `#ffffff` | `#c4b5fd` | `#2e1065` | Inter |
+| restaurant | `#c2410c` | `#ffffff` | `#fdba74` | `#431407` | Fraunces |
+| local-business | `#0f766e` | `#ffffff` | `#5eead4` | `#042f2e` | Inter |
+| nonprofit | `#15803d` | `#ffffff` | `#86efac` | `#052e16` | Inter |
+| events | `#be123c` | `#ffffff` | `#fda4af` | `#4c0519` | Inter |
+
+`.surface-primary` turns a band into the accent colour and swaps text, buttons and the focus ring, so everything in
+it keeps its contrast (used by `BlockCta`). A template may give the band its own colour with `--brand-surface` and
+`--brand-surface-foreground` in `main.css` (text on it ≥ 4.5:1). Use it in `.dark` when the dark accent is a light
+tint: a full-width band of it is the loudest surface on a near-black page. nonprofit: `#14532d` with `#f0fdf4`
+(8.7:1) in dark mode; buttons and links keep `#86efac`.
+
+Dark mode: `@nuxtjs/color-mode` puts `.dark` on `<html>` (first visit: the system setting); `dark:` utilities and
+`color-scheme` follow it. Printing always uses the light neutrals (paper is white). The navigation, notices, controls and closing band are left
+out (`print:hidden`); the footer prints only the name, address, email and phone, so any page prints as its content
+with whose it is.
+
+## Type
+
+Inter (variable, latin and latin-ext) through `@nuxt/fonts`, served from the site itself. A display face for headings
+is optional (`--font-heading`); a narrow one may set `--text-h3` larger in an `@theme` block of `main.css`, so titles
+still lead the body text (the portfolio). Right-to-left languages add their own face on `:lang(…)`.
+
+| Utility | Size | Line height |
+|---|---|---|
+| `text-h1` | `clamp(2.25rem, 1.5rem + 3.2vw, 4rem)` | 1.05, tracking −0.025em; one per page |
+| `text-h2` | `clamp(1.75rem, 1.35rem + 1.7vw, 2.75rem)` | 1.1, tracking −0.02em; sentences such as the `BlockCta` title |
+| `text-h3` | `clamp(1.2rem, 1.1rem + 0.45vw, 1.45rem)` | 1.3; section labels and `##` in Markdown |
+| `text-lead` | `clamp(1.125rem, 1.06rem + 0.3vw, 1.3125rem)` | 1.5 |
+| `text-body` | `1.0625rem` | 1.6 |
+| `text-small` | `0.9375rem` | 1.5 |
+| `text-xs` | `0.8125rem` | 1.4; the smallest size |
+
+Headings balance their lines and hyphenate (the page sets `lang`). Prices, times and dates use `tabular-nums`
+(`<time>` gets it by default). Text runs at most `max-w-prose` (43.5rem, about 65 characters of body text; in rem so the line width does not
+change when the web font replaces its fallback).
+
+## Space, size, radius, shadow
+
+| Token | Value | Use |
+|---|---|---|
+| `pt-section` (`--spacing-section`) | `clamp(3.5rem, 2.25rem + 5.5vw, 7rem)` | space above each section |
+| `px-gutter` (`--spacing-gutter`) | `clamp(1rem, 0.5rem + 2.4vw, 2rem)` | page edges (16 px on phones) |
+| `max-w-page` | `76rem` | page width |
+| `max-w-prose` | `43.5rem` | text width (about 65 characters) |
+| `rounded-md` (`--radius`) | `0.625rem` | buttons, controls |
+| `rounded-block` | `1rem` | images, cards, the CTA band |
+| `shadow-overlay` | one soft shadow | nav sheet, dialog, menus; nothing else |
+
+Tailwind's spacing steps (`p-4`, `gap-6`) stay available.
+
+## Focus and motion
+
+Every interactive element shows a 2px ring in `--ring`, 3px away (`:focus-visible` in `tokens.css`); components do
+not draw their own. Motion only for a change of state: 150 ms for colours, 200–300 ms for the sheet, accordion and
+dialog, `ease-out`. With `prefers-reduced-motion`, transitions and animations are switched off.
+
+## Components
+
+`app/components/ui/`: shadcn-vue components, copied with the shadcn-vue CLI and trimmed to these:
+
+| Component | Variants |
+|---|---|
+| `Button` | shadcn-vue's names: `default` (the main action), `outline`, `secondary`, `destructive`, `ghost`, `link`; sizes `default` (44 px), `sm` (36 px with a mouse, 44 px on touch), `lg` (48 px), `icon` (44 px), `icon-sm`, `icon-lg` |
+| `Sheet` | `side="start"` (default) or `end`: logical sides, so it opens from the right in right-to-left languages |
+| `Accordion` | as in shadcn-vue, on these tokens; only in templates with questions and answers (`BlockFaq`) |
+
+Nothing else until a feature needs it. To add one: `npx shadcn-vue@latest add <name>`, then:
+
+1. Change `import { cn } from 'cn'` to `import { cn } from '@/lib/utils'` and remove the `cn` package the CLI adds.
+2. Replace Tailwind default classes (`text-sm`, `shadow-lg`, `rounded-lg`, `bg-black/80`) with the tokens above. In
+   the browser they give no error, they just do nothing.
+3. Run `npm run lint` and `npm run typecheck`, and look at the component in light and dark. Lint fails on every class
+   the theme does not have (`eslint.tailwind.mjs`, which reads `main.css`). A class that is on purpose not Tailwind
+   (a hook for plain CSS) goes into the explicit list at the top of that file, with a comment saying why.
+
+Icons come from `@lucide/vue` (what the CLI installs; `lucide-vue-next` is deprecated).
+
+`cn` (`app/lib/utils.ts`) joins classes and resolves conflicts with tailwind-merge, as in shadcn: a
+`class="text-small"` on a component that sets `text-h3` wins. tailwind-merge is configured for the theme of
+tokens.css (`text-small`, `p-gutter`, `max-w-page`, `rounded-block`…); a new token in `@theme` gets its line there too.
+
+`app/components/site/`: `SiteHeader` (name or logo, up to 6 links, language switch, theme toggle; the links move into
+`SiteNavSheet` below `md`, or below `xl` when there are more than 4), `SiteFooter`, `SiteSkipLink`, `SiteLogo`,
+`SiteNavLink`, `SiteThemeToggle`, `SiteLanguageSwitch` (the same page in each language), `SiteNotice` (up to two
+notices above the header).
+
+`app/components/block/` and two more:
+
+| Component | Use |
+|---|---|
+| `BlockHero` | home only: the page's h1, a lead, one primary and one secondary action, an optional photo (16:9) |
+| `BlockPageHeader` | every other page: h1, lead, optional meta line |
+| `BlockSection` | a short label as heading (`text-h3`, the size of a Markdown `##`), optional lead, content; from `lg` heading 4 and content 8 of 12 columns, or full width |
+| `BlockCards` | 2–4 per row; the whole card is one link; photos 3:2 |
+| `BlockFeatures` | 2–6 items divided by lines, no cards |
+| `BlockCta` | a closing band on the accent; one per page, not on legal, contact or error pages |
+| `BlockEmpty` | an empty list: what to add, and where (`content/…`) |
+| `ProseBody` | a Markdown body (headings start at `##`); with `@lupinum/ginko-components` installed, its components too |
+| `InitialsAvatar` | a person without a photo: initials, never a stock face |
+
+## Page patterns
+
+- Home starts with `BlockHero`; other pages with `BlockPageHeader`.
+- Section titles are short labels without a full stop; hero and CTA titles are sentences.
+- Lists show the date or status a visitor needs, in tabular numbers.
+- Every image has a real width, height and alt text, and a fixed ratio per block, so nothing jumps while loading.
+- Right-to-left: only logical utilities (`ms-`, `pe-`, `start-`, `text-start`); arrows get `rtl:-scale-x-100`.
+
+## Patterns of the features
+
+In templates that have these features (`templates/_features/` in the Ginko repository):
+
+- **Open now** (`hours`): `HoursToday` says open or closed in words, the dot only repeats it. It stands above the h1 on
+  the home page, under the call and email buttons on a page for getting in touch, and at the top of the footer's
+  contact column on every page (`app/components/site/FooterStatus.vue`). Opening times never break inside a span:
+  a narrow screen breaks between "11:30–14:00 and" and "17:30–22:00".
+- **Where** (home): one quiet line under the hero's actions: a pin icon, the address, and an "Open in maps" link
+  (`text-small`, muted, the link at least 44 px tall). No embedded map.
+- **Getting in touch** (a reservations page): right under `BlockPageHeader`, one primary button (call) and one
+  secondary (email), `size="lg"`, full width below `sm`; the open-now line under them; text and the opening hours
+  below.
+- **A long list** (the menu): under the header, a row of links to its sections (`text-small`, accent, at least 44 px
+  tall), so a phone reaches the desserts in one tap; each section has an `id`.
+- **Reading** (`blog`): a post's date and reading time in one muted line under the lead, the authors with their
+  initials under it; tags as quiet bordered links (at least 44 px tall) after the text; the older and the newer post
+  as two bordered links side by side (stacked on phones). In a Markdown text, a photo's caption is an emphasised line
+  right under the image (`![Alt text](./photo.jpg)`, then `*The caption*` on the next line); long lines in code
+  blocks wrap.
+- **Photos on phones** (`gallery`): one column at full width, each photo 3:2; justified rows from `sm`.
+
+## Do and don't
+
+| Do | Don't |
+|---|---|
+| `text-muted-foreground` for secondary text | pick a grey by hand |
+| add a token to the CSS and this file | arbitrary values (`p-[13px]`, `bg-[#…]`) |
+| one primary button per view, one CTA band per page | the accent behind body text |
+| status with a word or an icon, plus colour | colour alone |
+| initials for people without a photo | stock faces for named people |

package/templates/events/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025-2026 Lupinum OG
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/templates/events/MEDIA.md

@@ -0,0 +1,32 @@
+# Media
+
+Photos and other media in this template, with their source and license. The code is MIT (see LICENSE); media keep
+their own license. People are shown with their initials, never with stock photos of faces.
+
+## Photos
+
+The [Unsplash License](https://unsplash.com/license) allows free use, also commercial, without asking; it does not
+allow selling the photos as they are or building a similar photo service.
+
+| File | Used in | What | Source | License |
+|---|---|---|---|---|
+| `public/media/hero.jpg` | home page (`content/home.md`) | a full conference hall seen from the back rows | [purzlbaum on Unsplash](https://unsplash.com/photos/men-and-women-sitting-on-chairs-inside-room-_wDZkpybAfY) | Unsplash License |
+| `public/media/talk.jpg` | last year's photos (`content/gallery.md`) | a speaker in front of a bright screen, the audience in silhouette | [typegon on Unsplash](https://unsplash.com/photos/audience-watching-speaker-on-bright-screen--NXNaE9lu6w) | Unsplash License |
+| `public/media/workshop-tables.jpg` | last year's photos | laptops, notebooks and cups on a long table, from above | [marvelous on Unsplash](https://unsplash.com/photos/people-sitting-down-near-table-with-assorted-laptop-computers-SYTO3xs06fU) | Unsplash License |
+| `public/media/coffee-break.jpg` | last year's photos | glasses of coffee on a wooden table | [john_tuesday on Unsplash](https://unsplash.com/photos/people-sitting-near-brown-wooden-table-xAGBuYFSbC8) | Unsplash License |
+| `public/media/venue.jpg` | page "Venue" (`content/pages/1.venue.md`) | a building with a facade of wooden slats against a blue sky | [mmpixz on Unsplash](https://unsplash.com/photos/brown-concrete-building-during-daytime-3cl6impBd_8) | Unsplash License |
+
+## Made for this template
+
+| File | What | License |
+|---|---|---|
+| `public/logos/kaltenegger-it.svg`, `nordlicht-hosting.svg`, `hallgarten-stiftung.svg`, `kanalcafe.svg` | wordmarks of fictional sponsors and partners, no real organisations | MIT, like the code |
+| `.github/screenshots/home-light.png`, `home-dark.png` | screenshots of this template | MIT, like the code |
+
+The share cards (1200 × 630) are generated by the site (nuxt-og-image) with Inter
+([SIL Open Font License](https://openfontlicense.org)).
+
+When you add a photo, put it in `public/media/`, give it alt text in every language file that shows it, and add a
+row here. The sample photos are stock photos of other events and another building. Replace them with photos of your
+own conference and venue (people only with their permission). A speaker needs no photo: without one the site shows
+their initials.

package/templates/events/NOTES.md

@@ -0,0 +1,13 @@
+# Notes before release
+
+- Sample data that must change before going live: `content/site.md` (the association "Verein Open Data Days" at
+  Seidenhofgasse, phone numbers whose local part starts with 0), the venue "Kulturhaus am Kanal, Schiffmeistergasse 12"
+  (an invented address), the ticket shop address (`tickets.opendatadays.example`), the email addresses
+  (`opendatadays.example`), the speakers (fictional people), the sessions, the sponsor logos (fictional), and the legal texts
+  (marked placeholders for Austria).
+- The photos are stock placeholders (Unsplash License, `MEDIA.md`), to be replaced by better-fitting ones before release.
+- The past event `content/events/3.last-edition.md` stays in the content as a record; the site never shows it (an
+  event leaves the site after its last day). It shows how a finished event looks in the files and in the Studio.
+- German says "Sie" on every page.
+- The Studio jobs of this template (gate 7: change a session's time, room or status on a phone; post a notice) come
+  later in `templates/_studio/events/`.

package/templates/events/README.md

@@ -0,0 +1,247 @@
+# Events
+
+A complete website for a conference, a festival or a community event over one or more days: the dates, the place
+with a link to the map and the ticket link on the first screen, the programme by day with time, room, speakers and
+"sold out" or "cancelled", a page per speaker, "now and next" on the home page during the event, questions and
+answers, sponsor logos, photos of last year, and legal texts. In English and German, with light and dark mode. Built
+with [Nuxt](https://nuxt.com) and [Ginko](https://github.com/lupinum-dev/ginko). All content is Markdown in
+`content/`; the site needs no account and no database. The sample is "Open Data Days", a two-day community
+conference about open data in Vienna.
+
+| Light | Dark |
+|---|---|
+| ![The events template's home page in light mode](.github/screenshots/home-light.png) | ![The events template's home page in dark mode](.github/screenshots/home-dark.png) |
+
+## Quick start
+
+```bash
+npm create ginko@latest my-site -- --template events
+```
+
+This copies the template into `my-site`, keeps the languages you choose (`--locales en,de` for English and German,
+`--locales de,en` for German first, `--locales en` for English only), moves the sample dates to this week (the
+conference stays a few weeks ahead), sets the site id and writes a `.env` with a new `NUXT_APP_SECRET`. Then:
+
+```bash
+cd my-site
+npm install
+npm run dev
+```
+
+Or copy the folder as it is, with both languages, through Nuxt's own command:
+
+```bash
+npm create nuxt@latest my-site -- -t github:lupinum-dev/ginko/templates/events#release
+```
+
+Copy `.env.example` to `.env` and fill in `NUXT_APP_SECRET` (see below). The `#release` branch follows the latest
+Ginko release, so both commands give you the same files. With this route the sample dates stay as they are: move
+them yourself (see "Dates and times").
+
+## Deploy
+
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Flupinum-dev%2Fginko%2Ftree%2Frelease%2Ftemplates%2Fevents&env=NUXT_APP_SECRET&envDescription=Signs%20the%20share%20card%20URLs.%20Any%2032%20or%20more%20random%20characters.)
+
+Any host that runs Node works: `npm run build` writes a server to `.output/`, started with
+`node .output/server/index.mjs`. Set these variables where the site runs:
+
+| Variable | What |
+|---|---|
+| `NUXT_APP_SECRET` | Signs the URLs of the share cards. 32 or more random characters (`openssl rand -hex 32`). |
+| `NUXT_PUBLIC_SITE_URL` | The address of the live site, for example `https://www.open-data-days.org`. On Vercel the production address is used when this is not set. |
+
+A build on Vercel stops with a message while the address is still `example.com`, so search engines never see wrong
+links. Other builds (CI, your computer) only print a warning.
+
+The site runs as a server, not as static files: a session leaves the programme the day after it took place, an event
+the day after its last day, a notice the day after its `until`, and "now and next" follows the clock, all with no new
+build. Static files (`npm run generate`) would keep the old state until the next build.
+
+## Develop, build, preview
+
+| Command | What |
+|---|---|
+| `npm run dev` | the site with live reload on http://localhost:3000 |
+| `npm run check` | Checks the content files in a few seconds: missing or wrong fields, dates, prices, links between pages and files in `public/`. Each problem names the file and the field. |
+| `npm run build` | the production build in `.output/` |
+| `npm run preview` | runs that build locally |
+| `npm run lint` | ESLint |
+| `npm run typecheck` | TypeScript and Vue types |
+
+`.github/workflows/ci.yml` runs lint, typecheck and build on every push. It needs no settings.
+
+## Edit content
+
+Every text is a Markdown file. The main language has no suffix (`welcome.md`); a translation adds the language code
+(`welcome.de.md`) and repeats only the texts: dates, times, rooms, speakers, prices and photos come from the main
+file. The number at the start of a file name sets the order. Files point to other entries by id: the folder and the file
+name without number and language, so `content/people/1.lena-hofer.md` is `people/lena-hofer`. The `slug` is only the
+address on the site: renaming a file breaks the references to it, changing the `slug` does not. Write dates as
+`2026-10-24`, times as `'09:30'`, prices as a plain number in euros (`95` or `12.50`). After each change, run
+`npm run check`.
+
+| On the site | File |
+|---|---|
+| Home page: title, lead, photo | `content/home.md` (and `home.de.md`) |
+| The conference and other dates: title, days (`when`), `start` (first day), `end` (last day), `location`, `price`, `booking` (the ticket shop), `bookingUntil` (the last day of ticket sales), `soldOut`, `draft: true` (not on the site yet, with its sessions), the text | `content/events/<n>.<name>.md`; the home page shows the first coming event that has sessions, and an event leaves the site after its last day. `4.next-edition.md` is a sample draft for next year: edit it for your next edition instead of adding a new file |
+| The programme: one file per session with `event` (`events/open-data-days`), `date`, `from`, `to`, `title`, `summary` (one or two sentences: what it is about, who it is for), `room`, `speakers` (`[people/lena-hofer]`), `status` (`open`, `soldOut` or `cancelled`) | `content/sessions/<name>.md`; the translation holds only the `title` and `summary`; "From the programme" on the home page shows the next sessions that have a summary |
+| Speakers: `name`, `slug` (the address), `role`, `bio`, `photo` (optional; without one the site shows initials) | `content/people/<n>.<name>.md`; the number sets the order on the speakers page and the home page (the first four) |
+| Questions and answers | `content/faq/<n>.<name>.md`: `question`, `answer`; the home page shows the first three |
+| Sponsor and partner logos | `content/logos/<n>.<name>.md`: `name`, `image` (an SVG or PNG in `public/logos/`), `url` |
+| Photos of last year | `content/gallery.md` and the alt texts in each translation. A translation lists the rows in the same order as the main file: when you add, remove or move a row in the main file, do the same at the same place in each translation (write `- {}` for a row with nothing to translate). `npm run check` reports a translation with a different number of rows. |
+| Venue, code of conduct, sponsoring and other pages | `content/pages/<n>.<name>.md`; each translation sets its own address with `slug:` |
+| Notices above the header ("Ticket sales end three days before the conference") | `content/notices/<n>.<name>.md`: `text` (at most 140 characters; in quotes when it contains a colon) and `until` (the last day it shows, like `2026-12-31`; without it the notice stays until you delete the file); a translation has only `text` |
+| Name, address, register number, email, phone of the organiser (footer, imprint, search engines) | `content/site.md` |
+| Privacy policy, terms, imprint | `content/legal/` (placeholders for Austria: replace them before you go live) |
+| Site name, description for search engines, time zone, country | `ginko.config.ts` (`name`, `seo.description`, `timeZone`, `country`) |
+| Menu, footer links, the line under the name in the footer | `app/app.config.ts` |
+| Rename the event or move it | the name: `name` and `seo.description` in `ginko.config.ts`, `title` in `content/home*.md`, the titles in `content/events/`, the summary of `content/pages/2.code-of-conduct*.md`; the place: `seo.description`, `lead` in `content/home*.md`, `home.title` in `i18n/<language>.json`, the tagline in `app/app.config.ts`, `location` in every file of `content/events/`, `content/pages/1.venue*.md`, `timeZone` in `ginko.config.ts`. `content/site.md` is the organiser's own address and changes only if the organiser changes. |
+| Texts of the home page sections and the FAQ page; the page titles and leads of the programme, speakers and dates | `i18n/<language>.json`; the features' own texts are in `i18n/<feature>/<language>.json`, and a key set in `i18n/<language>.json` wins (as `events.book` = "Get tickets" there does) |
+
+**A session moves or changes.** Change `from`, `to`, `room` or `status` in its main file
+(`content/sessions/<name>.md`). If the session is now the first or the last of the event, also change `start` or `end`
+in the event's file (`content/events/<n>.<name>.md`): the home page shows those times. A room the venue page does not
+list yet goes into `content/pages/1.venue.md` and its translation. The programme, the speaker pages, "now and next",
+the event page and the data for search engines all read that one file, so they cannot disagree. Write a room's name
+only in the main file, never in a translation: a room is a name on a sign (Festsaal, Studio), and a second copy in
+another language would stay behind when the room changes. `status: soldOut` shows "Sold out", `status: cancelled` shows
+"Cancelled"; a cancelled session stays in the programme, so people who planned to go see it, but never shows under
+"now" or "next".
+
+**Dates and times.** All times are in the site's time zone (`timeZone: 'Europe/Vienna'` in `ginko.config.ts`), as they
+are on the printed programme; search engines get them with the right offset for summer or winter time. A session leaves
+the programme the day after its `date`. On days that have sessions the home page puts "now and next" right below the
+dates and the place (without the lead and the photo): the sessions running now and the ones that start next, as of the
+minute the page was loaded, and it moves on every minute while the page is open. The programme page then says "Now"
+next to the running sessions and greys out the finished ones. `start` in the event's file is the time of the first day
+and `end` of the last one: a two-day event shows "Thu 09:00 – Fri 16:00". A session's `date` must lie within its
+event's `when`: when you move the event, move its sessions too. `npm run check` does not catch a session outside its
+event yet.
+
+**Tickets.** The site sells nothing: `booking` in the event's file is the address of your ticket shop, and "Get
+tickets" leads there: on the home page, in the closing band with the price, on the programme and on the event page.
+`bookingUntil` is the last day of ticket sales; after it the links give way to "Ticket sales have ended", and the
+programme becomes the main button. When the event is full, set `soldOut: true`: the button gives way to "Fully
+booked". An event without `booking` shows the organiser's phone and email instead.
+
+Notices show newest first. Give a new notice a smaller number than the others: `0.` works and numbers may have gaps, so
+older notices keep theirs. At most two show at once.
+
+## Make it yours
+
+- **Name.** `name` in `ginko.config.ts` (header, footer, share cards, search engines). The sample name and place also
+  appear as text in other files: "Rename the event or move it" under [Edit content](#edit-content) lists them.
+  `legalName` in `content/site.md` is the organiser's legal name (sample: Verein Open Data Days). Search `content/` and
+  `i18n/` for the name and the place and replace what is left.
+- **Menu.** `nav` in `app/app.config.ts` holds at most six items: a page of
+  `ginko.config.ts` (`{ page: 'programme', label: { … } }`, label per language, the same words as the page's title) or
+  a page of `content/pages/` by id (`{ entry: 'pages/venue' }` is `content/pages/1.venue.md`).
+- **Logo.** Put the file in `public/` and set `logo: { src: '/logo.svg', width: 120, height: 32 }` in
+  `app/app.config.ts`. Without it, the header shows the name.
+- **Colour.** `--brand` and `--brand-foreground` in `app/assets/css/main.css`, once for light and once for dark
+  (`.dark`); in `.dark` also `--brand-surface` and `--brand-surface-foreground` (the closing band); and the light value
+  as `seo.color` in `ginko.config.ts` (the background of the share cards). This template uses rose (`#be123c`, dark
+  `#fda4af`). Text on the colour needs a contrast of at least 4.5:1 in both modes; check each pair with a contrast
+  checker (for example webaim.org/resources/contrastchecker). `DESIGN.md` has the rules.
+- **Fonts.** `--font-body` in `main.css`. `@nuxt/fonts` downloads the fonts at build time and serves them from your
+  site.
+- **Organisation type.** `organization: 'Organization'` in `app/app.config.ts` tells search engines what you are;
+  address and contact come from `content/site.md`, the country from `country` in `ginko.config.ts`.
+- **Addresses.** The words of the addresses per language (`programme` → `programm`, `speakers` → `vortragende`) are in
+  `app/routes.ts`. Change a word there; the pages, the menu and the links follow.
+
+`DESIGN.md` explains the tokens and components. The parts in `app/components/ui/` are
+[shadcn-vue](https://www.shadcn-vue.com) components.
+
+## Add a page
+
+**A text page:** add `content/pages/4.travel-grants.md` with a `title`, an optional `summary` and the text below the
+frontmatter. It appears at `/travel-grants`; each translation sets its own address with `slug:` (`slug: reisekosten`
+in `4.travel-grants.de.md` gives `/de/reisekosten`). Add `{ entry: 'pages/travel-grants' }` to `nav` or `footer` in
+`app/app.config.ts` to link it.
+
+**A page with its own layout:** add a Vue file in `app/pages/`, for example `app/pages/workshops.vue`. Start it with
+`<BlockPageHeader>` and call `usePageSeo()`, like `app/pages/faq.vue`. Register it in `ginko.config.ts` under `pages`
+(`workshops: localized('/workshops')`) and add the words of its address per language to `segments` in
+`app/routes.ts` (`workshops: { en: 'workshops', de: 'workshops' }`). It then answers at `/workshops` and
+`/de/workshops`, and `useGinkoPath()('workshops')` links to it.
+
+## Add or remove a language
+
+The languages are the `locales` list in `app/routes.ts`; the first is the main language, whose addresses have no
+prefix.
+
+- **Remove one:** start fresh with `npm create ginko@latest my-site -- --template events --locales en`, or delete it
+  from `locales` and from the maps in `app/routes.ts` and `languages` in `ginko.config.ts`, then delete its files
+  (`*.de.md`, `i18n/de.json`, `i18n/*/de.json`).
+- **Add one** (for example Italian): add `'it'` to `locales` and a word per address in `app/routes.ts`, its tag to
+  `languages` in `ginko.config.ts` (`it: 'it-IT'`), and the Italian labels of `nav`, `footer` and `tagline` in
+  `app/app.config.ts` (without them they show in the main language). Add `i18n/it.json` and the texts of every
+  `i18n/<feature>/en.json` translated as `i18n/<feature>/it.json`.
+- **Translate the content** as `content/**/*.it.md`. A session needs only its `title`; a speaker their `role` and
+  `bio`. A page, legal text or event shows in the new language only once it has its translation file: without one
+  it is not on the Italian site, the menu leaves it out, and links to it lead to its page in the main language.
+  Translate at least the legal texts (`content/legal/`) before the language goes live.
+
+## Tickets, registration and contact forms
+
+The site sends no data to other companies, so it has no forms and takes no payments. "Get tickets" leads to your
+ticket shop (`booking` in the event's file); a registration or call for proposals works the same way: link to a form
+service of your choice from a page. Name these services in your privacy policy. The venue page links to OpenStreetMap
+instead of embedding a map, so no map loads from another company.
+
+## Remove a feature
+
+Links in the content name pages by their key (`[questions page]($page.faq)`). After you remove a page, search
+`content/` for `$page.<key>` and remove or change those links: the build stops on a link that leads nowhere.
+
+| Feature | Delete |
+|---|---|
+| Programme and speakers | `content/sessions/`, `content/people/`, the `sessions` and `people` bricks, their imports and `pages.programme` and `pages.speakers` in `ginko.config.ts`, their `nav` items in `app/app.config.ts`; in `app/pages/index.vue` "Now and next", "From the programme" and "Speakers" with `rows`, `state`, `at`, `highlights` and `people`, `onEventDay` (also in the "booking closed" line; the hero then always has its lead and photo) and the hero's "Programme" button (`programme`: the tickets are the main button, else the venue, and the venue is the second button only with tickets), and `event` becomes the first of `events`; the `sessions` block in `i18n/<language>.json` and the `home.programme`, `home.highlights` and `home.speakers` texts, `app/pages/programme.vue`, `app/pages/speakers/`, `app/components/session/`, `app/components/event/Programme.vue`, `app/composables/useSessions.ts`, `app/utils/sessions.ts`, `i18n/sessions/`, and `"sessions"` in `package.json` → `ginko.features`; the home page then shows the next event |
+| Questions and answers | `content/faq/`, the `faq` brick, its import and `pages.faq` in `ginko.config.ts`, its `nav` item in `app/app.config.ts`, "Questions" on the home page, `app/pages/faq.vue`, `app/components/block/Faq.vue`, `app/components/ui/accordion/`, `"faq"` in `ginko.features`; the link to `$page.faq` in `content/pages/1.venue*.md` |
+| Sponsor logos | `content/logos/`, `public/logos/` and its row in `MEDIA.md`, the `logos` brick and its import in `ginko.config.ts`, "Sponsors and partners" on the home page, `app/bricks/logos-quotes.ts`, `app/components/block/Logos.vue`, `Quote.vue`, `"logos-quotes"` in `ginko.features`; and the Sponsoring page (`content/pages/3.sponsoring*.md`, its `footer` item in `app/app.config.ts`) if you want none |
+| Last year's photos | `content/gallery*.md`, `public/media/talk.jpg`, `workshop-tables.jpg`, `coffee-break.jpg` and their rows in `MEDIA.md`, the `gallery` brick and its import in `ginko.config.ts`, "Last year" on the home page, `app/components/block/Gallery.vue`, `app/components/site/Lightbox.vue`, `i18n/gallery/`, `"gallery"` in `ginko.features` |
+| Notices | `content/notices/`, the `notices` brick and its import in `ginko.config.ts`, `<SiteNotice />` in `app/layouts/default.vue`, `app/components/site/Notice.vue` |
+| A language | see "Add or remove a language" |
+| Dark mode | `<SiteThemeToggle />` in `app/components/site/Header.vue`, `app/components/site/ThemeToggle.vue`, and `@nuxtjs/color-mode` with its `colorMode` options in `nuxt.config.ts` and `package.json` |
+| Share cards | `nuxt-og-image` and `@takumi-rs/core` in `nuxt.config.ts` and `package.json`; then `NUXT_APP_SECRET` is not needed |
+
+The dates (`content/events/`, the events list and the event pages) are the core of this template: keep them.
+
+## Before you deploy
+
+- [ ] `NUXT_PUBLIC_SITE_URL` (or `url` in `ginko.config.ts`) is your real address.
+- [ ] `NUXT_APP_SECRET` is set where the site runs.
+- [ ] `content/site.md` shows the organiser's real name, address, register number and contact details.
+- [ ] The event in `content/events/` has your dates, place and the address of your ticket shop in `booking`.
+- [ ] The sample draft `4.next-edition.md` and its session `next-edition-keynote.md` are yours or deleted.
+- [ ] `npm run check` ends with OK.
+- [ ] The sample sessions, speakers, questions, sponsor logos and photos are replaced or deleted; speakers' names,
+      roles and photos only with their permission.
+- [ ] The placeholders in `content/legal/` are replaced by your own texts, and the ones you do not need are deleted.
+- [ ] The sample phone numbers and emails are replaced: they reach nobody (the numbers start their local part
+      with 0, the emails end in .example), so a forgotten one fails quietly.
+- [ ] Every photo you added has alt text in each language and a source in `MEDIA.md`.
+
+## Move to the Studio
+
+Ginko Studio is Lupinum's hosted editor: during the event, someone on the team moves a session, changes its room or
+marks it sold out or cancelled from their phone in a few taps, and it is right on every page at once; notices end by
+themselves, and the Today page shows the next event and how many speakers have no bio yet. It is
+open by invitation, and Lupinum moves your content with you. The site stays the same code: each brick in
+`ginko.config.ts` loses its `source: 'files'`, and its content then comes from the Studio. Until then, everything here
+works without it. Ask at [lupinum.com](https://lupinum.com).
+
+## Updating
+
+Move all Ginko packages to the same version in one step:
+
+```bash
+npm install @lupinum/ginko@latest @lupinum/ginko-content@latest @lupinum/ginko-i18n@latest
+```
+
+The release notes list "Template files changed": compare those files with yours if you want the changes.
+
+## License
+
+Code: MIT (see `LICENSE`). Media: see `MEDIA.md`.

package/templates/events/app/app.config.ts

@@ -0,0 +1,30 @@
+import type { SiteAppConfig } from './composables/useSiteAppConfig'
+
+// The brand and navigation of the site. The name is `name` in ginko.config.ts; colours and fonts are in
+// app/assets/css/main.css; address and contact are in content/site.md.
+export default defineAppConfig({
+  site: {
+    // logo: { src: '/logo.svg', width: 120, height: 32 },
+    // One line under the name in the footer, per language.
+    tagline: {
+      en: 'A community conference about open data in Vienna.',
+      de: 'Eine Community-Konferenz über offene Daten in Wien.',
+    },
+    organization: 'Organization',
+    // At most 6. A page of ginko.config.ts (`page`, with its label per language; keep it the same as the page's
+    // title) or an entry of content/pages/ by id (`pages/<file name without number>`).
+    nav: [
+      { page: 'programme', label: { en: 'Programme', de: 'Programm' } },
+      { page: 'speakers', label: { en: 'Speakers', de: 'Vortragende' } },
+      { entry: 'pages/venue' },
+      { page: 'faq', label: { en: 'FAQ', de: 'Fragen' } },
+    ],
+    footer: [
+      { page: 'events', label: { en: 'Dates', de: 'Termine' } },
+      { entry: 'pages/code-of-conduct' },
+      { entry: 'pages/sponsoring' },
+    ],
+    // For example { label: 'Mastodon', url: 'https://mastodon.social/@opendatadays' }.
+    socials: [],
+  } satisfies SiteAppConfig,
+})

package/templates/events/app/app.vue

@@ -0,0 +1,7 @@
+<!-- Synced from templates/_features/site/app/app.vue by `pnpm templates sync`. Edit the source, not this copy. -->
+<template>
+  <NuxtRouteAnnouncer />
+  <NuxtLayout>
+    <NuxtPage />
+  </NuxtLayout>
+</template>

package/templates/events/app/assets/css/main.css

@@ -0,0 +1,22 @@
+@import "tailwindcss";
+@import "tw-animate-css";
+@import "./tokens.css";
+
+/* This template's accent and fonts (DESIGN.md "Your accent"). Everything else comes from tokens.css.
+   events: rose. White on the accent 6.3:1 light; the accent on the page 6.3:1 light; #4c0519 on the dark accent
+   8.3:1; the dark accent on the page 10.4:1. The focus ring and links in text use the accent. */
+:root {
+  --brand: #be123c;
+  --brand-foreground: #ffffff;
+  /* @nuxt/fonts serves Inter from the site and adds size-matched fallbacks. */
+  --font-body: "Inter", ui-sans-serif, system-ui, sans-serif;
+}
+
+.dark {
+  --brand: #fda4af;
+  --brand-foreground: #4c0519;
+  /* The closing band in dark mode: a deep rose instead of the light accent, so it does not outshine the page.
+     #fff1f2 on #881337 8.7:1. */
+  --brand-surface: #881337;
+  --brand-surface-foreground: #fff1f2;
+}