Skip to content

release(docs): rebuilt feature pages, real logos, value-first copy - #983

Merged
izadoesdev merged 14 commits into
mainfrom
izadoesdev/feature-pages-release
Sep 29, 2026
Merged

izadoesdev merged 14 commits into
mainfrom
izadoesdev/feature-pages-release

Conversation

@izadoesdev

@izadoesdev izadoesdev commented Sep 28, 2026 •

Copy link
Copy Markdown
Member

Releases the rebuilt feature pages from staging to main, cherry-picked with -x.

What ships

  • Rebuilt pages: /databunny, /errors, /feature-flags, /links, /uptime and /web-vitals. Each has looping motion visuals, headlines that say what the user gets, and no pricing sections, badges or duplicate CTAs.
  • Homepage: the landing AI section replays a Databunny investigation, the feature grid copy leads with outcomes, and the navbar feature descriptions are rewritten.
  • Real brand logos from the pinned @icons-pack/react-simple-icons, plus Slack and LinkedIn vendored from Simple Icons 13.21.0. They replace placeholder names such as Acme and Jane Doe, including in the contact, startups, ambassador and OSS form placeholders.
  • Button padding fix: apps/docs/app/global.css now scans packages/ui/src, so @databuddy/ui classes like the hero button padding are generated.
  • Cleanup: removes unused landing primitives, MidPageCta, the old demo files, and the d3-geo / topojson-client / world-atlas dependencies.

Commits

3c50d58, 30c3304, 269702a, 960239c, bdf9571, 3fe2dfe, c009e5d, fe6c40b, e65001f, a08de3e, 2a00268, 9026152.

Also one commit specific to this release branch, ac7761f. Staging's lockfile also moves nuxt to sdk ^3.0.0, but main's nuxt still declares ^2.4.20, so the lockfile here is regenerated against main. The only lockfile change is the removed docs packages.

Verification

  • Docs tsc --noEmit passes on this branch after building sdk, ui, tracker and devtools. Ultracite is clean on all changed files.
  • The diff touches only apps/docs and bun.lock.
  • On staging, all six pages were checked in Playwright with reduced motion and with motion on. Page height stayed at one value, there were no console errors, and hero buttons had 14px padding.
  • Product claims were checked against the code, for example that link clicks are not metered as events and that uptime and web vitals are ungated.

Summary by cubic

Releases the rebuilt feature pages from staging to main.

  • Rebuilds /databunny, /errors, /feature-flags, /links, /uptime, and /web-vitals with looping motion visuals, outcome-first headlines, and no pricing sections or duplicate CTAs.
  • Rewrites the homepage AI section, feature grid, and navbar feature descriptions to lead with outcomes.
  • Replaces placeholder names like Acme and Jane Doe with real brand logos from @icons-pack/react-simple-icons.
  • Fixes hero button padding in apps/docs/app/global.css by scanning packages/ui/src for Tailwind classes.
  • Consolidates the motion visuals on shared timeline, reveal, Count, and FeatureSection helpers in demo-primitives.tsx, and removes MidPageCta, old demo files, demo-constants.ts, and the d3-geo, topojson-client, and world-atlas dependencies.
  • Regenerates bun.lock against main because main's nuxt sdk range (^2.4.20) differs from staging's.

Written for commit a2700c4. Summary will update on new commits.

Review in cubic

A framed three-step stage (checks every source, finds the cause, tells you what to fix) cycles through three incidents and replaces the example questions and the Slack card. MCP moves to its own row beside the terminal.

(cherry picked from commit 3c50d58)
Six motion visuals, each timeline-driven and always rendered, so nothing shifts or starts empty: baseline bands in the hero, how Databunny decides what stays quiet, commit zoom, one thread per problem, fix and verify, and chat with its query.

Copy and visual labels were audited against the investigation worker: no weekday baselines, no per-step funnel checks, no rising referral cases, real revenue SQL, and the landing AI section drops a title that matched a competitor's hero.

(cherry picked from commit 30c3304)
One consistent story (a copy change that cut signups), a trust line and plain pricing in the hero, a free chat CTA, plan contents on the pricing rows, setup, AI data, and wrong-call FAQs, a renamed funnel-fix section, and legible quiet-list reasons, from three blind first-visit reviews and a retest.

(cherry picked from commit 269702a)
…an lookups

