Add /events/ page with Luma embed for first event#22
Merged
Conversation
New top-level page at /events/ for publishing upcoming events. Ships with the first event embedded as a Luma iframe and a footer entry under Resources. OG image registered in the static manifest. Hard-codes the single event inline; if we get past 3-4 events, lift into a content collection. No Schema.org Event JSON-LD — event metadata lives inside the Luma iframe and isn't in the page DOM, so fabricating it would risk drift. Uses WebPage schema instead.
initializ-mk
force-pushed
the
feat/events-page
branch
from
3abac79 to
17bc19e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/events/for publishing upcoming events (talks, workshops, meetups, conferences).evt-9ZnGnQtifJKOHd3) with a fallback "Open on Luma" link in case the embed fails to load.scripts/generate-og.tsstatic manifest →public/og/events.pngauto-generates on build.Page sections: hero → upcoming (iframe) → "Want us at your event?" CTA (mailto + Discord).
Design notes
EventJSON-LD. The event metadata (name, date, location) lives inside the Luma iframe and isn't surfaced in the page DOM. Fabricating it in JSON-LD would risk drift. UsesWebPageschema instead.src/content/events/collection with a proper schema.Nav.astrois already at 6 links + GitHub badge. Footer placement only.hello@initializ.ai(existing alias) — swap to a dedicatedevents@if/when that routes.Test plan
npm run buildcompletes; emitsdist/events/index.htmlandpublic/og/events.pnggrep '"WebPage"' dist/events/index.htmlreturns the schema blockgrep 'href="/events/"' dist/index.htmlreturns the footer entrygrep 'luma.com/embed/event/evt-9ZnGnQtifJKOHd3' dist/events/index.htmlreturns the iframe srcmax-w-2xl+w-full)