Category restructure and a splash of color (#1038)

codykerns · web-flow · commit ae280d502368 · 2025-08-04T13:48:23.000-04:00
* mcp

* webhooks

* oauth

* restructure support &amp; guides

* tweaks

* blue links

* fix broken titles

* adjust charts colors

* cleaning up

* fix admonition

* tweaks

* landing

* css
diff --git a/docs/guides/common-architecture.mdx b/docs/guides/common-architecture.mdx
@@ -5,8 +5,6 @@ excerpt: Most common architecture Common setup w/ RC
 hidden: false
 ---
 
-## Entitlements On Your Existing Backend
-
 Integrating RevenueCat with your backend allows you to seamlessly manage subscription purchases and unlock content for users while keeping your existing setup intact. By using RevenueCat’s SDK and webhooks, you can ensure that your backend stays synchronized with user purchases and entitlements, providing a reliable and up-to-date system for managing access to premium content.
 
 ![Entitlement on Backend](/docs_images/guides/entitlement_on_backend_screenshot.png)
diff --git a/docs/guides/environment-strategies.mdx b/docs/guides/environment-strategies.mdx
@@ -1,7 +1,7 @@
 ---
-title: Environment Strategies
+title: App Environment Strategies
 slug: environment-strategies
-excerpt: Recommended Environment Strategies for your use cases.
+excerpt: Strategies for using different environments in your app
 hidden: false
 ---
 
diff --git a/docs/known-store-issues/storekit/ios-18-4-canceled-state-after-successful-purchase.mdx b/docs/known-store-issues/storekit/ios-18-4-canceled-state-after-successful-purchase.mdx
@@ -12,8 +12,6 @@ import content31 from "@site/code_blocks/customers/customer-info_31.js.txt?raw";
 import content32 from "@site/code_blocks/customers/customer-info_32.cs?raw";
 import contentCapacitor from "@site/code_blocks/customers/customer-info_add_listener_capacitor.ts.txt?raw";
 
-# iOS 18.4-18.5 Canceled State After Successful Purchase
-
 ## Resolved
 
 Apple has rolled out a fix for this issue, and it should no longer be present in any version of iOS. We are keeping this page for historical reference.
diff --git a/docs/migrating-to-revenuecat/swiftystorekit.mdx b/docs/migrating-to-revenuecat/swiftystorekit.mdx
@@ -11,8 +11,6 @@ This guide describes how to integrate specific features from SwiftyStoreKit into
 
 If you're app is already live with SwiftyStoreKit, be sure to read the last section on [Migrating active subscriptions](/migrating-to-revenuecat/swiftystorekit#section-migrating-active-subscriptions).
 
----
-
 ## App startup
 
 Apple recommends registering an `SKPaymentTransactionObserver` as soon as the app launches. RevenueCat automatically does this when you configure an instance of _Purchases_.
diff --git a/docs/platform-resources/developer-store-payments.md b/docs/platform-resources/developer-store-payments.md
@@ -1,15 +1,13 @@
 ---
 title: Payments from Stores and Country Availability
 slug: developer-store-payments
-excerpt: How and when do developers receive their payouts?
+excerpt: How and when developers receive their payouts
 hidden: false
 ---
 
-## How do you receive your revenue from purchases?
-
 As RevenueCat is not the payment processor when your customers make a purchase, you will receive the revenue generated from the purchases from the stores themselves. Apple, Google, Amazon, and Stripe will take a percentage of the revenue as payment for their services before sending the remaining portion to your account. Depending on the store and the country where you are based, different rules may be applied to your revenue.
 
-## Instructions on Setting up Your Payment Information
+## Instructions on setting up your payment information
 
 In order to receive these payments from the stores, you will need to provide them with your banking information through their developer portals.
 
diff --git a/docs/projects/connect-a-store.md b/docs/projects/connect-a-store.md
@@ -2,7 +2,7 @@
 title: Connect Apps & Web Providers
 sidebar_label: Connect Apps & Web Providers
 slug: connect-a-store
-excerpt: Connect your project to App Store Connect, Google Play Console, and more
+excerpt: Connect supported apps and web providers to your project
 ---
 
 Once you've created a [project](/projects/overview), you'll need to connect it to the stores and payment providers you want to support and set up [Server Notifications](/platform-resources/server-notifications). After you've connected your app, you can import your products from the stores to start configuring your offerings.
diff --git a/docs/projects/projects-overview.mdx b/docs/projects/projects-overview.mdx
@@ -2,9 +2,10 @@
 title: Projects
 sidebar_label: Overview
 slug: overview
+description: "The top-level entity for RevenueCat"
 ---
 
-A RevenueCat project is the top-level entity for RevenueCat - it's like a container for your apps, products, and entitlements. Once you've created a project and added your apps, you can implement the RevenueCat SDK in your app to start making purchases.
+A RevenueCat project is the top-level entity for RevenueCat - it's like a container for your apps, products, entitlements, and integrations. Once you've created a project and added your apps, you can implement the RevenueCat SDK in your app to start making purchases.
 
 Within a project, you can also configure integrations like [Webhooks](/integrations/webhooks), run [Experiments](/tools/experiments-v1), and create remotely configurable [Paywalls](/tools/paywalls).
 
diff --git a/docs/test-and-launch/debugging/troubleshooting-the-sdks.mdx b/docs/test-and-launch/debugging/troubleshooting-the-sdks.mdx
@@ -9,7 +9,7 @@ Having trouble with our SDKs? This guide covers common issues and solutions. Go
 - [RevenueCat Developer Community](https://community.revenuecat.com) for general inquiries about the SDK and best practices
 - [StackOverflow](https://stackoverflow.com/questions/tagged/revenuecat) for help on specific questions about your code
 
-# All SDKs
+## All SDKs
 
 Make sure that you're using the latest version of the SDK for your platform, and have installed the SDK according to our [Installation](/getting-started/installation) guides.
 
@@ -29,9 +29,9 @@ You can find the latest version of our SDKs here:
 - [Roku](https://github.com/RevenueCat/purchases-roku)
 - [Ionic Native](https://ionicframework.com/docs/native/purchases)
 
-# Issues when compiling or archiving
+## Issues when compiling or archiving
 
-## iOS
+### iOS
 
 1. **Clean derived data:** in Xcode, go to Product -> Clean Build Data.
 2. **Make sure Swift support is enabled in the project:** check that Swift Language Version is defined as at least "Swift 5" in Build Settings for your target.
@@ -40,12 +40,12 @@ You can find the latest version of our SDKs here:
 4. **Check the Swift version:** Check that the value for [`SWIFT_VERSION` isn't overridden by the `Podfile`, if you have one.](https://github.com/RevenueCat/purchases-flutter/issues/168#issuecomment-796468415).
 5. **Enable Swift support:** If you're getting errors when compiling Swift files after this, try adding a single, empty Swift file to the project.
 
-### If you're using SPM:
+#### If you're using SPM:
 
 1. If you're using the `RevenueCat` Package from a framework and get `(fatal) module 'RevenueCat' not found`, disable [Clang's Module Verifier](https://developer.apple.com/documentation/xcode/identifying-and-addressing-framework-module-issues#Enable-the-module-verifier-build-setting) (`ENABLE_MODULE_VERIFIER`) from build settings. That does not work correctly with SPM as of Xcode 14.3 and 15.0 (this has been reported to Apple as Feedback `FB13048691`):
    ![](/docs_images/test/disable-module-verifier.png)
 
-### If you're using CocoaPods:
+#### If you're using CocoaPods:
 
 1. **Make sure you're using the latest version of CocoaPods.** You can see your version by running `pod --version`, and find the [latest version here](https://github.com/CocoaPods/CocoaPods/releases/latest).
 2. **Re-install pods:** run `pod deintegrate` and then `pod install`, then try running / archiving the project again.
@@ -55,20 +55,20 @@ You can find the latest version of our SDKs here:
 5. **Enable Swift support:** If you're getting errors when compiling Swift files after this, try adding a single, empty Swift file to the project.
 6. **If that _still_ doesn't work**, then make sure that Swift is added to your Library Search Paths. Go to Build Settings, then look for Library Search Paths, and add `$(SDKROOT)/usr/lib/swift` as the **first** item on the list if it's not present.
 
-### If you're using Carthage:
+#### If you're using Carthage:
 
 1. Make sure you're using the latest version of Carthage.
 2. If you're using XCFrameworks with Carthage, make sure you [follow our installation guide](/getting-started/installation/ios#carthage-with-xcframeworks).
 
-## Flutter
+### Flutter
 
 1. Upgrade to the latest version of [purchases-flutter](https://github.com/revenuecat/purchases-flutter/releases/latest)
 2. Upgrade to the [latest version of Flutter](https://flutter.dev/docs/development/tools/sdk/upgrading)
 3. Run `pub cache clean`
 4. Follow the [troubleshooting steps for iOS](/test-and-launch/debugging/troubleshooting-the-sdks#ios).
 5. [Check that Flutter doesn't override the minimum deployment version on iOS](https://github.com/RevenueCat/purchases-flutter/issues/189#issuecomment-824189586)
 
-## React-Native
+### React-Native
 
 1. Upgrade to the latest version of [react-native-purchases](https://github.com/revenuecat/react-native-purchases/releases/latest)
 2. Upgrade to the [latest version of React-Native](https://reactnative.dev/docs/upgrading).
@@ -87,7 +87,7 @@ import ts1 from "@site/code_blocks/test-and-launch/debugging/troubleshooting-the
 
 4. Follow the [troubleshooting steps for iOS](/test-and-launch/debugging/troubleshooting-the-sdks#ios).
 
-# Common Issues
+## Common Issues
 
 - [Products are empty](https://community.revenuecat.com/sdks-51/why-are-offerings-or-products-empty-124)
 - [Active entitlements are empty with an active subscription](https://community.revenuecat.com/dashboard-tools-52/why-are-active-entitlements-empty-with-an-active-subscription-125)
diff --git a/docs/test-and-launch/errors.mdx b/docs/test-and-launch/errors.mdx
@@ -5,8 +5,9 @@ excerpt: Handling errors in Purchases SDK
 hidden: false
 ---
 
-> **Success**
-> This section assumes you've followed our [Quickstart](/getting-started/quickstart) section of our Getting Started guide to install and configure our SDK.
+:::success
+This section assumes you've followed our [Quickstart](/getting-started/quickstart) section of our Getting Started guide to install and configure our SDK.
+:::
 
 ## Error Handling
 
diff --git a/docs/test-and-launch/launch-checklist.mdx b/docs/test-and-launch/launch-checklist.mdx
@@ -1,7 +1,8 @@
 ---
 title: App Subscription Launch Checklist
 slug: launch-checklist
-excerpt: Purchases SDK pre-launch checklist
+sidebar_label: Launch Checklist
+excerpt: RevenueCat pre-launch checklist
 hidden: false
 ---
 
@@ -81,15 +82,15 @@ This document contains a checklist of things to consider before launching subscr
 | ------------------------------------------------------------------------------------------------------------------------------ | --- | ------- |
 | If you're using an attribution integration, ensure your app complies with IDFA usage guidelines by disclosing the use of IDFA. | ✅  | ❌      |
 
-> :warning: **First release on App Store?**
->
-> If the app has never been released on the App Store, it must be released before in-app purchases will work in production (even if you download with a code).
->
-> We recommend releasing and waiting up to 24 hours to ensure purchases work before starting marketing/release campaigns.
+### First release on App Store?
 
-> RevenueCat detects when you launch based on the purchases we receive, so there's nothing you need to do in RevenueCat when you're ready to ship.
+If the app has never been released on the App Store, it must be released before in-app purchases will work in production (even if you download with a code).
 
-# Next steps
+We recommend releasing and waiting up to 24 hours to ensure purchases work before starting marketing/release campaigns.
+
+RevenueCat detects when you launch based on the purchases we receive, so there's nothing you need to do in RevenueCat when you're ready to ship.
+
+## Next steps
 
 - Profit! However, if your app gets rejected, don't panic - check out our post on [getting through App Store review →](https://medium.com/revenuecat-blog/getting-through-app-review-39ac50438c62)
 - Subscribe to [Changelog](https://community.revenuecat.com/product-updates) to stay up to date with new SDK releases
diff --git a/docs/tools/experiments-v1.md b/docs/tools/experiments-v1.md
@@ -8,7 +8,7 @@ hidden: false
 
 RevenueCat Experiments allow you to optimize your subscription pricing and paywall design with easy-to-deploy A/B tests backed by comprehensive cross-platform results. With Experiments, you can A/B test two different Offerings for any paywall location in your app and analyzing the full subscription lifecycle to understand which variant is producing more value for your business.
 
-:::tip
+:::success
 Experiments is available to Pro & Enterprise customers. [Learn more about pricing here](https://www.revenuecat.com/pricing/).
 :::
 
diff --git a/docs/web/web-billing/lifecycle-emails.mdx b/docs/web/web-billing/lifecycle-emails.mdx
@@ -9,8 +9,6 @@ hidden: false
 Beginning July 1, 2025, new rules apply for customers in California related to auto-renewing subscriptions, including wording changes at the time of purchase and renewal notification emails for subscriptions. RevenueCat has implemented new lifecycle emails to comply with the updated rules: [see below](#optional-lifecycle-emails-for-auto-renewing-subscriptions).
 :::
 
-# Lifecycle emails
-
 Customers purchasing through Web Billing (formerly RevenueCat Billing) will receive emails related to their subscriptions and other purchases on the web.
 
 Emails sent to customers:
@@ -19,15 +17,15 @@ Emails sent to customers:
 - Display your **app name** as the sender (configured in Web Billing settings)
 - Use your **support email address** as the _reply-to_ (configured in the Web Billing app settings, if set) or `noreply@revenuecat.com` by default”
 
-## Email customization
+### Email customization
 
 Lifecycle emails are lightly customized according to your brand colors configured in the RevenueCat dashboard (see [Customization](/web/web-billing/customization)).
 
 Only the `Page background` and `Primary button` colors are used to brand emails. Text colors are automatically determined, based on contrast with the background.
 
 ![](/docs_images/web/web-billing/customization_in_emails.png)
 
-## \[optional\] Lifecycle emails for auto-renewing subscriptions
+### \[optional\] Lifecycle emails for auto-renewing subscriptions
 
 Two lifecycle emails can be enabled to comply with the latest (as of July 1st, 2025) California requirements for auto-renewing subscriptions. These emails can be enabled in: the **Billing** tab of your Web Billing configuration:
 
@@ -37,7 +35,7 @@ Two lifecycle emails can be enabled to comply with the latest (as of July 1st, 2
 
 Read more: [Legal ruling](https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=BPC&division=7.&title=&part=3.&chapter=1.&article=9.), [explanation](https://www.arnoldporter.com/en/perspectives/advisories/2025/01/new-california-requirements-for-subscriptions-in-2025)
 
-## All emails, triggers, and calls to action
+### All emails, triggers, and calls to action
 
 You can find a complete list of customer emails below, in addition to the triggers that are used to send them.
 
diff --git a/docs/web/web-billing/overview.mdx b/docs/web/web-billing/overview.mdx
@@ -1,5 +1,5 @@
 ---
-title: RC Web overview
+title: RevenueCat Web Overview
 slug: overview
 excerpt: Overview of RevenueCat's support for web purchases
 hidden: false
diff --git a/docs/welcome/overview.mdx b/docs/welcome/overview.mdx
@@ -11,7 +11,7 @@ With dynamic [paywalls](/tools/paywalls), actionable [analytics](/dashboard-and-
 
 Get started with RevenueCat by [creating an account](https://app.revenuecat.com/signup). All you need is an email address.
 
-:::info See it in action
+:::info
 We host live office hours every other Friday, where we demo the platform and answer your questions live. [Register for the next office hours →](https://app.livestorm.co/revenuecat/live-revenuecat-demo?type=detailed)
 :::
 
@@ -41,6 +41,14 @@ Check out our features, guides, and best practices for implementing different mo
   iconColor="var(--rc-blue-primary)"
 />
 
+<FeatureItem
+  title="App Launch Checklist"
+  subtitle="Ensure your app is ready to launch with our pre-launch checklist"
+  link="/docs/test-and-launch/launch-checklist"
+  iconName="open-external"
+  iconColor="var(--rc-violet-primary)"
+/>
+
 ### Features
 
 <FeatureItem
@@ -72,7 +80,7 @@ Check out our features, guides, and best practices for implementing different mo
   subtitle="Get insights into your business with charts, metrics, and data exports."
   link="/docs/dashboard-and-metrics/overview"
   iconName="chart-bar"
-  iconColor="var(--rc-green-primary)"
+  iconColor="var(--rc-froggy-primary)"
 />
 
 <FeatureItem
diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -101,7 +101,7 @@ const config = {
           },
         ],
         theme: {
-          primaryColor: "#f25a5a",
+          primaryColor: "#576cdb",
         },
         config: "redocly.yaml",
       },
@@ -183,13 +183,14 @@ const config = {
                 sidebarId: "dataSidebar",
                 label: "Charts, Metrics, & Data Reference",
               },
-              {
-                type: "docSidebar",
-                sidebarId: "playbookSidebar",
-                label: "Playbooks & Guides",
-              },
             ],
           },
+          {
+            label: "Guides",
+            type: "docSidebar",
+            sidebarId: "playbookSidebar",
+            position: "left",
+          },
           {
             label: "REST API",
             to: "/api-v1/",
@@ -205,13 +206,9 @@ const config = {
             ],
           },
           {
-            label: "Blog",
-            to: "https://www.revenuecat.com/blog/",
-            position: "left",
-          },
-          {
-            label: "Get Help",
-            to: "/revenuecat-support/support-first-steps",
+            label: "Support",
+            type: "docSidebar",
+            sidebarId: "supportSidebar",
             position: "left",
           },
           {
diff --git a/sidebars.ts b/sidebars.ts
diff --git a/src/css/custom.css b/src/css/custom.css
diff --git a/src/pages/index.js b/src/pages/index.js
diff --git a/src/sidebars/sidebar-utils.ts b/src/sidebars/sidebar-utils.ts
diff --git a/src/theme/Admonition.tsx b/src/theme/Admonition.tsx
