[codex] Hide CFP speaker callout on home page#183
Conversation
|
This is somewhat intentional, it's all synced to Sessionize and as soon as we populate speakers it'll switch modes |
|
We'd need to start caching that state somewhere, wouldn't want to put the main homepage behind Sessionise API as that'll just lead to rate limits and more error cases |
Yeah, easy enough to do right - could even stick it in the DB that's cache for X days or even weeks to be honest as it doesn't change that often |
|
Get codex on it Nowham Maybe save it on the event obj |
|
Implemented the event-level CFP flag on this branch. Changes:
Validation:
|
Co-authored-by: James Sherlock <15193942+Sherlouk@users.noreply.github.com>
Sherlouk
left a comment
There was a problem hiding this comment.
looks good, let's push to staging and test
Fork pull_request runs don't receive repository secrets, so the "Login to Google Artifact Registry" step failed with "Password required". Gate the registry login, image push, and deploy job on same-repo events so fork PRs still lint, test, and compile the release build without attempting secret-dependent steps. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@Sherlouk i've had to add a rule there because deploy can't happen on forked PRs. if it's wrong let me know, i think you need to approve the deply |
|
Merging into an org-owned branch for testing |

What changed
Removed the home-page fallback that rendered the CFP speaker callout when no speakers were announced.
Why
The site should no longer show the "We are looking for speakers" call for papers section on the home page.
Impact
When speakers exist, the speaker section still renders as before. When no speakers exist, the home page now skips the CFP callout instead of linking visitors to
/cfpfrom that section.Validation
Resources/Views/Home/home.leaf.swift build, but stopped it after several minutes while SwiftPM was still fetching the largeaws-sdk-swiftdependency and had not reached compilation.