Cool file names on code blocks

docs/src/content/docs/guides/details.md

@@ -49,7 +49,7 @@ If for whatever reason you want to set up a Unity project manually instead of us
 1. Start up a Unity 2019.4.39f1 project
 2. In the "Assets" folder in Unity, create a new folder called "Editor". In it create a file called "CreateAssetBundle.cs" with the following code in it:
 
-```cs
+```cs title="Editor/CreateAssetBundle.cs"
 using UnityEditor;
 using UnityEngine;
 using System.IO;

docs/src/content/docs/guides/dialogue.md

@@ -31,7 +31,7 @@ A remote trigger is used to have an NPC talk to you from a distance; ex: Slate s
 
 Here's an example dialogue XML:
 
-```xml
+```xml title="ExampleDialogue.xml"
 <!-- Example Dialogue -->
 <!-- All files must have `DialogueTree` as the root element, the xmlns:xsi=... and xsi:noNamespaceSchemaLocation=... is optional but provides improved error checking if your editor supports it -->
 <DialogueTree xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

docs/src/content/docs/guides/extending-configs.md

@@ -9,7 +9,7 @@ This guide will explain how to use the API to add new features to New Horizons.
 
 Addon developers will add a key to the `extras` object in the root of the config
 
-```json
+```json title="wetrock.json"
 {
     "name": "Wetrock",
     "extras": {

docs/src/content/docs/guides/planet-generation.md

@@ -17,7 +17,7 @@ Here's an example heightmap of earth from the Real Solar System addon.
 
 ![Earth's Heightmap](@/assets/docs-images/planet_gen/earth_heightmap.webp)
 
-```json
+```json title="cool_planet.json"
 {
     "name": "My Cool Planet",
     "HeightMap": {
@@ -44,7 +44,7 @@ The following modules support variable sizing, meaning they can change scale ove
 
 To do this, simply specify a `curve` property on the module
 
-```json
+```json title="cool_water_planet.json"
 {
     "name": "My Cool Planet",
     "Water": {
@@ -69,7 +69,7 @@ This makes the water on this planet shrink over the course of 22 minutes.
 In order to create a quantum planet, first create a normal planet. Then, create a second planet config with the same `name` as the first and `isQuantumState` set to `true`.
 This makes the second planet a quantum state of the first, anything you specify here will only apply when the planet is in this state.
 
-```json
+```json title="cool_planet_sun_state.json"
 {
     "name": "MyPlanet",
     "Orbit": {
@@ -79,7 +79,7 @@ This makes the second planet a quantum state of the first, anything you specify
 }
 ```
 
-```json
+```json title="cool_planet_th_state.json"
 {
     "name": "MyPlanet",
     "isQuantumState": true,
@@ -94,7 +94,7 @@ This makes the second planet a quantum state of the first, anything you specify
 
 To create a binary system of planets (like ash twin and ember twin), first create a config with `FocalPoint` set
 
-```json
+```json title="center.json"
 {
     "name": "My Focal Point",
     "Orbit": {
@@ -110,7 +110,7 @@ To create a binary system of planets (like ash twin and ember twin), first creat
 
 Now in each config set the `primaryBody` to the focal point
 
-```json
+```json title="a.json"
 {
     "name": "Planet A",
     "Orbit": {
@@ -122,7 +122,7 @@ Now in each config set the `primaryBody` to the focal point
 }
 ```
 
-```json
+```json title="b.json"
 {
     "name": "Planet B",
     "Orbit": {

docs/src/content/docs/guides/ship-log.md

@@ -53,7 +53,7 @@ navigate to ShipLogManager.
 
 ### Example File
 
-```xml
+```xml title="ExampleShipLog.xml"
 <!-- Example File -->
 <!-- All files must have "AstroObjectEntry" as their root element, the xmlns:xsi=... and xsi:noNamespaceSchemaLocation=... is optional but heavily encouraged to reduce errors -->
 <AstroObjectEntry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

docs/src/content/docs/guides/star-systems.md

@@ -13,7 +13,7 @@ The name of your star system config must be the same as the unique id used in th
 
 A star system config file will look something like this:
 
-```json
+```json title="my_star_system.json"
 {
     "$schema": "https://raw.githubusercontent.com/Outer-Wilds-New-Horizons/new-horizons/main/NewHorizons/Schemas/star_system_schema.json",
     "travelAudio": "assets/Travel.mp3",

docs/src/content/docs/guides/translation.md

@@ -11,7 +11,7 @@ In this folder you can put json files with the name of the language you want to
 
 Here's an example, for `russian.json`:
 
-```json
+```json title="russian.json"
 {
     "$schema": "https://raw.githubusercontent.com/Outer-Wilds-New-Horizons/new-horizons/main/NewHorizons/Schemas/translation_schema.json",
     "DialogueDictionary": {

docs/src/content/docs/guides/updating-planets.md

@@ -9,7 +9,7 @@ Only some of the above modules are supported (currently) for existing planets. T
 
 You can also delete parts of an existing planet. Here's part of an example config which would delete the rising sand from Ember Twin:
 
-```json
+```json title="ember_twin.json"
 {
     "name": "Ember Twin",
     "removeChildren": ["SandSphere_Rising"]
@@ -22,7 +22,7 @@ In `childrenToDestroy` you list the relative paths for the children of the plane
 
 You do this (but with the appropriate name) as its own config.
 
-```json
+```json title="ember_twin.json"
 {
     "name": "Ember Twin",
     "destroy": true

docs/src/content/docs/start-here/getting-started.md

@@ -30,7 +30,7 @@ To get started, create a new file in this folder called `wetrock.json`, we'll ex
 Open this file in VSCode (you can do so by right-clicking the file and clicking "Open with Code")
 Once in VSCode, paste this code into the file:
 
-```json
+```json title="wetrock.json"
 {
     "name": "Wetrock",
     "$schema": "https://raw.githubusercontent.com/xen-42/outer-wilds-new-horizons/main/NewHorizons/Schemas/body_schema.json",