* Update nextjs.mdx
just a little comment.. that save LOTS OF DEBUGGING time.
* fix: tweak wording
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
Partials are currently defined via MDX includes. This PR switches to pre-compile-time partials, which have a new syntax:
```
<$Partial path="path/to/file.mdx" />
```
## Rationale
This produces two improvements:
1. Partial substitution can occur in pipelines that don't use MDX compilation. For example, we can now do partial substitution before building the search index, so partial content will also be indexed.
2. After the App Router migration, the MDXProviders should've been deprecated, but were kept around for the sole reason of making partials work, and leading to us shipping unnecessary client-side code. We get a minor decrease in overall client bundle size (5.74 MB to 5.6 MB) by getting rid of the Providers.
## Breaking changes
Besides the change to partial syntax, the arguments are also less powerful than before because we are doing string substitution and don't have the full power of JS. Defining string variables is still possible (documented in the Contributing guide), and since that's all we actually do in practice, this shouldn't be too cumbersome. There is always the escape hatch of making a custom component for more complex content reuse cases.
* deleted all old pages except from FAQs
* added pricing section to feature docs pages
* adjusted all links to new pages (on Dashboard, in docs, on Pricing page)
* configured redirects from old billing docs pages to new pages
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
Co-authored-by: Kevin Grüneberg <k.grueneberg1994@gmail.com>
The docs directed to localhost:3000/login
It seems the nextjs template now has a new route `/sign-in`
Added note:
the route does not become available until .env.local is in env
* docs: state that whatsapp is only supported for Twilio
* docs: update format in callout
* docs: include twilio verify
* fixing capitalization
---------
Co-authored-by: Brian B (theOtherBrian1) <brian@supabase.io>
The purpose of this change is to reduce the bounce back rate of
the default email provider at Supabase. This change will allow
users to continue copying examples from the docs. Without it, an
upcoming change in supabase/auth[1] will begin rejecting these
invalid emails.
[1] https://github.com/supabase/auth/pull/1845
Co-authored-by: Chris Stockton <chris.stockton@supabase.io>
* docs(auth): update PKCE flow and Next.js example for password-based auth
Update the password-based authentication documentation to improve consistency and clarity:
- Add email redirect information to PKCE flow, mirroring the Implicit flow section
- Align the Next.js example in app/auth/confirm/route.ts with the official Supabase documentation for server-side auth in Next.js
- Update email template to include 'next' parameter for better redirect handling
- Improve error handling and redirect logic in the Next.js example
These changes aim to provide a more comprehensive and consistent guide for implementing password-based authentication, especially for Next.js applications using the PKCE flow.
Ref: https://supabase.com/docs/guides/auth/server-side/nextjs
* fix(docs): format email confirmation link and update sign-up function example
