2026 Static Site#354
Open
maxxcrawford wants to merge 23 commits into
Open
Conversation
✅ Deploy Preview for 200ok-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
* Add Kevin, April, Taron speaker info * fix(static-2026): make conference nav targets real The 2026 header shipped with placeholder anchors, which left primary navigation and the ticket CTA inert. This wires the nav to real page destinations, points ticket purchases at the existing Tito URL, and adds compact schedule and FAQ sections so each anchor lands on visible content. Constraint: 2026 page is a standalone static HTML page in this PR checkout Rejected: Leave Schedule and FAQ pointed at placeholder anchors | users would still hit inert navigation Confidence: high Scope-risk: narrow Directive: Replace provisional schedule and FAQ copy when final 2026 program details are available Tested: Static anchor verification; git diff --check Not-tested: Browser visual QA * content(static-2026): update April Dunnam talk abstract April provided the final Copilot-focused title and abstract, so the 2026 speaker card now reflects the submitted session details instead of the earlier placeholder OpenClaw copy. Constraint: Preserve April's existing bio and social links Rejected: Keep the old OpenClaw-focused description | it no longer matches the speaker-provided abstract Confidence: high Scope-risk: narrow Tested: Static anchor verification; required April abstract copy check; git diff --check Not-tested: Browser visual QA * content(static-2026): add Gitwit venue map link The FAQ should identify the 2026 venue by name and give attendees a direct map target, so the location answer now includes Gitwit and a Google Maps search link for the venue address. Constraint: Keep the update scoped to the existing FAQ answer Rejected: Link only the raw address | the user specifically asked to add Gitwit Confidence: high Scope-risk: narrow Tested: Static anchor verification; required venue copy check; git diff --check Not-tested: Browser visual QA --------- Co-authored-by: ThatGuySam <sam@sam.lc>
Refreshes Kevin's public speaker profile from his provided bio so the 2026 page reflects his current NVIDIA role, KSG consulting work, and relevant background without publishing private email or phone details. Constraint: Source update came from Kevin Griffin's email request Rejected: Add email and phone contact details | personal contact information does not belong on the public speaker card Confidence: high Scope-risk: narrow Directive: Keep speaker profile links public-facing; do not add private contact details from email signatures Tested: Kevin card content verification script; npm run build --prefix static-2026 Not-tested: Live browser visual check
Adds a progressive Expand/Collapse control so speaker cards stay scannable while preserving full bio content and public profile links. Constraint: 2026 site is static HTML without a component framework Rejected: Hard truncate the copy | would hide content from users and search engines without a recovery path Confidence: high Scope-risk: narrow Directive: Keep profile links outside the collapsed bio region so speaker links remain immediately reachable Tested: Inline script syntax check; speaker bio DOM behavior stub; static marker verification; npm run build --prefix static-2026 Not-tested: Live browser visual check
The 2026 static page needed Luke's confirmed talk and bio in the speakers section. The card follows the existing static speaker markup and uses a current public profile image at the expected local asset path so the page can render without remote image dependencies. Constraint: Keep 2026 static site paths stable for speaker images Rejected: Use the archived 200x200 placeholder | lower quality than current public profile avatar Confidence: high Scope-risk: narrow Directive: Replace the avatar only if Luke provides a newer approved high-resolution headshot Tested: npm run build in static-2026; git diff --check; headless Chromium render of speakers section Not-tested: Production deploy
Luke's latest deck uses Mr. Fixbot and lists his role as Privacy & Security Software Engineer at Mozilla, so the public speaker card should match that source instead of the earlier placeholder title. Constraint: Details came from the provided deck screenshot Rejected: Keep Mr. Brokebot copy | no longer matches the provided talk deck Confidence: high Scope-risk: narrow Directive: Keep future Luke talk copy aligned with the final speaker deck or speaker-provided details Tested: npm_config_cache=/private/tmp/200ok-npm-cache npm run build; git diff --check; headless Chromium render before push Not-tested: Production deploy
Add a standalone /map page with the finalized floor SVG assets and an accessible room summary for attendee navigation. Verified with npm run build, HTML/ARIA/SVG structure checks, and git diff --check.
The conference needs a stable public URL for Slack QR codes while Slack invite URLs remain replaceable behind Netlify redirects. Constraint: Slack invite URL can be rotated without reprinting QR materials Confidence: high Scope-risk: narrow Directive: Keep /slack pointed at the current Techlahoma Slack invite link Tested: mise exec node@18.12.1 -- npm run build Tested: mise exec node@18.12.1 -- npx netlify build --dry --offline Not-tested: Live Netlify deploy redirect after push
Netlify production is currently publishing the static-2026 directory from the 2026-site branch, so the Eleventy /content/map.njk page was committed but not included in the live output. This adds the same standalone map page and SVG assets under static-2026 so /map/ exists in the deployed publish directory. Constraint: Netlify production deploys 2026-site from static-2026 Rejected: Wait for main Eleventy deploy | production is not using that output today Confidence: high Scope-risk: narrow Directive: Keep static-2026/map in sync with content/map.njk while 2026-site is the production publish path Tested: npm ci in static-2026 Tested: npm run build in static-2026 Tested: static HTML/ARIA/SVG checks Tested: local static server returned 200 for /map/
Adds a Map nav item and location FAQ link on the 2026 homepage, then gives /map/ the same production header and footer as the homepage so the map feels integrated with the live static site. Constraint: Netlify production is currently serving static-2026 from 2026-site Rejected: Only update the Eleventy content page | it is not the active production publish path Confidence: high Scope-risk: narrow Tested: npm run build in static-2026 Tested: home/map HTML structure and ARIA checks Tested: git diff --check Tested: local static server returned 200 for / and /map/ Not-tested: Browser screenshot; Playwright browser binary was not installed in the local cache
The live Netlify site is served from static-2026 on the 2026-site branch, so the speaker replacement belongs in that static homepage rather than the older Eleventy content path. Greg Tatum replaces the withdrawn Fox listing with his current AI-model talk details and supplied headshot. Constraint: 200ok.us currently serves the static-2026 site from Netlify Rejected: Update content/index.md only | that is the older Eleventy homepage and does not match the live 2026 site Confidence: high Scope-risk: narrow Directive: Keep 2026 speaker lineup edits in static-2026 unless Netlify build routing changes Tested: npm run build in static-2026; local static preview at localhost:8099; rg confirms no Fox references remain in static-2026 Not-tested: Netlify production deploy after push
The 2026 speaker list needs Greg Tatum to appear after Luke Crouch while keeping the existing speaker details unchanged. This commit only reorders the static homepage cards used by the deployed Netlify site. Constraint: 200ok.us currently serves the static-2026 homepage from the 2026-site branch Confidence: high Scope-risk: narrow Tested: npm run build in static-2026; git diff --check; rg line order confirms Luke precedes Greg Not-tested: Netlify production deploy after push
The attendee schedule now lives under a Guide section with the floor 1 map above it, matching the public day-of-conference flow. A Netlify redirect gives QR codes and direct links a stable /guide entry point while preserving the existing Schedule nav anchor. Constraint: Site is static 2026 HTML published from static-2026 Rejected: Split guide into a separate page | current request asked to move schedule into a section and redirect /guide to it Confidence: high Scope-risk: narrow Directive: Keep /guide anchored to the guide section if guide content moves Tested: npm run build in static-2026; git diff --check; netlify.toml parsed with tomllib; Chromium desktop and mobile renders against local server Not-tested: Netlify CLI redirect smoke test under local Node 25 due CLI dependency crash
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
2 participants
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.
No description provided.