Skip to content

Update understand-page-design.mdx#429

Merged
clairekinde11 merged 2 commits intomainfrom
feat/custom-ui-pages
May 30, 2025
Merged

Update understand-page-design.mdx#429
clairekinde11 merged 2 commits intomainfrom
feat/custom-ui-pages

Conversation

@clairekinde11
Copy link
Copy Markdown
Contributor

@clairekinde11 clairekinde11 commented May 29, 2025

Added all pages to custom page list

Summary by CodeRabbit

  • Documentation
    • Improved heading structure for better readability.
    • Added a warning to recommend testing custom code in non-production environments first.
    • Expanded and clarified the list of customizable routes, including new categories and upcoming billing-related routes.
    • Made minor formatting and clarification updates for enhanced understanding.

Added all pages to custom page list
@clairekinde11 clairekinde11 requested a review from DaveOrDead May 29, 2025 08:35
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 29, 2025

"""

Walkthrough

The documentation was updated to adjust heading levels for major sections, add a warning about customizing routes in production, and significantly expand the list of customizable routes with new categories and route names. Minor formatting improvements and clarifications were also made, without altering any functional descriptions.

Changes

File(s) Change Summary
src/content/docs/design/customize-with-code/understand-page-design.mdx Adjusted heading levels, added a warning aside, expanded and categorized customizable routes, and made minor formatting and clarification updates.

Suggested reviewers

  • DaveOrDead

Poem

In docs we hop, with headings tall,
Warnings now guide, so no one will fall.
New routes abound—so many to see!
Customizing safely, as easy as can be.
With every tweak, the docs grow bright,
A rabbit’s work, done just right! 🐇✨
"""


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 220ff06 and 1528717.

📒 Files selected for processing (1)
  • src/content/docs/design/customize-with-code/understand-page-design.mdx (5 hunks)
🔇 Additional comments (4)
src/content/docs/design/customize-with-code/understand-page-design.mdx (4)

147-147: Section promoted to H2 as intended
Updating “Page structure in the Git directory” from H3 to H2 correctly elevates its importance in the document hierarchy.


165-165: Updated Kinde.json section to H2
The “Kinde.json” heading is now an H2, matching the pattern for major sections.


180-180: Elevated “Which pages can I customize?” to H2
Promoting this section to H2 aligns it with other top-level topics.


186-190: Added warning aside for non-production testing
The new <Aside type="warning"> block effectively reminds users to apply custom code in a non-production environment first, which is a valuable best practice.


</Aside>

Common routes
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Missing markdown for “Common routes” heading
The “Common routes” line is not prefixed with a heading marker. It should be defined as an H3 (e.g., ### Common routes) under the current H2 context to maintain consistent styling.
Please apply:

- Common routes
+ ### Common routes
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Common routes
### Common routes
🤖 Prompt for AI Agents
In src/content/docs/design/customize-with-code/understand-page-design.mdx at
line 192, the text "Common routes" is missing the markdown heading syntax. Add
the H3 markdown prefix by changing the line to "### Common routes" to ensure
consistent heading styling under the current H2 context.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented May 29, 2025

Deploying kinde-docs-previews with  Cloudflare Pages  Cloudflare Pages

Latest commit: bac54d0
Status: ✅  Deploy successful!
Preview URL: https://3f02ef59.kinde-docs-previews.pages.dev
Branch Preview URL: https://feat-custom-ui-pages.kinde-docs-previews.pages.dev

View logs


`(index)` - If someone visits the root domain for your business, e.g. `https://<yourdomain>.kinde.com`

Errors
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a stab at some groupings

## Common pages

These are the most frequently used or fallback pages.

* `(default)` – Fallback template used when a specific page is not found.
* `(register)` – The sign-up page.
* `(login)` – The sign-in page.
* `(index)` – Landing page when visiting the root domain (e.g. `https://<yourdomain>.kinde.com`).

## Authentication

Pages involved in initiating authentication flows.
* `(register)` – The sign-up page.
* `(login)` – The sign-in page.
* `(sso_home_realm)` – Displayed when a user selects “Continue with SSO” to choose their identity provider.
* `(provide_email)` – Shown when using a social login provider that does not return an email address.
* `(clickwrap)` – Displays terms and conditions or agreements that must be accepted.

## Password flows

Used in password-based authentication and recovery.

* `(verify_password)` – Shown during sign-in when using a password-based method.
* `(set_password)` – Shown during a password-based sign-up flow.
* `(reset_password_verify_email_otp)` – First step of the reset flow where the user verifies identity using an email OTP.
* `(reset_password)` – Password entry screen shown after verification during the reset flow.

## One-Time Passcode (OTP) verification

Used in sign-in and sign-up flows with OTP (email or phone).

* `(sign_in_use_email_otp)` – Sign in with a one-time email code.
* `(sign_up_use_email_otp)` – Sign up with a one-time email code.
* `(sign_in_sign_up_use_phone_otp)` – Sign in or sign up with a one-time phone code.

## Multi-Factor Authentication (MFA)

Shown after primary authentication when MFA is required or being set up.

* `(mfa_method_selection)` – User selects their preferred MFA method.
* `(mfa_authenticator_app)` – Setup screen for using an authenticator app.
* `(mfa_setup_email)` – Setup screen for email-based MFA.
* `(mfa_setup_phone)` – Setup screen for phone-based MFA.
* `(mfa_use_email_otp)` – Enter a one-time email code for MFA.
* `(mfa_use_phone_otp)` – Enter a one-time phone code for MFA.
* `(mfa_use_recovery_code)` – Enter a recovery code if unable to use other MFA methods.
* `(mfa_view_recovery_codes)` – View and save MFA recovery codes.

## Billing (coming soon)

Pages related to choosing a plan and making a payment.

* `(choose_plan)` – User selects a subscription plan.
* `(collect_payment_details)` – User enters billing information.
* `(subscription_success)` – Confirmation page shown after successful subscription.

## Early access

Pages for gated access to your product before full launch.

* `(request_access)` – Request early access to your product.
* `(request_access_success)` – Confirmation page after a request is submitted.

## Error pages

Shown when a user encounters an error state.

* `(account_locked)` – The user’s account has been locked.
* `(account_not_found)` – No account was found for the entered credentials.
* `(invalid_redirect_url)` – The redirect URL is invalid or not on the allowed list.
* `(error)` – Generic error screen.

Updated list with Dave's definitions
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
src/content/docs/design/customize-with-code/understand-page-design.mdx (4)

186-190: Ensure consistent <Aside> usage

The new <Aside type="warning"> admonition clearly warns about production pitfalls. The earlier <Aside> at lines 141–145 uses the default type; consider explicitly specifying its type (e.g., type="info") to maintain consistency across all asides.


192-200: Avoid duplicate entries across categories

In the “Common pages” list, (register) and (login) also appear under “Authentication.” If the intent is to distinguish overall fallback pages from flow-specific pages, consider adding a clarifying note or removing duplicates to prevent confusion.


214-214: Improve grammar in bullet description

At (verify_password), consider including an article for clarity, e.g.:
* (verify_password) – Shown during the sign-in process when using a password-based method.

🧰 Tools
🪛 LanguageTool

[grammar] ~214-~214: Before the countable noun ‘during’ an article or a possessive pronoun is necessary.
Context: .... * (verify_password) – Shown during sign-in when using a password-based method. * `...

(IN_NN_CC_VBG)


242-242: Consider more concise phrasing

The sentence “Pages related to choosing a plan and making a payment.” could be streamlined to “Pages for plan selection and payment processing.”

🧰 Tools
🪛 LanguageTool

[style] ~242-~242: ‘making a payment’ might be wordy. Consider a shorter alternative.
Context: ...) Pages related to choosing a plan and making a payment. * (choose_plan) – User selects a su...

(EN_WORDINESS_PREMIUM_MAKING_A_PAYMENT)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1528717 and bac54d0.

📒 Files selected for processing (1)
  • src/content/docs/design/customize-with-code/understand-page-design.mdx (4 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/design/customize-with-code/understand-page-design.mdx

[grammar] ~214-~214: Before the countable noun ‘during’ an article or a possessive pronoun is necessary.
Context: .... * (verify_password) – Shown during sign-in when using a password-based method. * `...

(IN_NN_CC_VBG)


[style] ~242-~242: ‘making a payment’ might be wordy. Consider a shorter alternative.
Context: ...) Pages related to choosing a plan and making a payment. * (choose_plan) – User selects a su...

(EN_WORDINESS_PREMIUM_MAKING_A_PAYMENT)

🔇 Additional comments (6)
src/content/docs/design/customize-with-code/understand-page-design.mdx (6)

147-147: Promoted main section headings to level 2

The sections “Page structure in the Git directory”, “Kinde.json”, and “Which pages can I customize?” have been elevated from H3 to H2. This improves the document hierarchy—please confirm it aligns with the overall outline and table of contents.

Also applies to: 165-165, 180-180


201-208: Authentication category is well-defined

The “Authentication” section clearly lists the relevant pages with concise descriptions. Formatting and terminology are consistent.


219-225: OTP verification section is clear

The “One-Time Passcode (OTP) verification” category and its bullet points are well-structured and easy to follow.


227-238: MFA section looks solid

The “Multi-Factor Authentication (MFA)” list is comprehensive and the descriptions are clear.


248-253: Early access section looks good

The “Early access” category and its descriptions are concise and consistent.


255-262: Error pages section is well-structured

The “Error pages” category and its bullet points are correctly formatted and informative.

@clairekinde11 clairekinde11 requested a review from DaveOrDead May 29, 2025 23:49
@clairekinde11 clairekinde11 merged commit 3c9f685 into main May 30, 2025
6 checks passed
@clairekinde11 clairekinde11 deleted the feat/custom-ui-pages branch May 30, 2025 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants