Conversation
New page
Update to sidebar category name
Index topic
index topic
New section
delete error section
Index topic
Index topic
Index topic
Delete old index topic
GS step
step topic
New topic
Intro topci
Draft 1
Draft 1
Draft 1
WalkthroughThis update adds extensive documentation for Kinde's new billing feature, covering billing concepts, plan creation and management, pricing tables, Stripe integration, and setup steps. It removes an outdated billing preview page and updates the sidebar navigation to feature a reorganized "Billing" section with multiple subtopics. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant KindeApp
participant Stripe
User->>KindeApp: Begin billing setup
KindeApp->>User: Prompt for billing role, currency, plans, etc.
User->>KindeApp: Configure billing role and currency
User->>KindeApp: Build and publish plans
KindeApp->>Stripe: Sync plans and features
User->>KindeApp: Connect Stripe account
KindeApp->>Stripe: Initiate Stripe onboarding
Stripe-->>User: Complete onboarding (test or production)
Stripe-->>KindeApp: Confirm connection
User->>KindeApp: Create pricing table (optional)
User->>KindeApp: Enable self-serve portal (optional)
User->>KindeApp: Test and review setup
Poem
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (29)
src/content/docs/billing/payment-management/payment-gateway.mdx (1)
1-10: Populate or remove empty frontmatter lists
TherelatedArticlesandapp_contextentries are left as single hyphens with no values. For clarity and YAML validity, either fill these with actual links/context or convert them to empty arrays (relatedArticles: [],app_context: []).src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx (1)
1-8: Add page content or TODO placeholder
The file currently contains only frontmatter and no body text. Please include at least a brief introduction or a “Coming soon” note, and consider adding anapp_contextfield (as in other billing docs) or remove unused metadata keys.src/content/docs/billing/pricing/pricing-models.mdx (1)
1-9: Clarify relatedArticles/app_context usage
BothrelatedArticlesandapp_contextare empty placeholders. If there are no entries yet, switch to explicit empty arrays (relatedArticles: [],app_context: []), and add a placeholder section in the body for the eventual pricing model overview.src/content/docs/billing/payment-management/manage-stripe-connection.mdx (1)
1-8: Specify a sidebar order value
sidebar.orderis blank, which will break navigation ordering. Assign an integer (e.g.,order: 2) to position this page correctly under the Payment Management section.src/content/docs/billing/manage-plans/create-plans.mdx (1)
1-11: Include initial content or outline
This page has rich frontmatter but no content. Please add at least a high-level outline or a placeholder paragraph under the metadata so reviewers have context on “Create plans” before filling in detailed instructions.src/content/docs/billing/get-started/self-serve-portal-setup.mdx (1)
12-12: Use consistent hyphenation and verb form
Apply hyphens and adjust wording for clarity:- Aside from account management, the self serve portal is for orgs to self manage teams and business information, and individuals to manage their user profile. + Aside from account management, the self-serve portal is for organizations to self-manage teams and business information, and for individuals to manage their user profile.🧰 Tools
🪛 LanguageTool
[grammar] ~12-~12: “Self” is a singular noun. It appears that the verb form is incorrect.
Context: ...Aside from account management, the self serve portal is for orgs to self manage teams...(PCT_SINGULAR_NOUN_PLURAL_VERB_AGREEMENT)
[misspelling] ~12-~12: This word is normally spelled with a hyphen.
Context: ...t, the self serve portal is for orgs to self manage teams and business information, and ind...(EN_COMPOUNDS_SELF_MANAGE)
src/content/docs/billing/get-started/publish-plans.mdx (1)
14-14: Refine wording for conciseness and readability
Consider removing “of” and adding a comma for better flow:- When you publish a plan, all of the plan features and charges are synced to Stripe where they are transformed into products that users can buy. + When you publish a plan, all the plan features and charges are synced to Stripe, where they are transformed into products users can buy.🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Consider removing “of” to be more concise
Context: ...: details --- When you publish a plan, all of the plan features and charges are synced to...(ALL_OF_THE)
[uncategorized] ~14-~14: Possible missing comma found.
Context: ...plan features and charges are synced to Stripe where they are transformed into product...(AI_HYDRA_LEO_MISSING_COMMA)
src/content/docs/billing/about-billing/billing-concepts-terms.mdx (2)
28-28: Clarify and correct hyphenation in bullet
The sentence is incomplete and “per-unit” should be hyphenated:- Might be metered or per unit price. + It might be metered or per-unit priced.🧰 Tools
🪛 LanguageTool
[style] ~28-~28: To form a complete sentence, be sure to include a subject.
Context: ...**: Incurs an additional fee when used. Might be metered or per unit price. - **N...(MISSING_IT_THERE)
[grammar] ~28-~28: In this context, “per-unit” forms an adjective and is spelled with a hyphen.
Context: ...onal fee when used. Might be metered or per unit price. - Non-chargeable feature...(PER_USER_BASIS_HYPHEN)
39-40: Avoid repetitive sentence starts
The three sentences here all begin with “Unit prices.” Consider merging or rewording for readability:- Unit prices can also be applied to metered features, e.g. x per unit. Unit prices can also be tiered, e.g. x per unit up to 10 units, then y for 10+ units. + These prices can be applied to metered features (e.g., x per unit) or tiered (e.g., x per unit up to 10 units, then y thereafter).🧰 Tools
🪛 LanguageTool
[style] ~39-~39: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...d to metered features, e.g. x per unit. Unit prices can also be tiered, e.g. x per u...(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
src/content/docs/billing/get-started/add-billing-role.mdx (1)
21-21: Remove extra space before comma.Typographical: remove the space before the comma after the code span.
- Name the role, for example, `Billing Admin` , and enter a description and **Key**. + Name the role, for example, `Billing Admin`, and enter a description and **Key**.src/content/docs/billing/get-started/build-plans.mdx (2)
32-33: Simplify link text to avoid redundancy.The text “[example spreadsheet for plan planning]” repeats “plan planning.” Consider shortening it to improve clarity:
- [example spreadsheet for plan planning](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/401ff633-c6c8-45ba-9502-1a29274b4400/public) + [example spreadsheet](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/401ff633-c6c8-45ba-9502-1a29274b4400/public)🧰 Tools
🪛 LanguageTool
[grammar] ~33-~33: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...erything. [example spreadsheet for plan planning](https://imagedelivery.net/skPPZTHzSlcs...(REPEATED_VERBS)
37-37: Add consistent “Next” navigation for Get Started flow.For consistency with other get-started guides, consider replacing “See” with a “Next:” link to the subsequent step:
- **See [Create plans](/billing/manage-plans/create-plans)** + **Next:** [Step 5 Publish plans](/billing/get-started/publish-plans/)src/content/docs/billing/billing-user-experience/plan-selection.mdx (1)
13-13: Insert missing preposition.Grammar: add “of” in the phrase for clarity:
- You can build a pricing table to enable your customers to select plans and go through a payment flow as part signing up to your app or site. + You can build a pricing table to enable your customers to select plans and go through a payment flow as part of signing up to your app or site.🧰 Tools
🪛 LanguageTool
[uncategorized] ~13-~13: Possible missing preposition found.
Context: ...s and go through a payment flow as part signing up to your app or site. Kinde's pricin...(AI_HYDRA_LEO_MISSING_OF)
src/content/docs/billing/get-started/setup-overview.mdx (1)
14-14: Add missing article.Grammar: insert “a” before “big step”:
- Billing is big step for a business, so it’s a good idea to review the process before you start. + Billing is a big step for a business, so it’s a good idea to review the process before you start.🧰 Tools
🪛 LanguageTool
[uncategorized] ~14-~14: You might be missing the article “a” here.
Context: ...m: billing - s: plans --- Billing is big step for a business, so it’s a good ide...(AI_EN_LECTOR_MISSING_DETERMINER_A)
src/content/docs/billing/about-billing/about-billing.mdx (5)
6-10: Remove empty frontmatter fields.The
relatedArticlesandapp_contextarrays are empty. To keep the frontmatter clean and avoid confusion, remove these keys or populate them with actual entries if needed.
31-33: Provide a valid feedback link and adjust tone.The placeholder
[not sure where]needs to be replaced with the actual feedback channel (e.g. GitHub Discussions, support email). Also consider swapping “amazing” for a more formal term like “helpful” or “valuable.”🧰 Tools
🪛 LanguageTool
[style] ~33-~33: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... ### How to send feedback It would be amazing if you can send any feedback you have v...(AWESOME)
35-35: Unify section heading with other docs.Change “## Known limitations” to “## Current limitations” to match the heading in related billing pages (e.g., About plans).
39-43: Consistent bullet punctuation.Some bullets end with a period and others don’t. Please add a trailing period to all items for consistency:
- Support for plan models with free trial periods + Support for plan models with free trial periods. - Changes to the billing cycle (e.g. choose billing anniversaries, etc.) + Changes to the billing cycle (e.g. choosing billing anniversaries, etc.). - Add-ons and discounts that can be applied to individual subscriptions + Add-ons and discounts that can be applied to individual subscriptions. - Plan versioning + Plan versioning.🧰 Tools
🪛 LanguageTool
[grammar] ~41-~41: If ‘choose’ is used as a verb, it usually requires the infinitive.
Context: ...anges to the billing cycle (e.g. choose billing anniversaries, etc.) - Add-ons and disc...(AFFORD_VBG)
41-41: Fix verb form in example.Use the gerund “choosing” instead of “choose”:
- Changes to the billing cycle (e.g. choose billing anniversaries, etc.) + Changes to the billing cycle (e.g. choosing billing anniversaries, etc.)🧰 Tools
🪛 LanguageTool
[grammar] ~41-~41: If ‘choose’ is used as a verb, it usually requires the infinitive.
Context: ...anges to the billing cycle (e.g. choose billing anniversaries, etc.) - Add-ons and disc...(AFFORD_VBG)
src/content/docs/billing/manage-plans/about-plans.mdx (2)
12-12: Correct grammar: plural agreement.Replace “Here’s some examples:” with “Here are some examples:”:
- It’s common to support both basic and more advanced plans for SaaS services. Here’s some examples: + It’s common to support both basic and more advanced plans for SaaS services. Here are some examples:🧰 Tools
🪛 LanguageTool
[grammar] ~12-~12: Did you mean “Here are some examples”?
Context: ... more advanced plans for SaaS services. Here’s some examples: - A simple subscription plan: $10 per...(THERE_S_MANY)
40-40: Add missing preposition.Insert “on” after “Depending”:
- Depending how you manage plans and feature provisioning… + Depending on how you manage plans and feature provisioning…src/content/docs/billing/get-started/connect-to-stripe.mdx (3)
16-16: Hyphenate compound adjective.Use “third-party” instead of “third party”:
- This is a Stripe-imposed limitation for third party payment gateway integrations. + This is a Stripe-imposed limitation for third-party payment gateway integrations.🧰 Tools
🪛 LanguageTool
[uncategorized] ~16-~16: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...This is a Stripe-imposed limitation for third party payment gateway integrations. We’re wor...(EN_COMPOUND_ADJECTIVE_INTERNAL)
36-36: Use “depending on whether” for clarity.Change the phrasing for grammatical correctness:
- Here’s what happens next, depending if you have a Stripe account already associated with your email address. + Here’s what happens next, depending on whether you have a Stripe account already associated with your email address.🧰 Tools
🪛 LanguageTool
[grammar] ~36-~36: The verb ‘depend’ requires the preposition ‘on’ (or ‘upon’).
Context: ...t Submit. Here’s what happens next, depending if you have a Stripe account already as...(DEPEND_ON)
43-47: Remove extra spaces in bold text.Fix the spacing in the action prompt:
- Any time you want to complete the setup, select **Update Stripe information**. + Any time you want to complete the setup, select **Update Stripe information**.src/content/docs/billing/about-billing/kinde-billing-model.mdx (5)
12-13: Clarify sync description and list punctuation.Adjust commas and plurality:
- This involves a continuous sync between Kinde and Stripe, to ensure that products, prices, subscription information, invoice and payments, are accurate in both systems. + This involves a continuous sync between Kinde and Stripe to ensure that products, prices, subscription information, invoices, and payments are accurate in both systems.
18-18: Insert missing preposition.Change “Depending which you are setting up” to “Depending on which you are setting up”:
- Depending which you are setting up, you may need to do a few extra tasks. + Depending on which you are setting up, you may need to do a few extra tasks.🧰 Tools
🪛 LanguageTool
[grammar] ~18-~18: The verb ‘depend’ requires the preposition ‘on’ (or ‘upon’).
Context: ...ts billing models for both B2B and B2C. Depending which you are setting up, you may need ...(DEPEND_ON)
27-27: Add comma before conjunction.Insert a comma before “and” joining two independent clauses:
- Stripe securely stores your customer’s payment details and Kinde never sees credit card or other bank information. + Stripe securely stores your customer’s payment details, and Kinde never sees credit card or other bank information.🧰 Tools
🪛 LanguageTool
[uncategorized] ~27-~27: Possible missing comma found.
Context: ...securely stores your customer’s payment details and Kinde never sees credit card or oth...(AI_HYDRA_LEO_MISSING_COMMA)
37-37: Separate independent clauses with comma.Add a comma for clarity:
- Kinde has customers everywhere and almost every global currency is supported. + Kinde has customers everywhere, and almost every global currency is supported.🧰 Tools
🪛 LanguageTool
[uncategorized] ~37-~37: Possible missing comma found.
Context: ...ticurrency support Kinde has customers everywhere and almost every global currency is sup...(AI_HYDRA_LEO_MISSING_COMMA)
55-55: Hyphenate “sign-up anniversary”.- Billing cycles are monthly and are processed on the sign up anniversary + Billing cycles are monthly and are processed on the sign-up anniversary🧰 Tools
🪛 LanguageTool
[uncategorized] ~55-~55: The noun “sign-up” is spelled with a hyphen.
Context: ...es are monthly and are processed on the sign up anniversary - Invoices include fixed ch...(SIGN_UP_HYPHEN)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (20)
src/content/docs/billing/about-billing/about-billing.mdx(1 hunks)src/content/docs/billing/about-billing/billing-concepts-terms.mdx(1 hunks)src/content/docs/billing/about-billing/kinde-billing-model.mdx(1 hunks)src/content/docs/billing/about-payments-and-plans/index.mdx(0 hunks)src/content/docs/billing/billing-user-experience/plan-selection.mdx(1 hunks)src/content/docs/billing/get-started/add-billing-role.mdx(1 hunks)src/content/docs/billing/get-started/add-pricing-table.mdx(1 hunks)src/content/docs/billing/get-started/build-plans.mdx(1 hunks)src/content/docs/billing/get-started/connect-to-stripe.mdx(1 hunks)src/content/docs/billing/get-started/default-billing-currency.mdx(1 hunks)src/content/docs/billing/get-started/publish-plans.mdx(1 hunks)src/content/docs/billing/get-started/self-serve-portal-setup.mdx(1 hunks)src/content/docs/billing/get-started/setup-overview.mdx(1 hunks)src/content/docs/billing/manage-plans/about-plans.mdx(1 hunks)src/content/docs/billing/manage-plans/create-plans.mdx(1 hunks)src/content/docs/billing/payment-management/manage-stripe-connection.mdx(1 hunks)src/content/docs/billing/payment-management/payment-gateway.mdx(1 hunks)src/content/docs/billing/pricing/pricing-models.mdx(1 hunks)src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx(1 hunks)src/data/sidebarData.ts(1 hunks)
💤 Files with no reviewable changes (1)
- src/content/docs/billing/about-payments-and-plans/index.mdx
🧰 Additional context used
🪛 LanguageTool
src/content/docs/billing/get-started/self-serve-portal-setup.mdx
[grammar] ~12-~12: “Self” is a singular noun. It appears that the verb form is incorrect.
Context: ...Aside from account management, the self serve portal is for orgs to self manage teams...
(PCT_SINGULAR_NOUN_PLURAL_VERB_AGREEMENT)
[misspelling] ~12-~12: This word is normally spelled with a hyphen.
Context: ...t, the self serve portal is for orgs to self manage teams and business information, and ind...
(EN_COMPOUNDS_SELF_MANAGE)
src/content/docs/billing/about-billing/billing-concepts-terms.mdx
[style] ~28-~28: To form a complete sentence, be sure to include a subject.
Context: ...**: Incurs an additional fee when used. Might be metered or per unit price. - **N...
(MISSING_IT_THERE)
[grammar] ~28-~28: In this context, “per-unit” forms an adjective and is spelled with a hyphen.
Context: ...onal fee when used. Might be metered or per unit price. - Non-chargeable feature...
(PER_USER_BASIS_HYPHEN)
[style] ~39-~39: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...d to metered features, e.g. x per unit. Unit prices can also be tiered, e.g. x per u...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
src/content/docs/billing/get-started/publish-plans.mdx
[style] ~14-~14: Consider removing “of” to be more concise
Context: ...: details --- When you publish a plan, all of the plan features and charges are synced to...
(ALL_OF_THE)
[uncategorized] ~14-~14: Possible missing comma found.
Context: ...plan features and charges are synced to Stripe where they are transformed into product...
(AI_HYDRA_LEO_MISSING_COMMA)
src/content/docs/billing/get-started/setup-overview.mdx
[uncategorized] ~14-~14: You might be missing the article “a” here.
Context: ...m: billing - s: plans --- Billing is big step for a business, so it’s a good ide...
(AI_EN_LECTOR_MISSING_DETERMINER_A)
src/content/docs/billing/get-started/build-plans.mdx
[grammar] ~33-~33: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...erything. [example spreadsheet for plan planning](https://imagedelivery.net/skPPZTHzSlcs...
(REPEATED_VERBS)
src/content/docs/billing/billing-user-experience/plan-selection.mdx
[uncategorized] ~13-~13: Possible missing preposition found.
Context: ...s and go through a payment flow as part signing up to your app or site. Kinde's pricin...
(AI_HYDRA_LEO_MISSING_OF)
[style] ~63-~63: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...n**, depending on the plan position. 5. Select Save. ## Add a features list to a ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~87-~87: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...translate pricing table content If you want to display pricing tables in multiple lang...
(REP_WANT_TO_VB)
[uncategorized] ~109-~109: The noun “sign-up” is spelled with a hyphen.
Context: ...not passed in the URL during the normal sign up flow. 1. Open the pricing table. 2. Se...
(SIGN_UP_HYPHEN)
src/content/docs/billing/about-billing/about-billing.mdx
[uncategorized] ~18-~18: When ‘Implement-specific’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...ze a pricing table for plan selection - Implement specific pricing models to suit your product - U...
(SPECIFIC_HYPHEN)
[style] ~33-~33: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... ### How to send feedback It would be amazing if you can send any feedback you have v...
(AWESOME)
[grammar] ~41-~41: If ‘choose’ is used as a verb, it usually requires the infinitive.
Context: ...anges to the billing cycle (e.g. choose billing anniversaries, etc.) - Add-ons and disc...
(AFFORD_VBG)
src/content/docs/billing/manage-plans/about-plans.mdx
[grammar] ~12-~12: Did you mean “Here are some examples”?
Context: ... more advanced plans for SaaS services. Here’s some examples: - A simple subscription plan: $10 per...
(THERE_S_MANY)
[grammar] ~39-~39: The verb ‘depend’ requires the preposition ‘on’ (or ‘upon’).
Context: ...nternal use. ### Plan feature pricing Depending how you manage plans and feature provis...
(DEPEND_ON)
[style] ~42-~42: Consider simply using “of” instead.
Context: ...et up a plan, you can include a mixture of any of these options: - Fixed charges - a...
(OF_ANY_OF)
src/content/docs/billing/get-started/connect-to-stripe.mdx
[uncategorized] ~16-~16: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...This is a Stripe-imposed limitation for third party payment gateway integrations. We’re wor...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~32-~32: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... If the Stripe flow doesn’t appear and you remain in the Kinde dashboard, sele...
(COMMA_COMPOUND_SENTENCE)
[grammar] ~36-~36: The verb ‘depend’ requires the preposition ‘on’ (or ‘upon’).
Context: ...t Submit. Here’s what happens next, depending if you have a Stripe account already as...
(DEPEND_ON)
[style] ~54-~54: Consider a more concise word here.
Context: ...quires some additional details from you in order to fully set up the account. Select **Upda...
(IN_ORDER_TO_PREMIUM)
[uncategorized] ~55-~55: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... is successfully syncing data with Kinde and you’re ready to publish plans. For mor...
(COMMA_COMPOUND_SENTENCE)
src/content/docs/billing/about-billing/kinde-billing-model.mdx
[grammar] ~18-~18: The verb ‘depend’ requires the preposition ‘on’ (or ‘upon’).
Context: ...ts billing models for both B2B and B2C. Depending which you are setting up, you may need ...
(DEPEND_ON)
[uncategorized] ~27-~27: Possible missing comma found.
Context: ...securely stores your customer’s payment details and Kinde never sees credit card or oth...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~37-~37: Possible missing comma found.
Context: ...ticurrency support Kinde has customers everywhere and almost every global currency is sup...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~47-~47: Possible missing article found.
Context: ...="Financial compliance"> The region in Stripe indicates where the transaction informa...
(AI_HYDRA_LEO_MISSING_THE)
[uncategorized] ~55-~55: The noun “sign-up” is spelled with a hyphen.
Context: ...es are monthly and are processed on the sign up anniversary - Invoices include fixed ch...
(SIGN_UP_HYPHEN)
[style] ~57-~57: ‘in arrears’ might be wordy. Consider a shorter alternative.
Context: ...nce. - Invoices include metered charges in arrears, e.g. MAU is metered throughout a month...
(EN_WORDINESS_PREMIUM_IN_ARREARS)
🔇 Additional comments (4)
src/data/sidebarData.ts (1)
142-143: Missing nested items under the Billing section
The sidebar only lists “About payments and plans” but several new billing pages (concepts, model, pricing table, get-started steps, etc.) aren’t represented. Please update theitemsarray to include all relevant billing documentation entries and verify thatcardLinkandautogenerate.directorypaths match the actual file locations.Likely an incorrect or invalid review comment.
src/content/docs/billing/get-started/self-serve-portal-setup.mdx (2)
5-7: Confirm frontmatter configuration
Please verify thatsidebar.order: 8correctly follows the previous steps and thatrelatedArticlespoints to the intended preceding guide ID.
14-14: Verify link destination
Ensure the[Self-serve portal](/build/set-up-options/self-serve-portal-for-orgs/)URL exists and points to the correct setup guide.src/content/docs/billing/get-started/default-billing-currency.mdx (1)
1-17: Documentation looks good
The frontmatter and step-by-step instructions are clear and accurate.
| sidebar: | ||
| order: | ||
| relatedArticles: | ||
| - | ||
| app_context: | ||
| - | ||
| --- |
There was a problem hiding this comment.
Frontmatter incomplete
The sidebar.order, relatedArticles, and app_context fields are empty. Populate or remove unused frontmatter keys so the page renders correctly in the sidebar and related-links sections.
🤖 Prompt for AI Agents
In src/content/docs/billing/about-billing/billing-concepts-terms.mdx around
lines 4 to 10, the frontmatter fields sidebar.order, relatedArticles, and
app_context are empty. To fix this, either provide appropriate values for these
fields based on the page's context and related content or remove these keys
entirely if they are not needed, ensuring the page renders correctly in the
sidebar and related-links sections.
|
|
||
| To create your own, go to [Build a pricing table](/billing/billing-user-experience/plan-selection/). | ||
|
|
||
| If you have your own screen flows for plan display and selection, you do not have to use Kinde’s pricing tables. Here's how to use your own, and not Kinde's [Link to topic] |
There was a problem hiding this comment.
Replace placeholder link with actual doc reference.
The text at this line contains a placeholder [Link to topic]. Please replace this with the real document title and URL (for example, a “Custom plan display integration guide” link).
🤖 Prompt for AI Agents
In src/content/docs/billing/get-started/add-pricing-table.mdx at line 19,
replace the placeholder text "[Link to topic]" with the actual document title
and URL that explains how to use custom plan display and selection flows, such
as a "Custom plan display integration guide" link. Ensure the link is properly
formatted and points to the correct internal or external documentation.
| app_context: | ||
| - | ||
| --- |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix empty app_context entry.
The app_context frontmatter has an empty list item. Either remove this block or populate it to match similar pages (e.g., m: billing and s: pricing_tables):
- app_context:
- -
+ app_context:
+ - m: billing
+ - s: pricing_tables📝 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.
| app_context: | |
| - | |
| --- | |
| app_context: | |
| - m: billing | |
| - s: pricing_tables | |
| --- |
🤖 Prompt for AI Agents
In src/content/docs/billing/billing-user-experience/plan-selection.mdx around
lines 9 to 11, the frontmatter contains an empty list item under app_context
which should be fixed. Remove the empty list item or populate the app_context
field with appropriate values similar to other pages, for example, setting m:
billing and s: pricing_tables to ensure consistency and correctness in the
frontmatter metadata.
| 2. Set currency - you can’t change this once plans are published | ||
| 3. Connect to Stripe | ||
| 4. Build plans | ||
| 5. Publish plans | ||
| 6. Enable subscription self-serve (optional) | ||
| 1. Create a plan selector | ||
| 2. Enable self-serve portal | ||
| 7. Update your code | ||
| 8. Test the setup and get your first subscriber! |
There was a problem hiding this comment.
Include missing pricing table creation step.
The setup overview omits the optional step to create a pricing table. Please insert it before enabling the self-serve portal and renumber subsequent steps:
- 5. Publish plans
- 6. Enable subscription self-serve (optional)
- 1. Create a plan selector
- 2. Enable self-serve portal
- 7. Update your code
- 8. Test the setup and get your first subscriber!
+ 5. Publish plans
+ 6. Create pricing table (optional)
+ 7. Enable subscription self-serve (optional)
+ 1. Create a plan selector
+ 2. Enable self-serve portal
+ 8. Update your code
+ 9. Test the setup and get your first subscriber!📝 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.
| 2. Set currency - you can’t change this once plans are published | |
| 3. Connect to Stripe | |
| 4. Build plans | |
| 5. Publish plans | |
| 6. Enable subscription self-serve (optional) | |
| 1. Create a plan selector | |
| 2. Enable self-serve portal | |
| 7. Update your code | |
| 8. Test the setup and get your first subscriber! | |
| 2. Set currency - you can’t change this once plans are published | |
| 3. Connect to Stripe | |
| 4. Build plans | |
| 5. Publish plans | |
| 6. Create pricing table (optional) | |
| 7. Enable subscription self-serve (optional) | |
| 1. Create a plan selector | |
| 2. Enable self-serve portal | |
| 8. Update your code | |
| 9. Test the setup and get your first subscriber! |
🤖 Prompt for AI Agents
In src/content/docs/billing/get-started/setup-overview.mdx around lines 19 to
27, the setup steps miss the optional step to create a pricing table. Insert a
new step "Create a pricing table" before "Enable self-serve portal" under step
6, and renumber the subsequent sub-steps accordingly to maintain correct order.
Billing docs nav
Deploying kinde-docs-previews with
|
| Latest commit: |
5b8e7de
|
| Status: | 🚫 Build failed. |
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/data/sidebarData.ts(1 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
src/data/sidebarData.ts
[error] 153-154: expected , but instead found {
Remove {
(parse)
[error] 158-159: expected , but instead found {
Remove {
(parse)
[error] 163-164: expected , but instead found {
Remove {
(parse)
[error] 168-169: expected , but instead found {
Remove {
(parse)
[error] 173-174: expected , but instead found {
Remove {
(parse)
🔇 Additional comments (1)
src/data/sidebarData.ts (1)
142-178: Well-structured billing section organization.The expansion from a single "About payments and plans" item to multiple organized billing sections (About billing, Get started, Manage plans, Payment management, Pricing, Billing user experience) provides much better navigation structure for users. The updated description "Monetize your product, build plans, and accept payments" clearly communicates the billing feature's value proposition.
🧰 Tools
🪛 Biome (1.9.4)
[error] 153-154: expected
,but instead found{Remove {
(parse)
[error] 158-159: expected
,but instead found{Remove {
(parse)
[error] 163-164: expected
,but instead found{Remove {
(parse)
[error] 168-169: expected
,but instead found{Remove {
(parse)
[error] 173-174: expected
,but instead found{Remove {
(parse)
| } | ||
| { | ||
| label: "Manage plans", | ||
| autogenerate: {directory: "billing/mange-plans"}, |
There was a problem hiding this comment.
Fix typo in directory path.
There's a typo in the directory path: "mange-plans" should be "manage-plans".
- autogenerate: {directory: "billing/mange-plans"},
+ autogenerate: {directory: "billing/manage-plans"},📝 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.
| autogenerate: {directory: "billing/mange-plans"}, | |
| autogenerate: {directory: "billing/manage-plans"}, |
🤖 Prompt for AI Agents
In src/data/sidebarData.ts at line 160, fix the typo in the directory path by
changing "billing/mange-plans" to "billing/manage-plans" to ensure the correct
directory is referenced.
| } | ||
| { | ||
| label: "Get started", | ||
| autogenerate: {directory: "billing/get-started"}, | ||
| collapsed: false | ||
| } | ||
| { | ||
| label: "Manage plans", | ||
| autogenerate: {directory: "billing/mange-plans"}, | ||
| collapsed: false | ||
| } | ||
| { | ||
| label: "Payment management", | ||
| autogenerate: {directory: "billing/payment-management"}, | ||
| collapsed: false | ||
| } | ||
| { | ||
| label: "Pricing", | ||
| autogenerate: {directory: "billing/pricing"}, | ||
| collapsed: false | ||
| } | ||
| { | ||
| label: "Billing user experience", | ||
| autogenerate: {directory: "billing/billing-user-experience"}, | ||
| collapsed: false | ||
| } |
There was a problem hiding this comment.
Fix critical syntax errors - missing commas between objects.
The static analysis tool correctly identified missing commas between objects in the items array, which will cause JavaScript syntax errors and prevent the code from running.
Apply this diff to fix the missing commas:
{
label: "About billing",
autogenerate: {directory: "billing/about-billing"},
collapsed: false
- }
+ },
{
label: "Get started",
autogenerate: {directory: "billing/get-started"},
collapsed: false
- }
+ },
{
label: "Manage plans",
- autogenerate: {directory: "billing/mange-plans"},
+ autogenerate: {directory: "billing/manage-plans"},
collapsed: false
- }
+ },
{
label: "Payment management",
autogenerate: {directory: "billing/payment-management"},
collapsed: false
- }
+ },
{
label: "Pricing",
autogenerate: {directory: "billing/pricing"},
collapsed: false
- }
+ },
{
label: "Billing user experience",
autogenerate: {directory: "billing/billing-user-experience"},
collapsed: false
}📝 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.
| } | |
| { | |
| label: "Get started", | |
| autogenerate: {directory: "billing/get-started"}, | |
| collapsed: false | |
| } | |
| { | |
| label: "Manage plans", | |
| autogenerate: {directory: "billing/mange-plans"}, | |
| collapsed: false | |
| } | |
| { | |
| label: "Payment management", | |
| autogenerate: {directory: "billing/payment-management"}, | |
| collapsed: false | |
| } | |
| { | |
| label: "Pricing", | |
| autogenerate: {directory: "billing/pricing"}, | |
| collapsed: false | |
| } | |
| { | |
| label: "Billing user experience", | |
| autogenerate: {directory: "billing/billing-user-experience"}, | |
| collapsed: false | |
| } | |
| { | |
| label: "About billing", | |
| autogenerate: {directory: "billing/about-billing"}, | |
| collapsed: false | |
| }, | |
| { | |
| label: "Get started", | |
| autogenerate: {directory: "billing/get-started"}, | |
| collapsed: false | |
| }, | |
| { | |
| label: "Manage plans", | |
| autogenerate: {directory: "billing/manage-plans"}, | |
| collapsed: false | |
| }, | |
| { | |
| label: "Payment management", | |
| autogenerate: {directory: "billing/payment-management"}, | |
| collapsed: false | |
| }, | |
| { | |
| label: "Pricing", | |
| autogenerate: {directory: "billing/pricing"}, | |
| collapsed: false | |
| }, | |
| { | |
| label: "Billing user experience", | |
| autogenerate: {directory: "billing/billing-user-experience"}, | |
| collapsed: false | |
| } |
🧰 Tools
🪛 Biome (1.9.4)
[error] 153-154: expected , but instead found {
Remove {
(parse)
[error] 158-159: expected , but instead found {
Remove {
(parse)
[error] 163-164: expected , but instead found {
Remove {
(parse)
[error] 168-169: expected , but instead found {
Remove {
(parse)
[error] 173-174: expected , but instead found {
Remove {
(parse)
🤖 Prompt for AI Agents
In src/data/sidebarData.ts between lines 152 and 177, there are missing commas
between the objects in the array, causing syntax errors. Add a comma after each
closing brace of the objects except the last one to separate them properly and
fix the syntax.
New topic to go with billing
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (3)
src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx (3)
10-12: Standardize terminology and hyphenation
Consider using “multifactor authentication” (one word) and ensure consistent usage of “self-service portal” or “self-serve portal” across your docs.🧰 Tools
🪛 LanguageTool
[misspelling] ~10-~10: This word is normally spelled as one.
Context: ...t details (if you have billing set up), multi-factor auth settings, and team members. A sel...(EN_COMPOUNDS_MULTI_FACTOR)
16-21: Refine instructional steps for clarity
- Replace “e.g.” with “for example” for readability.
- Remove “etc.” from the Organization alias examples or list all options explicitly.
- Rephrase “visible in the interface in the portal” to “visible in the portal UI.”
25-25: Remove extraneous line
Line 25 appears to be a stray number or blank—please delete it.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx
[misspelling] ~10-~10: This word is normally spelled as one.
Context: ...t details (if you have billing set up), multi-factor auth settings, and team members. A sel...
(EN_COMPOUNDS_MULTI_FACTOR)
| ## Give an organization access to the portal | ||
|
|
||
| TBC |
There was a problem hiding this comment.
Remove placeholder content before publishing
The “TBC” marker indicates incomplete content. Either supply the missing steps or remove this section until it’s ready for review.
🤖 Prompt for AI Agents
In src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx at lines
22 to 24, the placeholder text "TBC" indicates incomplete content. Replace the
"TBC" with the actual instructions for giving an organization access to the
portal, or remove this section entirely until the content is ready to be
published.
| --- | ||
| page_id: a2668524-5842-4c68-ab50-30b7e8c3e842 | ||
| title: Enable self-serve portal for orgs | ||
| sidebar: | ||
| order: 7 | ||
| relatedArticles: | ||
| - | ||
| --- |
There was a problem hiding this comment.
Correct frontmatter configuration
The relatedArticles field currently contains an empty list item (- ) and should either reference valid article IDs or be removed. Additionally, verify that the frontmatter includes all required fields (e.g., id or slug, sidebar_label) in a format consistent with other docs.
🤖 Prompt for AI Agents
In src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx lines 1
to 8, the frontmatter has an empty list item under relatedArticles which should
be removed or replaced with valid article IDs. Also, ensure the frontmatter
includes all required fields such as id or slug and sidebar_label, formatted
consistently with other documentation files. Update the frontmatter accordingly
to fix these issues.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (6)
src/content/docs/billing/manage-plans/create-plans.mdx (6)
29-29: Typo in image alt text.
The alt text reads “Add plas window” but should be “Add plan window” to accurately describe the screenshot.Apply this diff:
- +
31-35: Ensure correct MDX list indentation.
The nested<Aside>under step 3 uses two-space indentation, which may not render as a sublist in MDX. Consider indenting with four spaces to maintain proper nesting.
37-38: Add comma after conjunctive adverb.
Insert a comma after “Otherwise” for proper sentence structure:-5. Select the **Group** the plan belongs to (only if you have multiple plan groups). Otherwise the plan is added to the default group. +5. Select the **Group** the plan belongs to (only if you have multiple plan groups). Otherwise, the plan is added to the default group.🧰 Tools
🪛 LanguageTool
[uncategorized] ~38-~38: A comma may be missing after the conjunctive/linking adverb ‘Otherwise’.
Context: ...only if you have multiple plan groups). Otherwise the plan is added to the default group....(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
51-66: Standardize nested list indentation.
The sub-steps under step 1 and 2 use two-space indentation. For consistent MDX rendering, indent nested items by four spaces.
79-79: Use “an” before vowel sounds.
Change “a unmetered feature” to “an unmetered feature”:-6. If you selected a unmetered feature, select **Save**. You’re done. +6. If you selected an unmetered feature, select **Save**. You’re done.🧰 Tools
🪛 LanguageTool
[misspelling] ~79-~79: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...rencing the feature. 6. If you selected a unmetered feature, select Save. You...(EN_A_VS_AN)
97-97: Clarify comma usage before “so”.
Consider adding a comma before “so” and updating casing for consistency:-If you want to make it so an upper limit is limitless, E.g. 1-10, 11-(blank/limitless); use 1-10, 11-1,000,000 (or a very high number). +If you want to make it, so an upper limit is limitless, e.g. 1-10, 11-(blank/limitless); use 1-10, 11-1,000,000 (or a very high number).🧰 Tools
🪛 LanguageTool
[uncategorized] ~97-~97: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...1-20, 21-30, etc. If you want to make it so an upper limit is limitless, E.g. 1-10,...(COMMA_COMPOUND_SENTENCE_2)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/content/docs/billing/manage-plans/create-plans.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/billing/manage-plans/create-plans.mdx
[uncategorized] ~18-~18: Possible missing comma found.
Context: ...eady to create them in Kinde.
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~38-~38: A comma may be missing after the conjunctive/linking adverb ‘Otherwise’.
Context: ...only if you have multiple plan groups). Otherwise the plan is added to the default group....
(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
[misspelling] ~79-~79: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...rencing the feature. 6. If you selected a unmetered feature, select Save. You...
(EN_A_VS_AN)
[uncategorized] ~97-~97: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...1-20, 21-30, etc. If you want to make it so an upper limit is limitless, E.g. 1-10,...
(COMMA_COMPOUND_SENTENCE_2)
🔇 Additional comments (5)
src/content/docs/billing/manage-plans/create-plans.mdx (5)
1-13: Frontmatter formatting is valid.
No issues found in the YAML frontmatter.
15-16: Introduction is clear and concise.
The opening paragraph effectively sets context for plan creation.
17-21: Aside callout provides helpful context.
The note about reusing charges/features is informative.🧰 Tools
🪛 LanguageTool
[uncategorized] ~18-~18: Possible missing comma found.
Remember you can create one charge or feature th...
Context: ...eady to create them in Kinde.(AI_HYDRA_LEO_MISSING_COMMA)
52-53: Verify UI label for existing charges.
The text says “Use existing feature” when adding a charge. Confirm whether the UI actually displays “Use existing charge” or “Use existing feature” to avoid reader confusion.
105-106: Next step link is correct.
The “Next: Step 5 Publish plans” link points to the right location.
| 9. Enter the **Unit measurement** name, e.g. `license`, `MAU` | ||
| 10. If the item is separately chargeable, select a **Pricing model**. | ||
|
|
||
|  |
There was a problem hiding this comment.
Broken image URL.
The URL ends with /publicg, which appears to be a typo and will break the image. It should end with /public:
-
+📝 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.
|  | |
|  |
🤖 Prompt for AI Agents
In src/content/docs/billing/manage-plans/create-plans.mdx at line 88, the image
URL ends with '/publicg', which is a typo causing the image to break. Correct
the URL by changing the ending from '/publicg' to '/public' to fix the broken
image link.
|
Oli - I was not ready for this to be a PR. Thanks for helping though. |
2 participants
I created this PR to see the updates for billing (i.e. drafted billing docs) and create a
buildI could read the billing docs from - to easily review them.Summary by CodeRabbit