Moves the timeline, status, and reveal helpers plus FeatureRow into demo-primitives and the plan price and event lookups into the pricing data, so the Databunny and errors pages use one copy. FeatureRow wraps its visual, which clears a React key warning.

(cherry picked from commit 960239c)
One story told plainly: a TypeError that hit 312 people. Visitors flowing to checkout, one stuck tab against one real bug, the visit it broke, Databunny's kept-going comparison, and a one-line setup that filters noise. Claims match the capture and dashboard code, and the navbar no longer promises error alerts.

(cherry picked from commit bdf9571)
…CTAs from the Databunny and errors pages

(cherry picked from commit 3fe2dfe)
…h, team, targeting, and dependency visuals

(cherry picked from commit c009e5d)
…drop the repeated flag header

(cherry picked from commit fe6c40b)
…al logos and what each one gets you

(cherry picked from commit a08de3e)
…with what users get, and swap placeholders for real logos

(cherry picked from commit 2a00268)
@vercel

vercel Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
databuddy-status Ready Ready Preview Sep 29, 2026 7:57am UTC
documentation Ready Ready Preview Sep 29, 2026 7:57am UTC
1 Skipped Deployment
Project Deployment Actions Updated
dashboard Skipped Skipped Sep 29, 2026 7:57am UTC

@unkey-deploy

unkey-deploy Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Unkey Deploy

Name Status Preview Inspect Updated (UTC)
links (preview) Ready Visit Preview Inspect Sep 29, 2026 7:56am

@coderabbitai

coderabbitai Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 6ccbe88d-44e5-41ba-8207-767d03c34bf3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 3/5

[Low risk] Rebuilt marketing pages with new copy and demo visuals.

The PR is not ready to merge until the Databunny repair and SSL-warning claims reflect the flows users can actually access.

Findings

  1. P1 SSL warning requires an alarm ▶
  2. P1 Tracking repair exists only in demo ▶
  3. P2 Flag logging is not once-only ▶

Summary

The PR rebuilds six feature landing pages and the homepage AI presentation with animated demonstrations and outcome-led copy. It also updates form placeholders, adds UI-package Tailwind scanning, and removes unused docs visuals and dependencies.

  • The new Databunny repair and uptime certificate-warning promises need to match the available product flows.
  • Feature-flag event copy should reflect the SDK’s actual deduplication scope.

Reviews (1) · Last reviewed commit: "chore(deps): keep main's lockfile on the..."

</div>
</Section>
<FeatureRow
body="You get a heads-up 14 days before it runs out, with time to renew before visitors see a security warning."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 SSL warning requires an alarm A newly created monitor has no linked alarm, and SSL expiry notifications are skipped when none is linked. The page promises a 14-day heads-up without stating that setup requirement, so a customer can create a monitor and receive no warning before its certificate expires.

Comment on lines +129 to +133
body="When a funnel or goal stops matching real traffic, Databunny proposes the fix and confirms it worked after you apply it."
flip
id="fixes"
title="Fix broken tracking in one click."
visual={<FixVerify />}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Tracking repair exists only in demo This section promises that a customer can apply a proposed tracking fix in one click and have Databunny verify it. The depicted Apply button only advances an animation; the available AI tools change funnel and goal definitions but provide no tracking-repair action. A customer following this section cannot perform the promised repair from an investigation.

question: "Are flag checks billed?",
answer:
"Every plan includes feature flags - the free plan gives you 3 flags to start, and paid plans scale from there. Flag evaluations never count toward your event quota.",
"No. Each browser logs a flag once so you can see who got it, and that log counts as one event.",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Flag logging is not once-only The SDK suppresses duplicate flag events only within the current manager, and a changed value or variant can produce another event. Reloading can also create a new manager. Since these events enter monthly usage, saying each browser logs a flag once may lead customers to underestimate their event count.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

…elpers home, and drop dead hero props and demo-constants

(cherry picked from commit 4290144)

This branch was successfully deployed

3 active and 1 inactive deployments
Preview – documentation — a2700c41 Deployed Sep 29, 2026 by vercel[bot]
Preview – databuddy-status — a2700c41 Deployed Sep 29, 2026 by vercel[bot]
links - preview — a2700c41 Deployed Sep 29, 2026 by unkey-deploy[bot]
Preview – dashboard — a2700c41 Deployed Sep 29, 2026 by vercel[bot]
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