Add the forking instructions

README.md

@@ -8,7 +8,20 @@ This is a game design document template, ready to be forked by you.
 * Mermaid used/recommended for flowcharts and diagrams.
 * Team-friendly, assuming your team can use Git and Markdown.
 
-Please remove this preface when you fork it. Leave a link if you'd like but it's not a priority. [It's yours.](LICENSE)
+## How To Fork
+I don't personally use Github. I don't want to make it easy for code to become training data, though in truth I know that's a losing battle since [intellectual property law is likely only applied one-way from wealthy to unwealthy individuals](https://arstechnica.com/tech-policy/2025/02/meta-defends-its-vast-book-torrenting-were-just-a-leech-no-proof-of-seeding/). Either way, I fight in my own way.
+
+To fork this repository onto Github, if that is your preferred forge, simply:
+
+1. `git clone https://git.misc.work/jahn/forkable-game-design.git my-game`
+2. `cd my-game`
+3. `git remote remove origin`
+
+Then create a repository on Github, and follow Github's steps for pushing an existing repo.
+From there, it's yours. You can sync to upstream if you'd like by adding an additional remote, but your project should grow individually so I'll leave that as an exercise to the reader. I won't be changing much here anyway.
+
+## This is yours.
+Please remove this preface after you fork it. Leave the link at the bottom if you'd like but it's not a priority. [It's yours.](LICENSE)
 
 --------------------------------------------------------------------------------
 
@@ -21,3 +34,7 @@ Truthfully non-linear, but in a loose order of priority.
 3. [Game Systems](systems/README.md)
 4. [Game Graphics](graphics/README.md)
 5. [Game Audio](audio/README.md)
+
+--------------------------------------------------------------------------------
+
+Design docs as Git repos, and the organizational efforts are a brainchild of Jahn at [misc.work](https://misc.work/)