diff --git a/src/_data/sidenav.yml b/src/_data/sidenav.yml
index 8b6c9a6809..2e56aa058c 100644
--- a/src/_data/sidenav.yml
+++ b/src/_data/sidenav.yml
@@ -155,10 +155,17 @@
           permalink: /development/platform-integration/c-interop
         - title: Hosting native Android and iOS views
           permalink: /development/platform-integration/platform-views
-        - title: Web FAQ
-          permalink: /development/platform-integration/web
         - title: Writing platform-specific code
           permalink: /development/platform-integration/platform-channels
+        - title: Web
+          permalink: /development/platform-integration/web
+          children:
+            - title: Web FAQ
+              permalink: /development/platform-integration/web/faq
+            - title: Web renderers
+              permalink: /development/platform-integration/web/renderers
+            - title: Custom app initialization
+              permalink: /development/platform-integration/web/initialization
         - title: Desktop
           permalink: /desktop
     - title: Packages & plugins
@@ -274,8 +281,6 @@
           permalink: /development/tools/flutter-fix
         - title: Code formatting
           permalink: /development/tools/formatting
-        - title: Web renderers
-          permalink: /development/tools/web-renderers
     - title: Migration notes
       permalink: /development/androidx-migration
       children:
diff --git a/src/development/platform-integration/web.md b/src/development/platform-integration/web/faq.md
similarity index 98%
rename from src/development/platform-integration/web.md
rename to src/development/platform-integration/web/faq.md
index 1937081586..b44aac6a2f 100644
--- a/src/development/platform-integration/web.md
+++ b/src/development/platform-integration/web/faq.md
@@ -66,7 +66,7 @@ are supported as the default browsers for debugging your app.
 ### Can I build, run, and deploy web apps in any of the IDEs?
 
 You can select **Chrome** or **Edge** as the target device in
-Android Studio/IntelliJ and VS Code. 
+Android Studio/IntelliJ and VS Code.
 
 The device pulldown should now include the **Chrome (web)**
 option for all channels.
@@ -77,7 +77,7 @@ See [Creating responsive apps][].
 
 ### Can I use Flutter plugins?
 
-Yes, several plugins have web support. 
+Yes, several plugins have web support.
 Find an updated list of plugins on [pub.dev][] using the web filter.
 You can also add web support to existing plugins or
 [write your own plugins][] for the web.
