refactor(landing): redesign sections below the hero
Give everything below the (unchanged) hero a cohesive radar/monitoring
visual language: shared app.css utilities (radar grid, signal pulse, hover
edge) and a reusable SectionEyebrow, applied across features, configurations,
statistics, screenshots, FAQ and the open-source banner.
Replace the five shaking metric cards with a grounded, full-width social-proof
band flush under the hero showing four rounded figures (users, active alerts,
alerts sent, auctions tracked) — approximate, never exact. Unify all sections
to max-w-5xl for consistent edges. Spec in docs/specs/landing-redesign.md.
refactor(landing): redesign sections below the hero
Give everything below the (unchanged) hero a cohesive radar/monitoring
visual language: shared app.css utilities (radar grid, signal pulse, hover
edge) and a reusable SectionEyebrow, applied across features, configurations,
statistics, screenshots, FAQ and the open-source banner.
Replace the five shaking metric cards with a grounded, full-width social-proof
band flush under the hero showing four rounded figures (users, active alerts,
alerts sent, auctions tracked) — approximate, never exact. Unify all sections
to max-w-5xl for consistent edges. Spec in docs/specs/landing-redesign.md.
feat(settings): connected-app revocation, fuller export, MCP on landing and guide
- Connected Applications card in settings, listing apps authorized over OAuth
with a Revoke button that deletes both the tokens and the stored consent, so
a later authorization must be approved again rather than resumed silently.
The listing unions oauthAccessToken with oauthConsent. Reading tokens alone
left an app that had been approved but had not yet exchanged its
authorization code invisible — and therefore impossible to revoke. Caught by
driving the flow in a real browser.
- Data export now includes cloud availability alerts and their history,
notification settings, and connected applications; it predated all three. It
shares the settings helper so both report the same grants. Token and client
secret values stay out: they are the application's credentials, not the
user's data, and a downloadable file containing them would be a credential
leak.
- Export button gets data-sveltekit-reload. It is an anchor, so the client
router was starting a navigation to an endpoint that replies with a file and
never completes, leaving the loading bar animating forever.
- Landing page section and guide chapter for the MCP server, covering how to
connect, what needs an account, how to revoke, and the net-of-VAT/IPv4
pricing basis so figures read back from an assistant mean what they say.
refactor(landing): redesign sections below the hero
Give everything below the (unchanged) hero a cohesive radar/monitoring
visual language: shared app.css utilities (radar grid, signal pulse, hover
edge) and a reusable SectionEyebrow, applied across features, configurations,
statistics, screenshots, FAQ and the open-source banner.
Replace the five shaking metric cards with a grounded, full-width social-proof
band flush under the hero showing four rounded figures (users, active alerts,
alerts sent, auctions tracked) — approximate, never exact. Unify all sections
to max-w-5xl for consistent edges. Spec in docs/specs/landing-redesign.md.
refactor(landing): redesign sections below the hero
Give everything below the (unchanged) hero a cohesive radar/monitoring
visual language: shared app.css utilities (radar grid, signal pulse, hover
edge) and a reusable SectionEyebrow, applied across features, configurations,
statistics, screenshots, FAQ and the open-source banner.
Replace the five shaking metric cards with a grounded, full-width social-proof
band flush under the hero showing four rounded figures (users, active alerts,
alerts sent, auctions tracked) — approximate, never exact. Unify all sections
to max-w-5xl for consistent edges. Spec in docs/specs/landing-redesign.md.
refactor(landing): redesign sections below the hero
Give everything below the (unchanged) hero a cohesive radar/monitoring
visual language: shared app.css utilities (radar grid, signal pulse, hover
edge) and a reusable SectionEyebrow, applied across features, configurations,
statistics, screenshots, FAQ and the open-source banner.
Replace the five shaking metric cards with a grounded, full-width social-proof
band flush under the hero showing four rounded figures (users, active alerts,
alerts sent, auctions tracked) — approximate, never exact. Unify all sections
to max-w-5xl for consistent edges. Spec in docs/specs/landing-redesign.md.