update Open Source Docs from Roblox internal teams

Author: rbx-open-source-docs[bot]

content/common/navigation/avatar/tutorials.yaml

@@ -1,5 +1,5 @@
 backTo:
-  title: Back to Avatar
+  title: Back to avatar
   path: /avatar/
 navigation:
   - heading: Curriculum paths

content/common/navigation/cloud/guides.yaml

@@ -10,7 +10,7 @@ navigation:
     path: /cloud/guides/inventory
   - title: Engine instances
     path: /cloud/guides/instance
-  - title: Experience notifications
+  - title: User notifications
     path: /cloud/guides/experience-notifications
   - title: Messaging
     path: /cloud/guides/usage-messaging

content/common/navigation/engine/reference.yaml

@@ -1288,6 +1288,11 @@ navigation:
         type: engineapi
         source: /reference/engine/classes/ImageLabel.yaml
         ignoreTranslation: true
+      - title: ImportSession
+        path: /reference/engine/classes/ImportSession
+        type: engineapi
+        source: /reference/engine/classes/ImportSession.yaml
+        ignoreTranslation: true
       - title: IncrementalPatchBuilder
         path: /reference/engine/classes/IncrementalPatchBuilder
         type: engineapi
@@ -2238,6 +2243,11 @@ navigation:
         type: engineapi
         source: /reference/engine/classes/SensorBase.yaml
         ignoreTranslation: true
+      - title: SerializationService
+        path: /reference/engine/classes/SerializationService
+        type: engineapi
+        source: /reference/engine/classes/SerializationService.yaml
+        ignoreTranslation: true
       - title: ServerReplicator
         path: /reference/engine/classes/ServerReplicator
         type: engineapi
@@ -2278,11 +2288,6 @@ navigation:
         type: engineapi
         source: /reference/engine/classes/ShirtGraphic.yaml
         ignoreTranslation: true
-      - title: ShorelineUpgraderService
-        path: /reference/engine/classes/ShorelineUpgraderService
-        type: engineapi
-        source: /reference/engine/classes/ShorelineUpgraderService.yaml
-        ignoreTranslation: true
       - title: SkateboardController
         path: /reference/engine/classes/SkateboardController
         type: engineapi
@@ -3301,6 +3306,11 @@ navigation:
         type: engineapi
         source: /reference/engine/enums/AccessoryType.yaml
         ignoreTranslation: true
+      - title: ActionOnAutoResumeSync
+        path: /reference/engine/enums/ActionOnAutoResumeSync
+        type: engineapi
+        source: /reference/engine/enums/ActionOnAutoResumeSync.yaml
+        ignoreTranslation: true
       - title: ActionOnStopSync
         path: /reference/engine/enums/ActionOnStopSync
         type: engineapi

content/common/navigation/engine/studio.yaml

@@ -1,6 +1,6 @@
 defaultType: markdown
 backTo:
-  title: Back to Platform
+  title: Back to platform
   path: /platform
 navigation:
   - heading: Roblox Studio

content/en-us/cloud/guides/experience-notifications.md

@@ -1,55 +1,30 @@
 ---
-title: Experience notifications
-description: Send experience notifications from the web with Open Cloud APIs. Experience notifications are a way for users to keep up with their favorite experiences through timely, personalized notifications.
+title: User notifications
+description: Use Open Cloud to send experience notifications to users. Help players keep up with their favorite experiences through timely, personalized notifications.
 ---
 
 import Intro from '../../includes/experience-notifications/intro.md'
-import Eligibility from '../../includes/experience-notifications/eligibility.md'
-import ImplementationCreateNotificationString from '../../includes/experience-notifications/implementation-create-notification-string.md'
-import DeliverySystem from '../../includes/experience-notifications/delivery-system.md'
-import AnalyticsOverview from '../../includes/experience-notifications/analytics-overview.md'
-import AnalyticsNotificationsSummary from '../../includes/experience-notifications/analytics-notification-summary.md'
-import AnalyticsItemizedStats from '../../includes/experience-notifications/analytics-itemized-stats.md'
-import Guidelines from '../../includes/experience-notifications/guidelines.md'
 
 <Intro components={props.components} />
 
