caelum0x 5f76bc68fa feat(ai-discoverability): add llms.txt/llms-full.txt/ai.txt + markdown mirror
mail.scribase.com was missing the llmstxt.org/ai-visibility.org.uk
AI-discoverability pass already shipped this session for scribase.com,
HomePlan, Bidstage, Yokharita Web and Railyard Vend/Toolgate/Insights.

Real finding: apps/web's root page (the only thing actually deployed to
mail.scribase.com) always redirects an anonymous visitor straight to
/login -- there is no marketing/pricing HTML live at `/` today, even
though apps/marketing (real written Resend-alternative copy, d806795) was
fully built and never wired into deploy/compose or Caddy. Rather than
invent new copy or silently pretend a page is live, the new /llms.txt,
/llms-full.txt, /index.md and /ai.txt routes mirror that real,
already-authored apps/marketing copy (hero, Resend-alternative
positioning, features, "Part of Scribase") into the surface that IS
actually deployed, with prices pulled live from the shared
PRICING_PLANS source of truth so they can't drift.

- apps/web/src/lib/ai-content/mail-pages.ts: real content + AI_SUMMARY
- app/llms.txt, app/llms-full.txt, app/ai.txt: new public routes
- app/index.md: per-page markdown mirror with the established header
  contract (text/markdown, X-Robots-Tag: noindex/follow, canonical Link)
- app/layout.tsx: <meta name="ai-summary"> + <link rel="alternate"
  type="text/markdown"> on the shared root metadata
- login-page.tsx: footer link to /llms.txt next to the existing AGPL
  source-code link

Verified locally against a real throwaway Postgres+Redis (not mocked):
next build clean, tsc clean, 665/665 unit tests unchanged, all 4 new
routes curled with correct content-type/headers/body, bogus paths still
404, and the metadata/footer-link changes confirmed present in the real
rendered page payload and compiled bundle.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-11-07 20:54:24 +03:00
..
2025-09-03 08:21:55 +10:00
2024-03-19 09:34:23 +11:00
2024-03-19 09:34:23 +11:00
2025-09-03 08:21:55 +10:00

Create T3 App

This is a T3 Stack project bootstrapped with create-t3-app.

What's next? How do I make an app with this?

We try to keep this project as simple as possible, so you can start with just the scaffolding we set up for you, and add additional things later when they become necessary.

If you are not familiar with the different technologies used in this project, please refer to the respective docs. If you still are in the wind, please join our Discord and ask for help.

Learn More

To learn more about the T3 Stack, take a look at the following resources:

You can check out the create-t3-app GitHub repository — your feedback and contributions are welcome!

How do I deploy this?

Follow our deployment guides for Vercel, Netlify and Docker for more information.