Hero editor: fullscreen landing, remove two-card row, quick links into hero #28
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/hero-fullscreen-landing"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Portal.jsx). The hero is now the entire landing page, with nothing rendered after it (aside from the site-wide footer, which is shared chrome on every public page and out of scope here).flex: 1+min-height: 100vhinstead of the oldclamp(600px,72vh,860px)fixed height.overflow: hiddenon the hero section. On mobile browsers,100vhcan compute smaller thanwindow.innerHeight(address-bar/viewport quirk) - withoverflow: hiddenthe wrapped quick-links text was getting clipped at the bottom edge. Verified this was a real, reproducible clip before the fix and confirmed it renders fully (in the safety gap before the footer) after.buttonselement appended indefaultLayout()(heroLayout.js). This reuses the existingbuttonselement type/component (same one used for "Enter the Website" / "Open the Wiki") - no changes to the hero editor's schema or admin UI code - so the links are fully editable/movable/removable through the existing Hero Editor out of the box.hero_layoutsetting is currently empty (unpublished), this new default takes effect immediately on merge with no DB migration needed. If a custom hero has already been published, an admin can add the same quick-links button set manually via "+ Buttons" in the editor.Test plan
/- confirmed the two-card row and old quick-links nav are gone, and the hero fills the page.background-size: coverholds, hero height matches100vh, and the quick-links row no longer gets clipped (previously reproduced the clipping bug withoverflow: hidden, confirmed fixed after removing it)./admin/heroand confirmed the quick-links element renders in the editor canvas as a normalbuttonselement (verified against the code-level default; a local dev-only draft in the DB predates this change and doesn't yet include it, which is expected - it's editable through the same existing Buttons panel as the other button elements).npm run buildinclient/passes clean.🤖 Generated with Claude Code