* docs: Maturity model - making it even clearer
* Update apps/docs/content/guides/platform/maturity-model.mdx
* Update apps/docs/content/guides/platform/maturity-model.mdx
* remove hardcoded part from the link
---------
Co-authored-by: Rodrigo Mansueli Nunes <rodrigo@mansueli.com>
Update nextjs.mdx
The example env file created with `npx create-next-app -e with-supabase` is called .env.example, not .env.example.local. This updates the getting started doc to reflect that.
This will make the page load if not logged in and eliminate the following error message:
Error: NG04014: Invalid configuration of route '/': path cannot start with a slash
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
* docs: fix incorrect .js extension with .ts extension
Within the SvelteKit example, the guide incorrectly references creating a .js file as opposed to a .ts as is required, given the contents of said file has Typescript within it
* Update apps/docs/pages/guides/auth/server-side/email-based-auth-with-pkce-flow-for-ssr.mdx
* run formatter
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
Co-authored-by: dshukertjr <dshukertjr@gmail.com>
* Minor correction to FCM Push Notifications Guide
Hi,
Just some minor edits to the FCM guide I wanted to share.
Thanks,
Ronan O'Driscoll
* Apply suggestions from code review
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
* fix: Code sample to get image URL using Supabase Storage
* Update apps/docs/pages/guides/storage/serving/downloads.mdx
* remove error for getPublicUrl
* run formatter
Begin the process of moving our MDX files into their own content directory.
Fixed a few minor bugs re: ToC and tabs not rerendering consistently on page navigation. (The ToC thing wasn't a problem before the refactor, the tabs thing is a problem on prod.)
Moved MDX files can't import their own components, so everything they require needs to be back in the component prop for mdx-remote's serializer. Cleaned this up a bit and lazy-loaded heavy/rare stuff. Also, the component prop doesn't take arbitrary objects (only actual components), so imported data has to be wrapped in a component.
Tyler