Skip to content

Feat/connect hero to app navigation - #15

Merged
Alex350-coder merged 2 commits into
mainfrom
feat/connect-hero-to-app-navigation
Sep 9, 2026
Merged

Alex350-coder merged 2 commits into
mainfrom
feat/connect-hero-to-app-navigation

Conversation

@Alex350-coder

Copy link
Copy Markdown
Owner

No description provided.

Alex350-coder and others added 2 commits September 8, 2026 21:09
'Platform' and 'How it works' linked to #platform/#how-it-works, but
neither InfoSection instance had a matching id, so both were dead
buttons. Add an optional id prop to InfoSection and wire it on the two
Hero sections; point the nav links at '/#platform' and '/#how-it-works'
(not bare '#anchor') so they still resolve correctly from other routes.

Also promote Navbar, Footer, and InfoSection from features/hero/components
to components/marketing — they carry no Hero-specific logic and the new
/docs page (next commit) needs to reuse the same nav/footer chrome.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
'Docs' linked to bare '#', going nowhere. Add /docs: a real
documentation landing page covering getting started, the supported
tool adapters (nmap, ffuf, nuclei), the graph's node/edge/metadata
model, and the security posture, reusing the shared Navbar/Footer/
InfoSection for visual consistency with the Hero.

Extract the httpOnly-refresh-cookie presence check page.tsx already
used into lib/auth-cookies.ts's getHasSession() so /docs's Navbar
reflects session state too, without duplicating the check.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@Alex350-coder
Alex350-coder merged commit e4c134b into main Sep 9, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant