feat: add documentation for {viewcontext} and {appcontext}

Author: prplwtf

apps/frontend/content/docs/concepts/placeholders.md

@@ -115,6 +115,26 @@ For example, you could use the `{webroot/public}` placeholder to add an image to
 <img src="{webroot/public}/cool_image.jpeg" />
 ```
 
+### Context
+
+Context placeholders simplify otherwise complicated paths and generally improve compatibility.
+
+#### Appcontext
+
+Returns the namespace prefix for an extension's PHP classes.
+
+| Placeholder    | Output                                                |
+| -------------- | ----------------------------------------------------- |
+| `{appcontext}` | Pterodactyl\BlueprintFramework\Extensions\myextension |
+
+#### Viewcontext
+
+Returns the view prefix for an extension's views.
+
+| Placeholder     | Output                           |
+| --------------- | -------------------------------- |
+| `{viewcontext}` | blueprint.extensions.myextension |
+
 ### Installer
 
 Technical details about the framework handling the extension.

apps/frontend/content/docs/concepts/routing.md

@@ -71,10 +71,10 @@ In your `requests.app` directory (which is called `app` in this case), create a
 ```php [app/FooController.php]
 <?php
 
-// This is the namespace 'requests.app' lives in. {identifier}
-// is automatically replaced with your extension's identifier
-// upon installation.
-namespace Pterodactyl\BlueprintFramework\Extensions\{identifier};
+// This is the namespace 'requests.app' lives in. {appcontext}
+// is automatically corrected by Blueprint upon installing your
+// extension.
+namespace {appcontext};
 
 use Pterodactyl\Http\Controllers\Controller;
 
@@ -94,7 +94,7 @@ Finally, update your `requests.routers.web` router. Import the `requests.app` na
 <?php
 
 use Illuminate\Support\Facades\Route;
-+ use Pterodactyl\BlueprintFramework\Extensions\{identifier};
++ use {appcontext};
 
 - Route::get('/foo', function () {
 -   return 'bar';
@@ -142,7 +142,7 @@ Create a controller called `FizzController.php` and make it render the `fizz.bla
 ```php [app/FizzController.php]
 <?php
 
-namespace Pterodactyl\BlueprintFramework\Extensions\{identifier};
+namespace {appcontext};
 
 use Pterodactyl\Http\Controllers\Controller;
 
@@ -156,9 +156,9 @@ class FizzController extends Controller {
   // Create another index function, this time promising a view
   // to be returned.
   public function index(): View {
-    // Make the view. 'requests.views' are always prefixed with
-    // 'blueprint.extensions.{identifier}'.
-    return $this->view->make('blueprint.extensions.{identifier}.fizz');
+    // Render a view. Views should be prefixed with {viewcontext}
+    // which is automatically replaced by Blueprint.
+    return $this->view->make('{viewcontext}.fizz');
   }
 }
 ```
@@ -169,7 +169,7 @@ Add the `/fizz` route to your `requests.routers.web` router.
 <?php
 
 use Illuminate\Support\Facades\Route;
-use Pterodactyl\BlueprintFramework\Extensions\{identifier};
+use {appcontext};
 
 Route::get('/foo', [FooController::class, 'index']);
 + Route::get('/fizz', [FizzController::class, 'index']);

apps/frontend/content/docs/configs/confyml.md

@@ -272,7 +272,7 @@ Defines how Blueprint should handle your extension's web request routing and app
 
 #### `requests.views`
 
-Directory containing additional blade view files. Symlinked to `resources/views/blueprint/extensions/{identifier}` for Laravel's view system and accessible as `blueprint.extensions.{identifier}.*`.
+Directory containing additional blade view files. Symlinked to `resources/views/blueprint/extensions/{identifier}` and accessible as `{viewcontext}.my-view-name`.
 
 ```yaml [conf.yml]
 requests:
@@ -283,7 +283,7 @@ requests:
 
 #### `requests.app`
 
-Application logic and controllers directory. Symlinked to `app/BlueprintFramework/Extensions/{identifier}`.
+Application logic and controllers directory. Symlinked to `app/BlueprintFramework/Extensions/{identifier}`, accessible as `{appcontext}\MyClassName`.
 
 ```yaml [conf.yml]
 requests: