Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
113 changes: 30 additions & 83 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,22 +51,15 @@ This project uses Hugo's **native Tailwind CSS processing** without PostCSS or N

### Data-Driven Content Model

Conference content is stored in **YAML data files** (`data/*.yml`), not Markdown frontmatter:
Conference content is stored in **YAML data files** (`data/*.yml`), not Markdown frontmatter. Two kinds of content come from external services instead, fetched at build time with `resources.GetRemote`:

**`data/speakers.yml`**
- Speaker profiles: id, name, title, company, bio, photo, keynote flag, social links
- Accessed: `.Site.Data.speakers`
- Keynotes: `where .Site.Data.speakers "keynote" true`
**Sessions and speakers: Sessionize**
- Source of truth: Sessionize. Pages embed the Sessionize widgets (`/schedule/`, `/grid/`, `/speakers/`)
- `params.sessionizeApiUrl` points to the JSON "All data" endpoint
- `layouts/partials/sessionize-data.html` normalises it (sessions with Europe/Dublin RFC 3339 times, room, speaker ids; speakers with tagline, bio, photo, links). Use with `partialCached`
- There is no `data/speakers.yml` / `data/sessions.yml` / `data/schedule.yml` any more: edit the programme in Sessionize and redeploy

**`data/sessions.yml`**
- Talk details: id, title, description, speaker_ids (array), type, duration, track
- Types: keynote, talk, break, lightning, ceremony
- Linked to speakers via `speaker_ids`

**`data/schedule.yml`**
- Multi-day, multi-track schedule grid
- Structure: `days[].slots[]` with time, type, session_ids, tracks, duration
- References sessions by ID
**Ticket prices: Tito** (see `layouts/partials/tito-data.html`)

**`data/sponsors.yml`**
- Sponsor tiers: Platinum, Gold, Silver, Community
Expand Down Expand Up @@ -95,19 +88,17 @@ The site implements **comprehensive JSON-LD schemas** across three layers:
- WebSite schema: Site metadata
- BreadcrumbList schema: Navigation hierarchy for interior pages

**Layer 2: Speakers (`layouts/partials/structured-data-speakers.html`)**
- ItemList schema: All speakers with position indexing
- Person schemas: Individual speaker profiles with `performerIn` property
- Bidirectional linking: Speaker → talks, talks → speakers
- Dedicated schemas for keynote speakers with expertise tags
**Layer 2: Speakers (`layouts/partials/structured-data-speakers.html`)**, built from Sessionize
- ItemList of Person nodes (name, tagline as `jobTitle`, bio, photo, `sameAs` links)
- `performerIn` links each speaker to their sessions

**Layer 3: Schedule (`layouts/partials/structured-data-schedule.html`)**, built from Sessionize, on `/schedule/` and `/grid/`
- One EducationEvent (schema.org has no "EducationalEvent") per accepted session in an `@graph`: exact `startDate`/`endDate`, room as `location` (venue `address`, `containedInPlace` the venue), `performer` references, `superEvent` → main event
- The homepage Event also lists all speakers as `performer`

**Layer 3: Schedule (`layouts/partials/structured-data-schedule.html`)**
- EducationalEvent schema: Each talk/keynote with precise timing
- EventSeries schema: Full conference schedule
- `superEvent` hierarchy: Links sessions to main event
- ISO 8601 dates/durations (e.g., `PT30M` for 30 minutes)
**Key Pattern:** Use `@id` for cross-references: speakers are `{{ site.BaseURL }}speakers/#<sessionize speaker id>`, sessions `{{ site.BaseURL }}schedule/#session-<sessionize session id>`. Build JSON-LD objects with `dict` + `jsonify | safeJS` rather than string templating, so titles and bios are escaped correctly.

**Key Pattern:** Use `@id` for cross-references (e.g., `{{ .Site.BaseURL }}speakers/#{{ $speaker.id }}`). This enables Google Knowledge Graph integration.
**Time zone:** Dublin is on GMT (`+00:00`) in November, IST (`+01:00`) in summer. `eventStartDate`/`eventEndDate` in `hugo.toml` must carry the right offset.

**Documentation:** See `docs/STRUCTURED-DATA.md` for complete schema details and validation instructions.

Expand Down Expand Up @@ -140,15 +131,14 @@ The site implements **comprehensive JSON-LD schemas** across three layers:
- `layouts/partials/tickets.html` — Tito ticket widget. The `js.tito.io` script is loaded from `head.html` on the homepage only (not site-wide). Tito's script resets the scroll position on `popstate`, so same-page anchor links are handled in `nav.html` with `pushState`
- `layouts/partials/tito-data.html` — Fetches ticket names, prices and sale state from Tito at build time (use with `partialCached`)
- `layouts/partials/stats.html` — Animated statistics counters
- `layouts/partials/keynotes.html` — Featured keynote speakers
- `layouts/partials/speaker-card.html` — Reusable speaker card component
- `layouts/partials/sessionize-data.html` — Fetches sessions and speakers from Sessionize at build time (use with `partialCached`)
- `layouts/partials/discover-dublin.html` — "Discover Dublin" section with gallery, top things to do, and transport info
- `layouts/partials/cta-newsletter.html` — Newsletter signup with social links (not active — no newsletter service configured yet)
- `layouts/partials/css.html` — Deferred CSS rendering with Tailwind processing

