\ No newline at end of file
diff --git a/docs/pages/documentation/$blueprint.md b/docs/pages/documentation/$blueprint.md
index 0e54742..f2de30f 100644
--- a/docs/pages/documentation/$blueprint.md
+++ b/docs/pages/documentation/$blueprint.md
@@ -1,8 +1,8 @@
# $blueprint
-
+
+
BlueprintExtensionLibrary (or $blueprint) is added automatically when using the default controller by leaving your controller path option blank. For custom controllers, you may refer to
this guide.
diff --git a/docs/pages/getting-started/Extension-development.md b/docs/pages/getting-started/Extension-development.md
index e6651fb..18b6711 100644
--- a/docs/pages/getting-started/Extension-development.md
+++ b/docs/pages/getting-started/Extension-development.md
@@ -1,7 +1,28 @@
# Extension development
Set up your extension development environment
+
+
+
Developer mode needs to be turned on in your
admin panel (Admin > Extensions > Blueprint) before you can run developer commands. You only have to do this once.
+
-
+### **Quick start**
+
+Get started by beginning from a template, naming and describing your extension through the initialize command.
+```sh
+blueprint -init
+```
+When choosing a template, select `Barebones` to be able to follow along with this guide. Most options can be changed later, so don't procrastinate too much thinking of an extension name.
+
+After running this command, you can now find your extension files in the `.blueprint/dev` directory (which is located inside of your Pterodactyl folder). You can use cd to change to this directory.
+```sh
+cd .blueprint/dev
+```
+
+
+
While you can develop extensions without ever leaving your terminal emulator, you can also transfer files from your local machine to your server using SFTP or use specific applications to automate this process (such as
this VSCode extension).
+
+
+
\ No newline at end of file