Skip to content

feat: 2027 homepage, Why Q audience pages, ticket page polish - #55

Open
Kiron-Q-Summit wants to merge 5 commits into
mainfrom
feat/homepage-2027
Open

Kiron-Q-Summit wants to merge 5 commits into
mainfrom
feat/homepage-2027

Conversation

@Kiron-Q-Summit

Copy link
Copy Markdown
Collaborator

What changes

Homepage for the 10th edition (apps/web/DESIGN.md HOME-1)

  • Video hero with badge, lead lines, a neon countdown to the first conference day (Europe/Berlin, always recomputed from the clock) and a transparent liquid glass Buy Now. The film dissolves into the page without a visible edge; the flat black veil over it is gone.
  • Key figures on one glass pane, partner logo rows from edge to edge, four audience tiles, speaker highlights (alumni plus lineup stand-ins; no face is covered by a tag or a name card), and a LinkedIn and Instagram section that shows the newest four posts, newest at the left.
  • Floating glass Qs behind the page. The FAQ section is no longer on the homepage.

Why Q?

  • The overview page is gone. /whyq/ redirects (302) to the audience tiles on the homepage (/#why-attend); the header item is one button that opens the four audience pages (/whyq/students/, /whyq/startups/, /whyq/corporates/, /whyq/investors/) as a dropdown on desktop and in place in the phone sheet, with keyboard support and a no-JS fallback.
  • llms.txt and llms-full.txt list the four audience pages instead of the overview.
  • /program/ stays offline (302 to the homepage), as before.

Ticket page

  • The glass Q render replaces the drawn Q bubbles; no text lies over it and all tickets keep the same size.
  • No typewriter effect, no Qs behind the page.
  • Resting glass panels no longer blur their backdrop on every frame, which removed the stutter on integrated graphics.

CMS (separate commit)

  • page-home: new optional fields (hero badge and lead lines, countdown wording, partner band heading, audience tiles with link and image, speaker highlights, lineup, stand-ins, social section with a post list of up to twelve rows; the site shows the newest four).
  • site-settings: nav items may carry sub-items.
  • Additive migration 20261111_104849_home_2027.

Release order (do not merge before the content step can follow)

Production reads its content from the CMS, and the new fields exist there only after this is merged. Until the content is published, the live homepage renders with the old copy and without countdown, tile links, posts and the Why Q? submenu (the Why Q? link then leads to the homepage tiles).

  1. Merge: Vercel runs the additive migration, the site rebuilds.
  2. Home content, navigation (Why Q? sub-items, no Program) and the new TikTok link are proposed as drafts.
  3. An approver publishes; the publish hook rebuilds the site.

Checks

  • Locally, each step of pnpm run check on its own (the wrapper cannot spawn pnpm on this Windows machine): docs, markdownlint, cspell, prettier, design, events, cms-styles, lint, astro check, fixture build, budgets, web tests, CMS types, CMS tests, CMS build: all pass.
  • Playwright (Edge): homepage behavior at 1440, 390 and 320 (countdown against the real clock, after a pause and at zero; reduced motion; no JS), Why Q? menu on desktop, phone, keyboard and without JS (19 checks), ticket compare pickers (28/28), carousel swipe, no ticket text over the Q at 17 widths.
  • GPU trace on integrated graphics: 60 frames per second in every section of both pages, one to three offscreen passes per frame.

Not verified

  • The migration has not been run against a database (Docker was not running on this machine). It is additive; verifying it with pnpm --filter cms run migrate on a local database before merging is still open.
  • No test on a real phone, Safari or Firefox.
  • Visual baselines will change; the advisory visual workflow refreshes them.

🤖 Generated with Claude Code

Kiron-Q-Summit and others added 2 commits November 11, 2026 23:28
Schema for the 2027 homepage, all additive and optional so the published
content keeps working until editors fill the new fields:

- page-home: hero badge and lead lines, countdown wording, partner band
  eyebrow and heading, audience tiles (eyebrow, link, link label, image),
  speaker highlights, lineup, stand-ins, and the social section with a
  post list (new posts are added at the end, the site shows the newest
  four, so the list holds up to twelve rows)
- site-settings: nav items may carry sub-items (the audience pages under
  Why Q?)
- page-whyq: live preview opens an audience page, since /whyq/ itself is
  now a redirect
- migration 20261111_104849_home_2027, seed and types updated
- tests for the new page-home fields and validations

Co-Authored-By: Claude <noreply@anthropic.com>
Homepage for the 10th edition (DESIGN.md HOME-1):

- video hero with badge, lead lines, a neon countdown to the first
  conference day (Europe/Berlin, recomputed from the clock) and a
  transparent liquid glass Buy Now; the film dissolves into the page
  without a visible edge and without the gray veil
- key figures on one glass pane, partner logo rows from edge to edge,
  four audience tiles, speaker highlights (alumni and lineup stand-ins;
  no face is ever covered by a tag or a name card), and a LinkedIn and
  Instagram section that shows the newest four posts, newest first
- floating glass Qs behind the page; FAQ section removed from home

Why Q?:

- the overview page is gone; /whyq/ redirects to the audience tiles on
  the homepage, and the header item is one button that opens the four
  audience pages (desktop dropdown, phone sheet, keyboard, no JS)
- llms.txt and llms-full.txt list the four audience pages instead
- /program/ stays offline (redirect to the homepage)

Ticket page:

- the glass Q render replaces the drawn Q bubbles; no text lies over it
  and all tickets keep the same size
- no typewriter effect, no Qs behind the page
- resting glass panels no longer blur their backdrop every frame, which
  removed the stutter on integrated graphics

Docs, design tokens, fixture and tests updated with the code.

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
q-web-cms Skipped Skipped Nov 11, 2026 10:44pm UTC

@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Visual review vs main

30 added · 45 changed · 349 same · 0 failed · 30 removed

Open report · e8fe6fc

Review changed pixel diffs first. Added means new vs main (no baseline there yet).

Baselines are staged on this PR. Merging adopts them.

45 changed
30 added
30 removed
  • home-faq-accordion · default 390, 768, 1280
  • home-faq-accordion · empty 390, 768, 1280
  • home-faq-accordion · long-answers 390, 768, 1280
  • home-faq-accordion · many-items 390, 768, 1280
  • home-partner-logos · many-logos 390, 768, 1280
  • home-partner-logos · single-logo 390, 768, 1280
  • home-speaker-grid · long-bio 390, 768, 1280
  • home-speaker-grid · many-speakers 390, 768, 1280
  • home-speaker-grid · single-speaker 390, 768, 1280
  • home-why-cards · many-cards 390, 768, 1280

Job log

The first row of speaker highlights shows past speakers. Q alumni are
former team members, so the badge example, the editor label ("Past
Speaker Label"), the fixture and the docs no longer say "alumni". The
stored field keeps its name (alumniLabel), so the migration is unchanged.

Co-Authored-By: Claude <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
q-web 148ce6d Commit Preview URL

Branch Preview URL
Nov 11 2026, 10:45 PM

This branch was previously deployed

1 inactive deployment
Preview — 148ce6d6 Deployed Nov 11, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant