Skip to content

feat(landing): price, retention and setup on every feature page - #2717

Open
Makisuo wants to merge 3 commits into
mainfrom
t3/feature-page-competitive-review
Open

Makisuo wants to merge 3 commits into
mainfrom
t3/feature-page-competitive-review

Conversation

@Makisuo

@Makisuo Makisuo commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

Feature pages never said what a feature costs, how long it keeps data, or where its setup doc lives. Their .md versions also dropped the extra sections, so an agent reading /features/kubernetes-monitoring.md never saw the Helm install that the HTML page shows. The roadmap still listed AI observability as in progress, months after Agent Sessions shipped.

What changed

  • A plan block on all 14 feature pages (HTML and .md):

    • the plan and the meter the feature bills under, read from the same getOffer() as /pricing;
    • retention, matching /docs/reference/retention;
    • any hard limit (10 uptime monitors);
    • the Superwall scale claim;
    • links to the setup doc and to pricing.

    It comes from lib/feature-plan.ts, so the page and its .md version can't disagree. Code review bills under AI usage. Alerts, status pages and MCP have no meter of their own and say so.

  • .md versions include the extra sections. Snippet data moved to lib/feature-sections.ts, and the section components and the .md versions both read it. Covered: the k8s install, product event snippets, status page feeds, uptime check traces, and CI and after-merge review.

  • Roadmap catches up. Newly marked shipped: Agent Sessions, self-hosting, the service API view, investigations, the EU region, product events, code review, uptime, anomaly detection, status pages, SLOs and on-call. Dates come from the changelog and git history. Continuous profiling is in progress.

  • MCP page facts list Cursor, 130+ tools and every kind of write. The documented write tools cover on-call, SLOs, uptime, status pages, dashboards and ingest rules.

  • llms.txt counts the feature pages from the registry instead of hard-coding 8 names.

  • getOffer() makes one Autumn request per build instead of one per page render. The site is fully static, so the cache never outlives a build.

  • ja/ko gain pricing_rate_included, which the pricing page was already rendering in English.

Verification

  • bun run test in apps/landing: 25 files, 198 tests pass. The new feature-markdown.test.ts checks:
    • every .md version states the plan and the scale proof;
    • the logs .md quotes the per-GB rate, the retention and the docs link;
    • code review bills as AI usage;
    • k8s carries the helm upgrade --install command;
    • product events carries its snippets;
    • llms.txt counts the registry.
  • bun run build succeeds (315 pages). I checked the built dist/features/*.md by hand.
  • A separate review pass checked every retention number, price, MCP claim and roadmap date against the docs, autumn.config.ts, the changelog and git history. Its fixes are in the second commit.

Screenshots

Log management, desktop:

desktop

Mobile (390px):

Japanese:

ja

Roadmap after the catch-up:

roadmap

The roadmap has nothing under Next or Later now, and its own empty state ("Nothing here yet") renders there. Real planned items need a product decision, so I didn't invent any.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.


Devin Review

Feature pages stated no price, retention or setup doc, and their .md twins
dropped the extra sections, so an agent reading
/features/kubernetes-monitoring.md never saw the Helm install.

- A plan block on every feature page and its .md twin: plan and meter rates
  from the same getOffer() as /pricing, retention per signal, the Superwall
  scale claim and the setup doc.
- The .md twins render each page's extra sections (install commands, product
  event snippets, status page feeds) from data now shared with the components.
- The roadmap lists what has shipped (Agent Sessions, self-hosting, uptime,
  status pages, SLOs, on-call, EU region, and more) instead of showing AI
  observability as in progress.
- The MCP page lists Cursor, the tool count and every kind of write; llms.txt
  counts the feature pages from the registry.
- getOffer() makes one Autumn request per build instead of one per render.
- ja/ko gain the missing pricing_rate_included string.
@maple-review-bot

This comment has been minimized.

@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 14 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f01c6275-af48-4441-a61d-a1e7da8704e6
Commits

Reviewing files that changed from the base of the PR and between 4748c8a and 624c519.

Files selected for processing: 29

  • apps/landing/messages/en.json
  • apps/landing/messages/ja.json
  • apps/landing/messages/ko.json
  • apps/landing/src/__tests__/feature-markdown.test.ts
  • apps/landing/src/components/page/FeaturePage.astro
  • apps/landing/src/components/page/PlanFacts.astro
  • apps/landing/src/components/page/sections/K8sInstall.astro
  • apps/landing/src/components/page/sections/ProductEventsSources.astro
  • apps/landing/src/components/page/sections/StatusPageFeeds.astro
  • apps/landing/src/content/roadmap/ai-observability.md
  • apps/landing/src/content/roadmap/anomaly-detection.md
  • apps/landing/src/content/roadmap/api-observability.md
  • apps/landing/src/content/roadmap/continuous-profiling.md
  • apps/landing/src/content/roadmap/eu-region.md
  • apps/landing/src/content/roadmap/github-code-review.md
  • apps/landing/src/content/roadmap/investigations.md
  • apps/landing/src/content/roadmap/on-call.md
  • apps/landing/src/content/roadmap/product-events.md
  • apps/landing/src/content/roadmap/selfhosting-setup.md
  • apps/landing/src/content/roadmap/slos.md
  • apps/landing/src/content/roadmap/status-pages.md
  • apps/landing/src/content/roadmap/uptime-monitoring.md
  • apps/landing/src/lib/feature-plan.ts
  • apps/landing/src/lib/feature-sections.ts
  • apps/landing/src/lib/features.ts
  • apps/landing/src/lib/page-registry.ts
  • apps/landing/src/lib/pricing-offer.ts
  • apps/landing/src/pages/features/[slug].md.ts
  • apps/landing/src/pages/llms.txt.ts
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@maple-review-bot

maple-review-bot Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Maple review

🟢 Confidence 10/10 · safe to merge. The only delta since the reviewed commit is a two-line type fix in one Astro file, and it type-checks the icon lookup without changing what renders.
no findings · tests covered · risk low

The delta since the last review is a two-line change in ProductEventsSources.astro that replaces the inline icon strings with an ICONS map inferred from PRODUCT_EVENT_SOURCES's labels. The cards still render the same label, title, body, file, snippet and docs link.

  • ProductEventsSources.astro icons come from an ICONS map checked against the source labels
  • Card fields are read from PRODUCT_EVENT_SOURCES, with messages called per render

624c519 · What was checked, coverage and telemetry details are on the Maple / review check. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.

This branch has not been deployed

No deployments
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