fix(events): restore live detail navigation - #30
Open
Elvis020 wants to merge 1 commit into
Open
Conversation
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
devcongress-website | 3cd1c86 | Commit Preview URL Branch Preview URL |
Aug 11 2026, 09:06 PM |
Elvis020
force-pushed
the
feature/fix-client-event-render
branch
2 times, most recently
from
August 11, 2026 19:58
828bfee to
025aea2
Compare
Elvis020
changed the title
Elvis020
force-pushed
the
feature/fix-client-event-render
branch
4 times, most recently
from
August 11, 2026 20:26
db08374 to
73677ff
Compare
Repair dynamic public event details while keeping the Events list stable, compact, responsive, and fast during in-page navigation. - Define status labels in the browser script instead of relying on Astro frontmatter. - Hide the past-event action completely when no recording is available. - Serve the dynamic event shell without waiting for an EMS lookup. - Add a dedicated readiness response for the Slack delivery safeguard. - Switch event cards, back navigation, and browser history inside the loaded events shell; refresh list data in the background and ignore stale route responses. - Reuse the confirmed live list response for event detail rendering and start an intent fetch on press when that response is not ready yet. - Preserve Calendar view and month through calendar event links and the detail Back link. - Restore the standard All Events heading, count, and browser title before revealing the list after an event-detail route. - Reduce mobile-only Events header padding and the wrapped calendar-control gap while retaining the desktop layout. - Make the mobile navigation menu an overlay, close it after a link selection or Escape, and respect reduced-motion preferences. - Refine the mobile navigation with an open-state shadow, clear close icon, directional links, and full-width touch-friendly actions. - Reduce mobile hero CTA sizing and spacing so the community highlight video keeps visual priority. - Remove the duplicate About this event heading from dynamic and static detail pages. Verification: - pnpm build - git diff --check - Public event detail API measured at 0.70-0.80 seconds before reuse - Local Worker: normal event route 200, readiness route 204, unknown readiness route 404
Elvis020
force-pushed
the
feature/fix-client-event-render
branch
from
August 11, 2026 21:06
73677ff to
3cd1c86
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
Public event pages load without a server-side EMS wait, and event navigation is fast, stable, and state-preserving across desktop and mobile.
What changed
?readiness=1; normal visitors get the page shell immediately.Checked
pnpm buildpassed.200; known readiness route204; unknown readiness route404.git diff --checkpassed.Requires the paired EMS readiness change in devcongress/events-management#107 before Slack starts using the readiness signal.