feat: archive 2026 and launch PlanetNix 2027 site - #42
Merged
Conversation
Archive the current (2026) edition into /2026/ as a self-contained
snapshot, mirroring how /2025/ and /2024/ are preserved, and reset the
root to a 2027 edition that reuses the existing design.
- Add /2026/ archive (index, agenda, speakers, assets); fix internal
archive links, manifest paths and sitemap to be self-contained
- Root index/agenda/speakers rebranded to 2027 with placeholders for
details still to be confirmed (marked TODO in-source):
- dates -> Dates to be announced
- CFP link -> CFP_LINK_TBA
- registration link -> REGISTRATION_LINK_TBA
- Sessionize event id -> SESSIONIZE_EVENT_ID_TBA
- 2026-specific speakers, partners and afterparty banner cleared
pending the new line-up
- Register /2026/ in sitemap index and footer archive lists
- Fix unprefixed mailto: on the footer contact link
Confirmed Thursday/Friday, April 1st-2nd, 2027 in Pasadena. Fill in hero date, location date and meta descriptions across index, agenda and speakers pages.
Wire the live Sessionize CFP (https://sessionize.com/planet-nix-2027) into index, agenda and speakers: enable the announcement banner (CFP open, closes Dec 23) and the CFP call-to-action button.
SCALE 24x registration is not live yet (scale/24x 404s). Comment out the Sign Up Now CTAs in the signup and location sections across index, agenda and speakers, pre-filling the likely SCALE 24x URL so they can be re-enabled with a one-line uncomment once registration opens.
No 2027 agenda yet, so comment out the Agenda navigation link across index, agenda and speakers. The agenda.html page stays in the repo (unlinked) and the link can be re-enabled with a one-line uncomment once the schedule is published.
✅ Deploy Preview for planetnix ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Comment out the announcement banner and CFP call-to-action across index, agenda and speakers. The Sessionize link is preserved in the comments so it can be re-enabled with a one-line uncomment once the CFP is announced.
The Lighthouse CI failed at 'flox activate' with: 'nodejs' conflicts with 'nodejs' — both packages provide include/node/common.gypi The explicit nodejs install and the nodejs bundled by clean-css-cli both resolved at priority 5 and collided. Running 'flox upgrade' re-locks the environment and resolves the conflict, also bumping: google-lighthouse 12.8.2 -> 13.3.0 nodejs 22.21.1 -> 24.15.0 just 1.43.1 -> 1.51.0 imagemagick 7.1.2-8 -> 7.1.2-23 Verified locally: 'flox activate' now builds and node/lighthouse/just/ cleancss all resolve.
The Lighthouse job builds the Flox env twice — once for the PR branch and once for the base branch comparison. Because the base branch (main) has the older, broken env locked (the nodejs/clean-css-cli conflict), the 'Start dev server for base branch' step failed even though this branch's env is fixed. Stash the PR branch's fixed .flox to /tmp before checking out the base branch, then restore it so the base measurement runs with the same working toolchain. This keeps the whole fix self-contained in one PR and makes the comparison apples-to-apples.
🔍 Lighthouse Performance ReportPerformance audit completed for commit bdd8b00 Scores Comparison
Performance Impact🎉 Great job! Performance improved by 26 points! ✨ Performance score is excellent! 📊 Score Guide
Change indicators:
🚀 Current OptimizationsOptimizations in place:
🤖 Automated report generated by Lighthouse CI comparing against |
Uncomment the announcement banner and CFP call-to-action across index, agenda and speakers — the Sessionize CFP (https://sessionize.com/planet-nix-2027) is now being announced.
|
I see you |
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.
Summary
Archives the 2026 edition into
/2026/(matching how/2025/and/2024/are preserved) and resets the site root to a 2027 edition reusing the existing design. Built incrementally as details were confirmed; remaining unknowns are commented out withTODO(Rok)markers so they're safe to ship and trivial to re-enable.Archive (
/2026/)Root to 2027
/2026/in sitemap index + footer archive lists; fixed a stray unprefixedmailto:Commented out until ready (each marked
TODO(Rok))SESSIONIZE_EVENT_ID_TBAplaceholderVerification
Served locally -- all routes (
/, subpages,/2026/*,/2025/,/2024/, sitemaps, assets) return 200; no broken internal links.