**Homepage composition (`layouts/index.html`):**
Active: Hero → About → Stats → Venue → Discover Dublin
Commented out (pending content): Keynotes, Sponsors, Tickets, Newsletter CTA
Active: Hero → key facts bar (date, venue, ticket prices) → About → Sponsors → Venue → Key questions → Tickets (Tito widget) → Discover Dublin
Commented out (pending content): Stats, Newsletter CTA

### Configuration (`hugo.toml`)

Expand Down Expand Up @@ -199,48 +189,9 @@ text-heading: #f1f5f9

## Content Management

### Adding Speakers

Edit `data/speakers.yml`:
```yaml
- id: "speaker-slug"
name: "Full Name"
title: "Job Title"
company: "Company Name"
bio: "Biography text"
photo: "/img/speakers/photo.jpg" # or placeholder.svg
keynote: true # or false
social:
twitter: "https://twitter.com/handle"
github: "https://github.com/username"
linkedin: "https://linkedin.com/in/username"
```

Structured data will auto-generate for new speakers.

### Adding Sessions/Talks

Edit `data/sessions.yml`:
```yaml
- id: "talk-slug"
title: "Talk Title"
description: "Detailed description"
speaker_ids: ["speaker-slug"] # Array, can have multiple
type: "talk" # or "keynote", "lightning", "workshop"
duration: 30 # minutes
track: "track-1" # or "main" for plenary
```

Then add to schedule in `data/schedule.yml`:
```yaml
- time: "14:00"
type: "session"
session_ids: ["talk-slug"]
tracks: ["track-1"]
duration: 30
```
### Adding Speakers and Sessions

EducationalEvent schemas will auto-generate with correct dates/times.
Speakers, sessions, rooms and times are managed in **Sessionize**. After a change there, trigger a new deploy so the JSON-LD (built from `params.sessionizeApiUrl`) picks it up; the embedded widgets update on their own.

### Adding Blog Posts

Expand Down Expand Up @@ -291,24 +242,20 @@ Commit message style:
### Accessing Data Files in Templates

```go
{{ range .Site.Data.speakers }}
{{ .name }} — {{ .company }}
{{ end }}

{{ $keynotes := where .Site.Data.speakers "keynote" true }}

{{ range where .Site.Data.sessions "type" "talk" }}
{{ .title }}
{{ range hugo.Data.sponsors.tiers }}
{{ .name }}
{{ end }}
```

### Linking Sessions to Speakers
### Sessions and Speakers from Sessionize

```go
{{ range .speaker_ids }}
{{ $speakerId := . }}
{{ range where $.Site.Data.speakers "id" $speakerId }}
<p>{{ .name }}</p>
{{ $sz := partialCached "sessionize-data.html" . }}
{{ if $sz.ok }}
{{ range $sz.sessions }}
<p>{{ .start }} {{ .title }}:
{{ range $i, $id := .speakers }}{{ if $i }}, {{ end }}{{ index $sz.speakerNames $id }}{{ end }}
</p>
{{ end }}
{{ end }}
```
Expand Down
2 changes: 1 addition & 1 deletion content/venue/_index.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
---
title: "Venue: Confirmed"
title: "Venue"
description: "PyCon Ireland 2026 will take place on 21 November at Chartered Accountants House, on Dublin's Pearse St."
---
53 changes: 0 additions & 53 deletions data/schedule.yml

This file was deleted.

74 changes: 0 additions & 74 deletions data/sessions.yml

This file was deleted.

62 changes: 0 additions & 62 deletions data/speakers.yml

This file was deleted.

3 changes: 3 additions & 0 deletions docs/STRUCTURED-DATA.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# Structured Data (JSON-LD) - Implementation Guide

> **Update (November 2026):** the speaker and schedule schemas are now generated from the Sessionize JSON endpoint (`params.sessionizeApiUrl`, see `layouts/partials/sessionize-data.html`). `data/speakers.yml`, `data/sessions.yml` and `data/schedule.yml` were removed, and the `EventSeries` block was dropped. Sections below that refer to those files or to `+01:00` offsets describe the former setup; `CLAUDE.md` is the up-to-date reference.


## 📋 Vue d'Ensemble

Le site PyCon Ireland 2026 implémente des schémas JSON-LD complets pour améliorer le référencement et activer les rich snippets dans les résultats de recherche Google.
Expand Down
5 changes: 3 additions & 2 deletions hugo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,8 @@ enableGitInfo = true
eventDate = "2026-11-21"

# Event dates in ISO 8601 format (for structured data)
eventStartDate = "2026-11-21T09:00:00+01:00"
eventEndDate = "2026-11-21T18:00:00+01:00"
eventStartDate = "2026-11-21T09:00:00+00:00" # Dublin is on GMT (UTC+0) in November
eventEndDate = "2026-11-21T19:05:00+00:00" # End of the last session (Lightning Talks) in Sessionize

# Venue information
venue = "Chartered Accountants House"
Expand All @@ -56,6 +56,7 @@ enableGitInfo = true
cfpUrl = "https://sessionize.com/pycon-ireland-2026/"
cfpOpens = "2026-05-25"
cfpCloses = "2026-08-30"
sessionizeApiUrl = "https://sessionize.com/api/v2/k10qao8b/view/All" # JSON "All data" endpoint; sessions/speakers JSON-LD is built from it at build time
ticketsUrl = "https://ti.to/python-ireland/pycon-ireland-2026" # Tito event URL; ticket names, prices and availability are fetched from Tito at build time
ticketsValidFrom = "2026-10-01" # Date pricing tiers were announced; required by Google's Offer.validFrom check

Expand Down
Loading
Loading