powersync-ja · benitav · Jan 8, 2025 · Jan 7, 2025 · Jan 8, 2025 · Jan 8, 2025
diff --git a/client-sdk-references/swift.mdx b/client-sdk-references/swift.mdx
@@ -26,7 +26,7 @@ The PowerSync Swift SDK currently makes use of the [PowerSync Kotlin Multiplatfo
 <Tip>
   **Demo App**
 
-  We recommend the [Supabase Todo List Demo](https://github.com/powersync-ja/powersync-swift/tree/main/Demo) app as a starting point for using the Swift SDK. See the README for details to run it.
+  We recommend the [Supabase To-Do List Demo](https://github.com/powersync-ja/powersync-swift/tree/main/Demo) app as a starting point for using the Swift SDK. See the README for details to run it.
 </Tip>
 
 ### SDK Features
@@ -90,7 +90,7 @@ The beta version of this SDK introduces a Swift-native wrapper around the packag
 * `@MainThread` usage is no longer required and should be removed.
 * Implementing `SuspendTaskWrapper` for database transactions is no longer required and should be removed.
 
-See the [Todo List Demo app](https://github.com/powersync-ja/powersync-swift/tree/main/Demo) as a reference.
+See the [To-Do List Demo app](https://github.com/powersync-ja/powersync-swift/tree/main/Demo) as a reference.
 
 ## Getting Started
 

diff --git a/installation/app-backend-setup.mdx b/installation/app-backend-setup.mdx
@@ -25,4 +25,4 @@ See [Authentication Setup](/installation/authentication-setup) for details.
 
 See our [Example Projects](/resources/demo-apps-example-projects#custom-backend-examples) page for examples of custom backend implementations (e.g. Django, Node.js, etc.)
 
-For Postgres developers, using [Supabase](/integration-guides/supabase-+-powersync) is an easy alternative to a custom backend. Several of our example apps demonstrate how to use [Supabase](https://supabase.com/) as the Postgres backend.
+For Postgres developers, using [Supabase](/integration-guides/supabase-+-powersync) is an easy alternative to a custom backend. Several of our demo apps demonstrate how to use [Supabase](https://supabase.com/) as the Postgres backend.
diff --git a/installation/quickstart-guide.mdx b/installation/quickstart-guide.mdx
@@ -10,7 +10,7 @@ Support for additional platforms is on our [Roadmap](https://roadmap.powersync.c
 </Note>
 
 ### <Icon icon="elephant" iconType="solid" size="24"/> Postgres Developers: Using Supabase? Try Our Guide.
-If you are using [Supabase](https://supabase.com/) as your backend, we provide a [PowerSync\<>Supabase integration guide](/integration-guides/supabase-+-powersync) which includes a tutorial and example app to quickly learn how to use PowerSync with Supabase.
+If you are using [Supabase](https://supabase.com/) as your backend, we provide a [PowerSync\<>Supabase integration guide](/integration-guides/supabase-+-powersync) which includes a tutorial and demo app to quickly learn how to use PowerSync with Supabase.
 
 ## Implementation outline
 

diff --git a/integration-guides/coolify.mdx b/integration-guides/coolify.mdx
@@ -227,7 +227,7 @@ The following Compose file serves as a universal starting point for deploying th
             content: |
             bucket_definitions:
                 user_lists:
-                # Separate bucket per todo list
+                # Separate bucket per To-Do list
                 parameters: select id as list_id from lists where owner_id = request.user_id()
                 data:
                     - select * from lists where id = bucket.list_id

diff --git a/integration-guides/supabase-+-powersync.mdx b/integration-guides/supabase-+-powersync.mdx
@@ -133,7 +133,7 @@ create publication powersync for table public.lists, public.todos;
 ```yaml
 bucket_definitions:
   user_lists:
-    # Separate bucket per todo list
+    # Separate bucket per To-Do list
     parameters: select id as list_id from lists where owner_id = request.user_id()
     data:
       - select * from lists where id = bucket.list_id

diff --git a/integration-guides/supabase-+-powersync/handling-attachments.mdx b/integration-guides/supabase-+-powersync/handling-attachments.mdx
@@ -5,7 +5,7 @@ description: "Examples of syncing attachments between a client app and Supabase
 
 ## <Icon icon="react"iconType="solid" size="24"/> React Native Example
 
-Our React Native [To-Do List example app](https://github.com/powersync-ja/powersync-js/tree/main/demos/react-native-supabase-todolist) showcases how to sync attachments (such as photos) using the [@powersync/attachments](https://www.npmjs.com/package/@powersync/attachments) library, the PowerSync Service, and Supabase.
+Our React Native [To-Do List demo app](https://github.com/powersync-ja/powersync-js/tree/main/demos/react-native-supabase-todolist) showcases how to sync attachments (such as photos) using the [@powersync/attachments](https://www.npmjs.com/package/@powersync/attachments) library, the PowerSync Service, and Supabase.
 
 In this example, we are syncing photos, however other media types, such as PDFs, are also supported.
 
@@ -17,7 +17,7 @@ The library and this example implementation can be used as a reference for imple
 
 ### Configure Storage in Supabase
 
-In this example app, [Supabase Storage](https://supabase.com/docs/guides/storage) is used to store and serve attachments. To configure this for your app, navigate to the **Storage** section of your Supabase project and create a new bucket:
+In this demo app, [Supabase Storage](https://supabase.com/docs/guides/storage) is used to store and serve attachments. To configure this for your app, navigate to the **Storage** section of your Supabase project and create a new bucket:
 
 <Frame>
   <img src="/images/integration-9.png"/>
@@ -35,7 +35,7 @@ Next, link this storage bucket to your app by opening up the **AppConfig.ts** fi
   <img src="/images/integration-11.png"/>
 </Frame>
 
-Lastly, configure a policy for this bucket. In this example app, we will allow all user operations on the media bucket.
+Lastly, configure a policy for this bucket. In this demo app, we will allow all user operations on the media bucket.
 
 Create a new policy for the **media** bucket:
 
@@ -54,7 +54,7 @@ Give the new policy a name, and allow SELECT, INSERT, UPDATE, and DELETE.
 </Frame>
 Proceed to review and save the policy.
 
-This concludes the necessary configuration for handling attachments in the To-Do List example app. When running the app now, a photo can be taken for a to-do list item, and PowerSync will ensure that the photo syncs to Supabase and other devices (if sync rules allow).
+This concludes the necessary configuration for handling attachments in the To-Do List demo app. When running the app now, a photo can be taken for a to-do list item, and PowerSync will ensure that the photo syncs to Supabase and other devices (if sync rules allow).
 
 <img src="/images/integration-15.avif" width="30%"/>
 
@@ -75,7 +75,7 @@ The [@powersync/attachments](https://www.npmjs.com/package/@powersync/attachment
    * Watch for changes and handle CRUD operations on `AttachmentRecord`s.
    * Store attachment data on the user's local storage, using file URIs on the device.
 
-The UI of the example app supports taking photos as follows:
+The UI of the demo app supports taking photos as follows:
 
 * [CameraWidget](https://github.com/powersync-ja/powersync-js/blob/main/demos/react-native-supabase-todolist/library/widgets/CameraWidget.tsx) uses `expo-camera` to allow users to capture a photo.
 * The photo is stored on the user's local storage.
@@ -107,7 +107,7 @@ The following improvements can be considered for this implementation.
 
 ## <Icon icon="flutter"iconType="solid" size="24"/> Flutter Example
 
-Our Flutter [To-Do List example app](https://github.com/powersync-ja/powersync.dart/tree/master/demos/supabase-todolist) showcases how to sync attachments (such as photos) using our [powersync\_attachments\_helper](https://pub.dev/packages/powersync_attachments_helper) package for Flutter.
+Our Flutter [To-Do List demo app](https://github.com/powersync-ja/powersync.dart/tree/master/demos/supabase-todolist) showcases how to sync attachments (such as photos) using our [powersync\_attachments\_helper](https://pub.dev/packages/powersync_attachments_helper) package for Flutter.
 
 ## See Also
 

diff --git a/intro/powersync-overview.mdx b/intro/powersync-overview.mdx
@@ -109,7 +109,7 @@ This applies to self-hosting of the [PowerSync Open Edition](https://www.powersy
   </Card>
 </CardGroup>
 
-## Examples
+## Examples & Tutorials
 
 Explore and learn from example implementations and common use cases with PowerSync.
 
@@ -121,6 +121,10 @@ Explore and learn from example implementations and common use cases with PowerSy
   <Card title="Use Case Examples" icon="gear" href="/usage/use-case-examples">
     Learn how to implement common use cases with PowerSync.
   </Card>
+
+  <Card title="Tutorials" icon="graduation-cap" href="/tutorials/overview">
+    Solve specific problems with our growing collection of tutorials.
+  </Card>
 </CardGroup>
 
 ## Troubleshooting

diff --git a/migration-guides/mongodb-atlas.mdx b/migration-guides/mongodb-atlas.mdx
@@ -1,6 +1,6 @@
 ---
 title: "MongoDB Atlas Migration Guide"
-description: "This page was last updated on 2024-10-16"
+description: "This page was last updated on 2024-12-27"
 ---
 
 ## MongoDB Atlas deprecation
@@ -48,6 +48,8 @@ As you can see, this is not a point-and-click migration, however it does enable
 
 ### Migration steps
 
+<Tip>The blog post [Migrating a MongoDB Atlas Device Sync App to PowerSync](https://www.powersync.com/blog/migrating-a-mongodb-atlas-device-sync-app-to-powersync) can serve as a handy guide through the migration process.</Tip>
+
 1. Connect your database to an instance of the PowerSync Service:
    1. Using PowerSync Cloud (hosted by us): See [Database Connection](/installation/database-connection#mongodb-alpha-specifics)
    2. Using PowerSync Open Edition (self-hosted): Refer to our end-to-end demo app [available here](https://github.com/powersync-ja/self-host-demo/tree/main/demos/nodejs-mongodb)

diff --git a/mint.json b/mint.json
@@ -51,7 +51,7 @@
       "url": "client-sdk-references"
     },
     {
-      "name": "Self Hosting",
+      "name": "Self-Hosting",
       "url": "self-hosting"
     },
     {
@@ -338,7 +338,7 @@
       ]
     },
     {
-      "group": "Self Hosting",
+      "group": "Self-Hosting",
       "pages": [
         "self-hosting/getting-started",
         {
@@ -372,10 +372,14 @@
         }
       ]
     },
+    {
+      "group": "",
+      "pages": ["tutorials/overview"]
+    },
     {
       "group": "Client",
       "pages": [
-        "tutorials/overview",
+        "tutorials/client/overview",
         {
           "group": "Attachments / Files",
           "pages": [
@@ -401,11 +405,7 @@
       ]
     },
     {
-      "group": "Backend",
-      "pages": ["tutorials/backend/overview"]
-    },
-    {
-      "group": "Self Host",
+      "group": "Self-Hosting",
       "pages": [
         "tutorials/self-host/overview",
         "tutorials/self-host/generate-dev-token"
Original file line number	Diff line number	Diff line change
Expand Up		@@ -25,4 +25,4 @@ See [Authentication Setup](/installation/authentication-setup) for details.

		See our [Example Projects](/resources/demo-apps-example-projects#custom-backend-examples) page for examples of custom backend implementations (e.g. Django, Node.js, etc.)

		For Postgres developers, using [Supabase](/integration-guides/supabase-+-powersync) is an easy alternative to a custom backend. Several of our example apps demonstrate how to use [Supabase](https://supabase.com/) as the Postgres backend.
		For Postgres developers, using [Supabase](/integration-guides/supabase-+-powersync) is an easy alternative to a custom backend. Several of our demo apps demonstrate how to use [Supabase](https://supabase.com/) as the Postgres backend.