mirror of
https://github.com/supabase/supabase.git
synced 2026-10-11 12:25:05 +03:00
This adds some pages that will be needed soon. Fixes https://linear.app/supabase/issue/API-901/ship-studio-authentication-confirmation-page Used by https://github.com/supabase/platform/pull/29718 Here are some screenshots of the 3 possible scenarios (initiated by the Management API): > [!NOTE] > As part of this flow, a new account + and a free organization will be created. ### Initializing the confirmation flow <img width="2708" height="1426" alt="CleanShot 2026-02-27 at 13 44 01@2x" src="https://github.com/user-attachments/assets/e5a90886-43a9-4202-ad81-fb42c13da036" /> ### Confirmation page <img width="2610" height="1640" alt="CleanShot 2026-02-27 at 13 44 20@2x" src="https://github.com/user-attachments/assets/8491fe24-c183-4987-a1c4-3d9b26dec9c3" /> ### In the event of going through a flow with a different signed-in account <img width="1982" height="1564" alt="CleanShot 2026-02-27 at 13 47 44@2x" src="https://github.com/user-attachments/assets/8a50b4c7-3fa4-4f6a-9d6f-b8776975b676" /> --------- Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
Writing pages
Rough guidelines
- Try to break down your pages into smaller building blocks - components which are tightly coupled to a page can be placed within the folder
components/interfaces/xxx/...(Refer to the README.md under the components folder) - Keep to using
useStatehooks for any UI related logic, do not create MobX local stores to handle UI logic.
Template for building pages
import { NextPage } from 'next'
import { withAuth } from 'hooks/misc/withAuth'
// Import the corresponding layout based on the page
import { Layout } from 'components/layouts'
// Import the main building blocks of the page
import { ... } from 'components/interfaces/xxx'
// Import reusable UI components if needed
import { ... } from 'components/ui/xxx'
// Name your page accordingly
const Page: NextPage = () => {
return (
<Layout>
<div>Page content</div>
</Layout>
)
}
export default withAuth(Page)