mirror of
https://github.com/supabase/supabase.git
synced 2026-10-07 02:15:05 +03:00
3f205627e0
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Feature — the visual redesign itself. Part 5 of 6 in a stack that splits the library redesign into reviewable pieces. The four PRs beneath it carry the build, content and Markdown work; what's left here is layout, navigation and styling. ## What is the current behavior? The library is laid out like a documentation site: a sidebar tree of framework folders, a homepage that lists links, and a guide page that opens with prose. That shape suits reference material, but the library's job is to help someone find a block and install it — and the sidebar is the only way to discover one. ## What is the new behavior? The homepage is the catalog itself — blocks grouped by what they do (authentication, database, storage, realtime, messaging, AI, foundations) rather than by framework, each with a preview of what it renders, filterable by category. Navigation moves into a site header whose Explore menu opens the same categories, so the catalog is reachable from any page and the per-page sidebar tree is gone. A guide opens with what the reader came for: the block's name, the install command, and a preview pane with tabs — the running component and its files — before any prose. The file tree that used to sit mid-page under "Folder structure" is one of those tabs. Every guide also offers a copy of the agent prompt that points at its Markdown. Getting-started pages get the same treatment: the quickstart is now a framework-tabbed walkthrough rather than a wall of setup links. ## Additional context `BlockOverviewTabs` renders Preview and Files here. #50369, stacked on top of this one, adds the third "What's added" tab — it is the only part of the redesign that depends on the new resource analyzer, which is why it sits above this PR rather than below it. Also removes what the redesign orphaned: the table-of-contents component and its `remark` / `mdast-util-toc` dependencies, and the sidebar nav and command-item configuration the new header replaced. The block source changes are typography only — auth card titles move from `text-2xl` to `font-medium text-lg tracking-normal` — which is what regenerates the auth registry artifacts. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a redesigned Supabase Library catalog with categorized blocks, framework-aware navigation, previews, file views, and installation actions. * Added framework-specific quickstart guides for Next.js, React, Vue, Nuxt, React Router, and TanStack Start. * Added copy-to-clipboard prompts, “Open in v0” actions, starter templates, and richer visual previews. * **Improvements** * Updated documentation layouts, FAQ content, typography, navigation, accessibility, and responsive behavior. * Improved mobile navigation, framework selection, and standardized block installation guidance. * Refined authentication and social-login block presentation with more consistent heading styles. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Danny White <3104761+dnywh@users.noreply.github.com>
85 lines
2.8 KiB
Plaintext
85 lines
2.8 KiB
Plaintext
---
|
|
title: Headless App
|
|
description: A backend with an agent as the primary interface
|
|
preview: |-
|
|
<BlockOverview name="headless-app-tanstack" showFiles>
|
|
<BlockPreview name="headless-app" />
|
|
</BlockOverview>
|
|
---
|
|
|
|
A headless app uses an AI agent as its primary interface. Users sign in and
|
|
approve access in the browser, then work through their agent using MCP tools.
|
|
This starter includes task tools and a database with Row Level Security (RLS)
|
|
that limits each user to their own data.
|
|
|
|
## Installation
|
|
|
|
Create a TanStack Start app:
|
|
|
|
```bash
|
|
pnpm dlx shadcn@latest init --template start --name my-app
|
|
cd my-app
|
|
```
|
|
|
|
Install the headless app:
|
|
|
|
<BlockItem name="headless-app-tanstack" showOpenInV0={false} />
|
|
|
|
Merge `supabase/config.toml` if you already have project settings. Add
|
|
`"supabase/functions/**"` to your app's `tsconfig.json` exclusions.
|
|
|
|
## Customize
|
|
|
|
- Set `VITE_PRODUCT_NAME` in `.env.local` and edit the generated pages and components.
|
|
- Define your tables, grants, and RLS policies in `supabase/schemas/`.
|
|
- Replace `supabase/functions/mcp-server/tools/tasks.ts` with your app's operations
|
|
and register them in `tools/index.ts`. Use the supplied user-scoped `supabase` client.
|
|
- Set `MCP_SERVER_NAME` and `MCP_SERVER_DESCRIPTION` with `supabase secrets set`.
|
|
|
|
## Deploy
|
|
|
|
Deploy the frontend using a [TanStack Start hosting adapter](https://tanstack.com/start/latest/docs/framework/react/guide/hosting).
|
|
Set these environment variables in your hosting provider before building:
|
|
|
|
```env
|
|
VITE_SUPABASE_URL=https://<project-ref>.supabase.co
|
|
VITE_SUPABASE_PUBLISHABLE_KEY=<publishable-key>
|
|
VITE_PRODUCT_NAME="Your app"
|
|
```
|
|
|
|
In `supabase/config.toml`, set `auth.site_url` to your deployed HTTPS origin,
|
|
update `auth.additional_redirect_urls` for your app's destinations, and set
|
|
`auth.email.enable_confirmations = true`. Keep the supplied OAuth and function settings.
|
|
Use an ES256 or RS256 signing key in your project's
|
|
[JWT Keys](https://supabase.com/dashboard/project/_/settings/jwt).
|
|
|
|
In [Email Templates](https://supabase.com/dashboard/project/_/auth/templates),
|
|
use this confirmation link for sign-up and change `type=email` to `type=recovery`
|
|
for password reset:
|
|
|
|
```html
|
|
<a
|
|
href="{{ .SiteURL }}/auth/confirm?token_hash={{ .TokenHash }}&type=email&next={{ .RedirectTo | urlquery }}"
|
|
>Confirm email</a
|
|
>
|
|
```
|
|
|
|
With the [Supabase CLI](https://supabase.com/docs/guides/local-development/cli/getting-started)
|
|
(2.117.0 or later) and Docker installed, generate a migration:
|
|
|
|
```bash
|
|
supabase db diff -f create_tasks
|
|
```
|
|
|
|
Review the migration, including grants and RLS policies, then deploy:
|
|
|
|
```bash
|
|
supabase link --project-ref <project-ref>
|
|
supabase db push
|
|
supabase config push
|
|
supabase functions deploy mcp-server
|
|
```
|
|
|
|
Open `/agents` on your deployed app, sign in, and copy the server URL into an
|
|
MCP client that supports HTTP and OAuth. Approve access to start using your tools.
|