release(docs): rebuilt feature pages, real logos, value-first copy - #983
Conversation
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)
…keep their padding (cherry picked from commit e65001f)
…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)
(cherry picked from commit 9026152)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
The latest updates on your projects. Learn more about Unkey Deploy
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
| </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." |
There was a problem hiding this comment.
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.
| 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 />} |
There was a problem hiding this comment.
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.", |
There was a problem hiding this comment.
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)
Releases the rebuilt feature pages from staging to main, cherry-picked with
-x.What ships
@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.apps/docs/app/global.cssnow scanspackages/ui/src, so@databuddy/uiclasses like the hero button padding are generated.MidPageCta, the old demo files, and thed3-geo/topojson-client/world-atlasdependencies.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
tsc --noEmitpasses on this branch after building sdk, ui, tracker and devtools. Ultracite is clean on all changed files.apps/docsandbun.lock.Summary by cubic
Releases the rebuilt feature pages from staging to main.
@icons-pack/react-simple-icons.apps/docs/app/global.cssby scanningpackages/ui/srcfor Tailwind classes.demo-primitives.tsx, and removesMidPageCta, old demo files,demo-constants.ts, and thed3-geo,topojson-client, andworld-atlasdependencies.bun.lockagainst main because main's nuxt sdk range (^2.4.20) differs from staging's.Written for commit a2700c4. Summary will update on new commits.