diff --git a/docs/.vitepress/config.js b/docs/.vitepress/config.js
index 4341c7eb..ae123689 100644
--- a/docs/.vitepress/config.js
+++ b/docs/.vitepress/config.js
@@ -66,6 +66,13 @@ module.exports = {
             { text: "Persistence", link: "/guide/important-concepts/persistence" }
           ]
         },
+        {
+          text: "Recipes",
+          collapsible: true,
+          items: [
+            { text: "Display Save Progress", link: "/guide/recipes/save-progress" }
+          ]
+        },
         {
           text: "Advanced Concepts",
           collapsible: true,
diff --git a/docs/guide/recipes/save-progress.md b/docs/guide/recipes/save-progress.md
new file mode 100644
index 00000000..16f4b617
--- /dev/null
+++ b/docs/guide/recipes/save-progress.md
@@ -0,0 +1,54 @@
+# Display Save Progress
+
+This is a recipe to add a section to each save in the Saves Manager that will describe the amount of progress within that save. This can allow the player to more easily compare the saves to determine which is which. This would be in addition to the game version, last time played, and the name of the save itself, which can already be used for comparing saves without any configuration.
+
+![save progress display](./save-progress.png)
+
+This recipe only requires modifying the `Save.vue` file within your project. You'll notice it has quite a bit going on, but all we need to focus on is adding a new coerced component for the progress display, and adding it to the template.
+
+## Creating the component
+
+Let's start with creating the coerced component. For this recipe we're going to make a couple assumptions about what this display should be. We'll assume the text will be more complex than just displaying a single value. That is, at different stages of the game progress will be indicated by different metrics. We'll also assume it will be a single line of descriptive text - no images or anything else that would justify making a new .vue component. Breaking these assumptions is left as an exercise for the reader. But for now, with those assumptions in mind, we'll write our component (in the `<script>` tag in `Save.vue`) similar to this example:
+
+```ts
+const progressDisplay = computeComponent(
+    computed(() => {
+    	if (someCondition) {
+    		return "Just started";
+    	}
+    	if (someOtherCondition) {
+    		return `Early game; ${formatWhole(someResourceValue)} resource name`;
+    	}
+    	...
+    	return "Unknown progress";
+    })
+);
+```
+
+This code will create a component that will simply render the returned text, and update as required. However, there's one significant complication in writing the code for these conditions and resource values: you're working with a potentially incomplete save data object.
+
+## Working with save data
+
+The save component is passed down a save data object, that works quite a bit differently than how most of your project accesses data. First off, you are typically working with the objects within a layer directly, but you can't here as you want the information from this specific save, not the currently loaded save. Structurally it'll be like the `player` object, where all computed values and non-persistent refs are stripped away, and refs are already unwrapped. However, unlike the `player` object, you don't know for certain any given property is there - saves can be corrupted or incomplete, or come from older versions of the game that simply had the data structured differently. You'll need to account for that appropriately.
+
+For most cases (specifically where new game versions only added new data to the save data object, rather than change the meaning of existing data), you can use the `LayerData` type to get proper typing for a given layer. For example, a type safe check for whether a save has earned a milestone called "nextSectionOfGame" on a layer called "main" would look like this:
+
+```ts
+if ((save.value?.layers?.main as LayerData<typeof main> | undefined)?.nextSectionOfGame.earned ?? false) {
+	return "Next section of game reached";
+}
+```
+
+## Displaying the component
+
+The template is a fairly large one, but fortunately we don't need to care about most of it, which has to deal with the various actions the player can perform. We just want to display a new component when the save is not in editing mode.
+
+Look for the section of the template, near the bottom, that looks like `<div class="details" v-if="save.error == undefined && !isEditing">`. This is where any details about a save should go. Note that there are _two_ divs with this CSS class, and we specifically want the one that's active when isEditing is `false`.
+
+Now just add the code to render the component in a new div:
+
+```html
+<div v-if="progressDisplay"><component :is="progressDisplay" /></div>
+```
+
+And there you have it! Your dev environment should now show the component in all its glory in the saves manager.
diff --git a/docs/guide/recipes/save-progress.png b/docs/guide/recipes/save-progress.png
new file mode 100644
index 00000000..52babc32
Binary files /dev/null and b/docs/guide/recipes/save-progress.png differ
diff --git a/docs/index.md b/docs/index.md
index 42e02bdc..fcb32edd 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -8,7 +8,7 @@ hero:
   actions:
     - theme: brand
       text: Get Started
-      link: /guide/setup
+      link: /guide/getting-started/setup
     - theme: alt
       text: Learn More
       link: /guide/