Start Documenting Roblox's Standard Scripts

content/common/navigation/engine/guides.yaml

@@ -582,6 +582,16 @@ navigation:
         path: /cloud-services/extended-services
       - title: Cross-server communication
         path: /cloud-services/cross-server-messaging
+  - title: Roblox Standard Scripts
+    section:
+      - title: Overview
+        path: /roblox-scripts
+      - title: PlayerModule
+        section:
+        - title: Overview
+          path: /roblox-scripts/PlayerModule
+        - title: CameraModule
+          path: /roblox-scripts/PlayerModule/CameraModule
   - title: Roblox for Unity developers
     path: /unity
   - title: Roblox for Unreal developers

content/en-us/roblox-scripts/PlayerModule/CameraModule.md

@@ -0,0 +1,21 @@
+---
+title: CameraModule
+description: Overview about the CameraModule
+---
+
+This ModuleScript implements a singleton class to manage the selection, activation, and deactivation of the current camera controller, character occlusion controller, and transparency controller.
+This script binds to RenderStepped at Camera priority and calls the Update() methods on the active controller instances.
+
+The camera controller ModuleScripts implement classes which are instantiated and activated as-needed,
+they are no longer all instantiated up front as they were in the previous generation of PlayerScripts.
+
+
+## cameraRenderUpdate
+
+``cameraRenderUpdate`` is the RenderStep name used and bound with by the ``CameraModule``
+with the priority ``Enum.RenderPriority.Camera.Value``, through Class.RunService:BindToRenderStep()|:BindToRenderStep().
+
+For custom camera or other behavior, it is recommended to keep the priority in mind. The MicroProfiler can be used to debug which render steps are running in which order.
+
+The order is important. For instance, if the ``CameraModule`` changes the ``Datatype.CFrame`` of the camera,
+you want to ensure that anything that's meant to change the ``Datatype.CFrame`` again runs first, before reading the ``Datatype.CFrame``, if you're expecting a different your custom modified values.

content/en-us/roblox-scripts/PlayerModule/index.md

@@ -0,0 +1,14 @@
+---
+title: Standard PlayerModule
+description: Overview of the PlayerModule.
+---
+
+The ``PlayerModule`` is initialized by ``PlayerScriptsLoader``.
+``PlayerScriptsLoader`` is a script which requires and instantiates the ``PlayerModule`` singleton.
+
+``PlayerModule`` comes with two further modules, ``CameraModule`` and ``ControlModule``.
+
+
+## PlayerModule
+
+This module requires and instantiates the camera and control modules, and provides getters for developers to access methods on these singletons without having to modify Roblox-supplied scripts.

content/en-us/roblox-scripts/index.md

@@ -0,0 +1,13 @@
+---
+title: Roblox Standard Scripts
+description: Overview of Roblox Standard Scripts
+---
+
+By default, Roblox creates default scripts that provide behavior for things such as the Camera and Character Controls.
+
+<figure>
+<img src="../assets/roblox-scripts/starterplayerscripts.png" width="200" alt="Showcase of some standard Roblox Scripts." />
+</figure>
+
+
+By starting a playtest <kbd>F5</kbd>, you can find the inserted scripts and copy them through the Explorer, and then stop the playtest and paste the scripts in, in order to optionally modify them, if preferred.