-## Eligibility requirements
+After they receive a notification, users can join the experience directly via the **Join** button and spawn according to your [launch data](#include-launch-and-analytics-data).
 
-<Eligibility components={props.components} />
-
-## Usage guidelines
-
-<Guidelines components={props.components} />
+For more information on features, eligibility requirements, usage guidelines, and the corresponding Engine API, see the [Experiences guide](../../production/promotion/experience-notifications.md).
 
 ## Implementation
 
-Implementing Experience Notifications begins with [creating a notification string](#create-a-notification-string). Once a notification string is set up, you can [send notifications](#send-an-experience-notification) with optional [custom parameters](#customize-notifications-using-parameters).
-
-Alternatively, you can use the [Engine API](../../production/promotion/experience-notifications.md) to trigger notifications through server-side scripts.
-
-### Create a notification string
-
-<ImplementationCreateNotificationString components={props.components} />
-
-### Send an experience notification
-
-The [UserNotification](../../cloud/reference/UserNotification) API lets you send Experience Notifications to users. Before using it, you must [generate an API key](../../cloud/auth/api-keys.md) or [configure OAuth 2.0](../../cloud/auth/oauth2-overview.md) for your app. The examples on this page use API keys.
-
-Notifications will be delivered to [opted-in](https://en.help.roblox.com/hc/en-us/articles/24769602332692-Out-of-Experience-Notifications) users age 13+ through their Roblox notification stream, at which point they can join the experience directly via the **Join** button on the notification and spawn according to your [launch data](#include-launch-and-analytics-data).
+The [UserNotification](/cloud/reference/UserNotification) resource lets you send experience notifications to users. Before using it, you must [generate an API key](../../cloud/auth/api-keys.md) or [configure OAuth 2.0](../../cloud/auth/oauth2-overview.md) for your app. The examples on this page use API keys.
 
-<img src="../../assets/open-cloud/experience-notifications/Notification-Stream.png" width="393" alt="Notifications stream on the Roblox app" />
-
-To send an Experience Notification to a user:
-
-1. Copy the API key to the `x-api-key` request header of the [Create User Notification](../../cloud/reference/UserNotification#Create-User-Notification) call.
-2. In your request:
+To send an experience notification to a user:
 
+1. [Create a notification string](../../production/promotion/experience-notifications.md#create-a-notification-string) in the [Creator Dashboard](https://create.roblox.com/dashboard/creations). This step must be done in the Creator Dashboard; there's no Open Cloud API for it.
+1. Form the request:
+   1. Copy the API key to the `x-api-key` request header.
    1. Copy the notification string asset ID as the value of the `payload.message_id` property.
-   2. Set `payload.type` to `"MOMENT"`.
-   3. Set `source.universe` to be the universe resource URL `"universes/${UniverseID}"`.
+   1. Set `payload.type` to `"MOMENT"`.
+   1. Set `source.universe` to be the universe resource URL `"universes/${UniverseID}"`.
 
-```bash title="Send an Experience Notification"
+```bash title="Send an experience notification"
 curl --location 'https://apis.roblox.com/cloud/v2/users/${UserId}/notifications' \
 --header 'x-api-key: ${ApiKey}' \
 --header 'Content-Type: application/json' \
@@ -75,11 +50,11 @@ Example response which returns the notification ID in the `id` field:
 
 ### Customize notifications using parameters
 
-To customize the notification for each recipient, you can include **parameters** in the [notification string](#create-a-notification-string), then customize the parameters when calling the API. For example, you can define the notification string as:
+To customize the notification for each recipient, include **parameters** in the [notification string](#implementation). Then customize the parameters when calling the API. For example, you can define the notification string as:
 
 <p><Chip label="{userId-friend} beat your high score by {points} points! Time to level up?" size="large" color="primary" variant="outlined" /></p>
 
-Then, set the `userId-friend` and `points` parameters in the script:
+Add the `userId-friend` and `points` parameters in the script:
 
 ```bash title="Customize Notification Using Parameters"
 curl --location 'https://apis.roblox.com/cloud/v2/users/${UserId}/notifications' \
@@ -102,7 +77,7 @@ curl --location 'https://apis.roblox.com/cloud/v2/users/${UserId}/notifications'
 
 ### Include launch and analytics data
 
-To further improve user experience, you can include **launch data** in the notification, useful for scenarios such as routing users to a coordinate location or personalizing the joining experience. Additionally, you can include [analytics](#analytics) data to segment the performance of different categories of notifications.
+To further improve user experience, you can include **launch data** in the notification, useful for scenarios such as routing users to a coordinate location or personalizing the joining experience. Additionally, you can include [analytics](../../production/promotion/experience-notifications.md#analytics) data to segment the performance of different categories of notifications.
 
 ```bash title="Include Launch Data and Analytics Data"
 curl --location 'https://apis.roblox.com/cloud/v2/users/${UserId}/notifications' \
@@ -125,18 +100,8 @@ curl --location 'https://apis.roblox.com/cloud/v2/users/${UserId}/notifications'
 }'
 ```
 
-## Delivery system
-
-<DeliverySystem components={props.components} />
-
-## Analytics
-
-<AnalyticsOverview components={props.components} />
-
-### Notifications summary
-
-<AnalyticsNotificationsSummary components={props.components} />
+## Rate limits and delivery
 
-### Itemized stats
+Each user can receive **one** notification per day from a given experience, and you receive transparent feedback when a user's throttle limit is reached.
 
-<AnalyticsItemizedStats components={props.components} />
+There are many other reasons that a notification might not be delivered. For more information, see [Delivery system](../../production/promotion/experience-notifications.md#delivery-system) in the Engine guide.

content/en-us/creator-fund.md

@@ -9,8 +9,8 @@ With the launch of the Creator Fund, we want new and existing developers to have
 
 <figure>
 <Chip
-    color="success"
-    label="Status: Open"
+    color="error"
+    label="Status: Closed"
     size="medium"
     variant="filled"/>
 </figure>
@@ -28,17 +28,3 @@ We prioritize projects that encompass:
 - In-experience avatars that reflect elements of the user's platform avatar identity. Ability to leverage items that you can equip on platform avatars, like the ones you buy in the [Marketplace](https://www.roblox.com/catalog).
 
 If you are accepted into the program, we partner with you to define key deliverables for your project and provide funding based off of your progress towards these milestones.
-
-## Application requirements
-
-- 18+ age requirement.
-- Details about you and/or your team.
-- Short description of your project.
-- Pitch deck of high-level strategy, design specifications, etc.
-- Project milestone schedule and budget.
-
-If you feel like you and your project are a perfect fit for this program, please submit your application.
-
-<figure>
-<Button size="large" variant="contained" href="https://roblox.qualtrics.com/jfe/form/SV_a4PdqU3StYp6crI">Apply Now</Button>
-</figure>

content/en-us/creator-programs/index.md

@@ -102,8 +102,8 @@ Roblox offers various programs for creators on the platform to provide additiona
     <h4>Creator Fund</h4>
         <figure>
     <Chip
-        color="success"
-        label="Status: Open"
+        color="error"
+        label="Status: Closed"
         size="medium"
         variant="filled"/>
     </figure>

content/en-us/creator-programs/rdc.md

@@ -3,7 +3,7 @@ title: Roblox Developers Conference
 description: RDC is an invite-only, hybrid (in-person and online) event that brings together Roblox developers, brands, and creators worldwide.
 ---
 
-RDC is an invite-only, hybrid (in-person and online) event that brings together Roblox developers, brands, and creators worldwide. There will be networking opportunities, in-depth breakout sessions, product demonstrations, and office hours—all designed to empower your success and showcase the future of Roblox.
+Roblox Developers Conference (RDC) is coming back as a virtual and in-person event to San Jose on September 5-6! RDC is an invite-only event that brings together Roblox developers, brands, and creators worldwide. There will be networking opportunities, in-depth breakout sessions, product demonstrations, and office hours—all designed to empower your success and showcase the future of Roblox.
 
 <figure>
 <Chip

content/en-us/discovery.md

@@ -183,6 +183,6 @@ Roblox is [committed](https://devforum.roblox.com/t/discovery-on-roblox-past-pre
 
 ### Notifications
 
-**Notifications** elevate timely and actionable information to users. Historically, we have focused on building and scaling social notifications, such as friend requests and invitations. This system allows for creators to engage with users directly while they are away. Milestones, high scores, [friend activity](https://devforum.roblox.com/t/user-mentions-in-experience-notifications/2980675), and other key moments can be delivered to users as personalized notifications to the notification stream. For additional information and implementation instructions, see [Experience Notifications](./cloud/guides/experience-notifications.md).
+**Notifications** elevate timely and actionable information to users. Historically, we have focused on building and scaling social notifications, such as friend requests and invitations. This system allows for creators to engage with users directly while they are away. Milestones, high scores, [friend activity](https://devforum.roblox.com/t/user-mentions-in-experience-notifications/2980675), and other key moments can be delivered to users as personalized notifications to the notification stream. For additional information and implementation instructions, see [Experience notifications](./cloud/guides/experience-notifications.md).
 
 You can also use our [in-experience notification permission prompts](https://devforum.roblox.com/t/introducing-in-experience-notification-permission-prompts/2909125) to upsell notification opt-in within experiences. Notifications can help resurrect lapsed users or remind users when they need to take an action.

content/en-us/includes/experience-notifications/delivery-system.md

@@ -4,7 +4,7 @@ title: include
 
 A spam prevention system exists to ensure the quality of notifications for users and protect the shared notification channel for all developers. Because of this, delivery of notifications is not guaranteed. This spam prevention system is directly informed by user engagement: the more users engage with your notifications, the more reach they'll receive. You can transparently track engagement metrics in the [analytics](#analytics) dashboard, as explained below.
 
-Experience Notifications have a static throttle limit where each user can receive one notification per day from a given experience and you'll receive transparent feedback when a user's throttle limit is reached.
+Experience notifications have a static throttle limit; each user can receive one notification per day from a given experience, and you receive transparent feedback when a user's throttle limit is reached.
 
 Additionally, the following list outlines some of the special cases which may result in **non‑delivery** of a notification: