feat: creating library page

Author: DecDuck

astro.config.mjs

@@ -2,13 +2,18 @@
 import { defineConfig } from "astro/config";
 import starlight from "@astrojs/starlight";
 import starlightThemeRapide from "starlight-theme-rapide";
-import starlightLinksValidator from 'starlight-links-validator'
+import starlightLinksValidator from "starlight-links-validator";
+import starlightImageZoom from "starlight-image-zoom";
 
 // https://astro.build/config
 export default defineConfig({
   integrations: [
     starlight({
-      plugins: [starlightThemeRapide(), starlightLinksValidator()],
+      plugins: [
+        starlightThemeRapide(),
+        starlightLinksValidator(),
+        starlightImageZoom(),
+      ],
       title: "Drop OSS",
       social: [
         {

package.json

@@ -13,6 +13,7 @@
     "@astrojs/starlight": "^0.37.4",
     "astro": "^5.6.1",
     "sharp": "^0.34.2",
+    "starlight-image-zoom": "^0.13.2",
     "starlight-links-validator": "^0.19.2",
     "starlight-theme-rapide": "^0.5.2"
   }

pnpm-lock.yaml

@@ -0,0 +1,41 @@
+---
+title: Creating a library
+---
+
+import { Steps } from "@astrojs/starlight/components";
+
+To import games and start using Drop, you must first create a library to import from.
+
+<Steps>
+
+1. **Decide on a library layout.**
+
+   Drop supports different layouts for your files on disk, you can read more about them in the [Library Sources](/reference/library-sources) reference section.
+
+2. **Mount your library in the Docker container.**
+
+   For Drop to access your library, you must mount it within the Docker container.
+
+   ```diff
+   drop:
+    image: ghcr.io/drop-oss/drop:latest
+    ...
+    volumes:
+   +  - /mnt/media/my-drop-library:/library
+   ```
+
+   Where:
+   - `/mnt/media/my-drop-library` is the path to your library.
+   - `/library` is a **unique** path inside the container. **Use something else if another volume mounts to `/library`**.
+
+   If you followed the [Quickstart](../quickstart.md) guide, you'll have already set up a library at `./library` pointing to `/library` within the container. You may want to instead edit that line in the `volumes` section to point to where your library is located.
+
+3. **Open library source interface in Admin Dashboard.**
+
+   Head to your admin dashboard, and click on the "Library" tab. Then, in the top rightmost corner, click on "Sources".
+
+4. **Create your library source.**
+
+   Use the "Create" button in the top right to create your library source. Use the **path from inside the container** when providing the path for the library, like `/library` from Step 2.
+
+</Steps>

src/content/docs/admin/guides/creating-library.md

@@ -50,9 +50,9 @@ So your game has gotten an update and you've got new files. All you need to do i
 
 If you have files that you're supposed to **paste over the previous version**, Drop supports that! Read [Update mode](./update-mode.mdx) to find out more.
 
-# Flat-style or 'compat'
+# Compatibility (flat-style)
 
-This is a more commonly used layout for game libraries, but doesn't support all of Drop's features. It's useful when you want to migrate to Drop from another application or having an existing library. **We recommend [Drop-style](#drop-style) libraries if you're starting from scratch**.
+This is a more commonly used layout for game libraries, but doesn't support all of Drop's features. It's useful when you want to migrate to Drop from another application or have an existing library. **We recommend [Drop-style](#drop-style) libraries if you're starting from scratch**.
 
 ## Structuring your library