Skip to content

Source Vault phone menu: always light one link with the gradient - #56

Merged
error404website merged 1 commit into
mainfrom
fix/vault-menu-gradient
Oct 8, 2026
Merged

error404website merged 1 commit into
mainfrom
fix/vault-menu-gradient

Conversation

@error404website

Copy link
Copy Markdown
Owner

On the main site, the open menu always shows one link in the magenta → cyan gradient: its first section (ARCHIVE_404) is the hero at the top of the page, so something is always lit. The vault's top is its header, which has no menu link, so at the top of the page nothing lit up.

Now the vault's phone menu lights PROMPTS (the first section) while the header is in view, then follows the scroll as before. The desktop bar is unchanged (no highlight over the header).

The gradient style itself was already checked in #55. The scroll spy only runs after unlock, and I don't handle the vault key, so please open the menu at the top of the page on the deploy preview: PROMPTS should be lit. npm run check passes.

🤖 Generated with Claude Code

Like the site's menu, the open hamburger always shows the current section
in the gradient; at the top of the page that's PROMPTS. The desktop bar
still shows none while the header is in view.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@netlify

netlify Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for stirring-hamster-57bba9 ready!

Name Link
🔨 Latest commit c2dc63a
🔍 Latest deploy log https://app.netlify.com/projects/stirring-hamster-57bba9/deploys/6ac72682a38ee50007f3cedb
😎 Deploy Preview https://deploy-preview-56--stirring-hamster-57bba9.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@error404website
error404website merged commit a16d095 into main Oct 8, 2026
5 checks passed
@error404website
error404website deleted the fix/vault-menu-gradient branch October 8, 2026 05:16
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