diff --git a/src/development/platform-integration/web/index.md b/src/development/platform-integration/web/index.md
new file mode 100644
index 0000000000..4a5aa9fa81
--- /dev/null
+++ b/src/development/platform-integration/web/index.md
@@ -0,0 +1,4 @@
+---
+title: Web
+layout: toc
+---
diff --git a/src/development/platform-integration/web/initialization.md b/src/development/platform-integration/web/initialization.md
new file mode 100644
index 0000000000..ea9e887628
--- /dev/null
+++ b/src/development/platform-integration/web/initialization.md
@@ -0,0 +1,179 @@
+---
+title: Customizing web app initialization
+description: Customize how Flutter apps are initialized on the web
+---
+
+You can customize how a Flutter app is initialized on the web
+using the `_flutter.loader` JavaScript API.
+This API can be used to display a loading indicator in CSS,
+prevent the app from loading based on a condition,
+or wait until the user presses a button before showing the app.
+
+The initialization process is split into the following stages:
+
+**Loading the entrypoint script**
+:  Fetches the `main.dart.js` script and initializes the service worker.
+**Initializing the Flutter engine**
+: Initializes Flutter's web engine by downloading required resources
+  such as assets, fonts, and CanvasKit.
+**Running the app**
+:  Prepares the DOM for your Flutter app and runs it.
+
+This page shows how to customize the behavior
+at each stage of the initialization process.
+
+## Getting started
+
+By default, the `index.html` file
+generated by the `flutter create` command
+contains a script tag
+that calls `loadEntrypoint` from the `flutter.js` file:
+
+```html
+<html>
+   <head>
+      <!-- ... -->
+      <script src="flutter.js" defer></script>
+   </head>
+   <body>
+      <script>
+         window.addEventListener('load', function (ev) {
+             // Download main.dart.js
+             _flutter.loader.loadEntrypoint({
+                 serviceWorker: {
+                     serviceWorkerVersion: serviceWorkerVersion,
+                 }
+             }).then(function (engineInitializer) {
+                 // Initialize the Flutter engine
+                 return engineInitializer.initializeEngine();
+             }).then(function (appRunner) {
+                 // Run the app
+                 return appRunner.runApp();
+             });
+         });
+      </script>
+   </body>
+</html>
+```
+
+
+
+{{site.alert.note}}
+  In Flutter 2.10 or earlier,
+  this script doesn't support customization.
+  To upgrade your `index.html` file to the latest version,
+  see [Upgrading an older project](#upgrading-an-older-project).
+{{site.alert.end}}
+
+
+
+The `loadEntrypoint` function returns a JavaScript [`Promise`][js-promise]
+that resolves when the Service Worker is initialized
+and the `main.dart.js` entrypoint has been downloaded by the browser.
+It resolves with an **engine initializer** object
+that initializes the Flutter Web engine.
+
+The `initializeEngine()` function returns a promise
+that resolves with an **app runner** object
+that has a single method `runApp()` that runs the Flutter app.
+
+[js-promise]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise
+
+## Customizing web app initialization
+
+In this section,
+learn how to customize each stage of your app’s initialization.
+
+### Loading the entrypoint
+
+The `loadEntrypoint` method accepts these parameters:
+
+`entrypointUrl`
+: The URL of your Flutter app's entrypoint. Defaults to `main.dart.js`.
+
+`serviceWorker`
+: The configuration of the `flutter_service_worker.js` file.
+  If this isn’t set, the service worker won’t be used.
+      
+`serviceWorkerVersion`
+: Pass *the `serviceWorkerVersion` var* set by
+  the build process in your <strong><code>index.html</code></strong> file.
+  
+`timeoutMillis`
+: The timeout value for the service worker load.
+  Defaults to <strong><code>4000ms</code></strong>.
+
+
+### Initializing the engine
+
+Instead of calling `initializeEngine()` on the engine initializer,
+you can call `autoStart()` to immediately start the app
+with the default configuration
+instead of using the app runner to call `runApp()`:
+
+
+```js
+_flutter.loader.loadEntrypoint({
+  serviceWorker: {
+    serviceWorkerVersion: serviceWorkerVersion,
+  }
+}).then(function(engineInitializer) {
+  return engineInitializer.autoStart();
+});
+```
+
+## Example: Display a progress indicator
+
+To give the user of your application feedback
+during the initialization process,
+use the hooks provided for each stage to update the DOM:
+
+
+```html
+<html>
+   <head>
+      <!-- ... -->
+      <script src="flutter.js" defer></script>
+   </head>
+   <body>
+      <div id="loading"></div>
+      <script>
+         window.addEventListener('load', function(ev) {
+           var loading = document.querySelector('#loading');
+           loading.textContent = "Loading entrypoint...";
+           _flutter.loader.loadEntrypoint({
+             serviceWorker: {
+               serviceWorkerVersion: serviceWorkerVersion,
+             }
+           }).then(function(engineInitializer) {
+             loading.textContent = "Initializing engine...";
+             return engineInitializer.initializeEngine();
+           }).then(function(appRunner) {
+             loading.textContent = "Running app...";
+             return appRunner.runApp();
+           });
+         });
+      </script>
+   </body>
+</html>
+```
+
+
+For a more practical example using CSS animations,
+see the [initialization code][gallery-init] for the Flutter Gallery.
+
+[gallery-init]: {{site.github}}/flutter/gallery/blob/master/web/index.html
+
+## Upgrading an older project
+
+If your project was created in Flutter 2.10 or earlier,
+you can create a new `index.html` file
+with the latest initialization template by running `flutter create`.
+
+From your project directory, run the following:
+
+```
+$ flutter create .
+```
+
+You can now customize the startup process as described above.
diff --git a/src/development/tools/web-renderers.md b/src/development/platform-integration/web/renderers.md
similarity index 91%
rename from src/development/tools/web-renderers.md
rename to src/development/platform-integration/web/renderers.md
index 18aa36435b..52109d8e99 100644
--- a/src/development/tools/web-renderers.md
+++ b/src/development/platform-integration/web/renderers.md
@@ -8,12 +8,12 @@ renderers. This page describes both renderers and how to choose the best one for
 your needs. The two renderers are:
 
 **HTML renderer**
-  : Uses a combination of HTML elements, CSS, Canvas elements, and SVG elements.
+: Uses a combination of HTML elements, CSS, Canvas elements, and SVG elements.
   This renderer has a smaller download size.
 
 **CanvasKit renderer**
-  : This renderer is fully consistent with Flutter mobile and desktop, has
-  faster performance with higher widget density, but adds about 2MB in 
+: This renderer is fully consistent with Flutter mobile and desktop, has
+  faster performance with higher widget density, but adds about 2MB in
   download size.
 
 ## Command line options
@@ -24,8 +24,8 @@ The `--web-renderer` command line option takes one of three values, `auto`,
 * `auto` (default) - automatically chooses which renderer to use. This option
   chooses the HTML renderer when the app is running in a mobile browser, and
   CanvasKit renderer when the app is running in a desktop browser.
-* `html` - always use the HTML renderer. 
-* `canvaskit` - always use the CanvasKit renderer. 
+* `html` - always use the HTML renderer
+* `canvaskit` - always use the CanvasKit renderer
 
 This flag can be used with the `run` or `build` subcommands. For example:
 
@@ -68,7 +68,7 @@ mobile browsers and optimizing for performance on desktop browsers.
 
 Choose the `html` option if you are optimizing download size over performance on
 both desktop and mobile browsers.
-  
+
 Choose the `canvaskit` option if you are prioritizing performance and
 pixel-perfect consistency on both desktop and mobile browsers.