Update understand-page-design.mdx

Added all pages to custom page list

Author: clairekinde11

src/content/docs/design/customize-with-code/understand-page-design.mdx

@@ -144,7 +144,7 @@ If you are using React for templating, note this code is rendered on the server.
 
 </Aside>
 
-### Page structure in the Git directory
+## Page structure in the Git directory
 
 The code for your pages must live in a GitHub repository (other git providers to be supported later). Your directory structure in the repo is critical to Kinde being able to run your design code.
 
@@ -162,7 +162,7 @@ myApp/
   └── kinde.json
 ```
 
-### Kinde.json
+## Kinde.json
 
 The `kinde.json` file defines the config for all custom code in Kinde, including workflows and custom pages. A typical config file will look as follows:
 
@@ -177,13 +177,19 @@ The `kinde.json` file defines the config for all custom code in Kinde, including
 
 `version` - based on the date when the API version was released. Any breaking changes will be released in a new API version.
 
-### Which pages can I customize?
+## Which pages can I customize?
 
 All Kinde hosted pages can be customized and use url route mapping to determine which template to use.
 
 If a specific mapped route does not exist, a special route called `(default)` will be rendered. Set up the `(default)` page to ensure all your pages follow this design unless you have overridden them with custom code.  
 
-Available routes:
+<Aside type="warning">
+
+Once you start customizing pages, it's on you not to break them. We recommend always applying custom code to pages in a non-prod environment first.
+
+</Aside>
+
+Common routes
 
 `(default)` - The page template that will be used for all Kinde hosted pages when a specific one cannot be found.
 
@@ -193,9 +199,73 @@ Available routes:
 
 `(index)` - If someone visits the root domain for your business, e.g. `https://<yourdomain>.kinde.com`
 
+Errors
+
+`(account_locked)`
+
+`(account_not_found)`
+
+`(error)`
+
+`(invalid_redirect_url)`
+
+Authentication & MFA
+
+`(clickwrap)`
+
+`(sso_home_realm)`
+
+`(provide_email)`
+
+`(mfa_authenticator_app)`
+
+`(mfa_method_selection)`
+
+`(mfa_setup_email)`
+
+`(mfa_setup_phone)`
+
+`(mfa_use_email_otp)`
+
+`(mfa_use_phone_otp)`
+
+`(mfa_use_recovery_code)`
+
+`(mfa_view_recovery_codes)`
+
+Passwords
+
+`(reset_password)`
+
+`(reset_password_verify_email_otp)`
+
+`(set_password)`
+
+`(verify_password)`
+
+Verify code
+
+`(sign_in_sign_up_use_phone_otp)`
+
+`(sign_in_use_email_otp)`
+
+`(sign_up_use_email_otp)`
+
+`(subscription_success)`
+
+Other routes
+
+`(request_access)` - before you launch and want to collect subscribers
+
+`(request_access_success)`
+
+`(choose_plan)` - coming soon, relates to billing
+
+`(collect_payment_details)` - coming soon, related to billing
+
 If you want specific customization for a page not listed here, reach out and let us know.
 
-### Set the page default export function
+## Set the page default export function
 
 Your `page.[ext]` file should contain a default export. It doesn’t matter what this is called, but the general convention is to call it `Page`. This is provided a single `event` argument which is an object containing 2 keys `context` and `request`.
 
@@ -225,7 +295,7 @@ The top level `context` key object contains information about the page itself, l
         - `description` the page description
         - `logoAlt` the alt text for your company logo
 
-### Page settings
+## Page settings
 
 Sometimes additional information needs to be passed to Kinde from your page. You can use the page settings object for this.