wip

Author: brendt

docs/1-essentials/02-views.md

@@ -4,13 +4,11 @@ description: "Tempest provides a modern templating engine with syntax inspired b
 keywords: "Experimental"
 ---
 
-:::warning
-Tempest View is currently experimental and is not covered by our backwards compatibility promise.
-:::
-
 ## Overview
 
-Views in Tempest are parsed by Tempest View, our own templating engine. Tempest View uses a syntax that can be thought of as a superset of HTML. If you prefer using a templating engine with more widespread support, [you may also use Blade, Twig, or any other](#using-other-engines)—as long as you provide a way to initialize it.
+Views in Tempest are parsed by Tempest View, our own templating engine. Tempest View uses a syntax that can be thought of as a superset of HTML. If you prefer using a templating engine with more widespread support, [you may also use Blade, Twig, or any other](#using-other-engines) — as long as you provide a way to initialize it.
+
+If you'd like to Tempest View as a standalone component in your project, you can read the documentation on how to do so [here](../5-extra-topics/02-standalone-components.md#tempest-view). 
 
 ### Syntax overview
 

docs/5-extra-topics/02-standalone-components.md

@@ -97,7 +97,7 @@ ld($variable);
 
 ## `tempest/view`
 
-Tempest's view renderer can be used to render views.
+Tempest View can be used as a standalone package:
 
 ```
 composer require tempest/view
@@ -111,6 +111,12 @@ $view = view(__DIR__ . '/src/b.view.php');
 echo $container->get(ViewRenderer::class)->render($view);
 ```
 
+There are a couple of notes to make when running Tempest View as a standalone component:
+
+- Any view files and components will be discovered and must be in a directory with a valid PSR-4 namespace. View files themselves don't need to have a namespace, though.
+- View files are compiled and cached. You can manually enable or disable this cache by setting the `{env}{:hl-keyword:VIEW_CACHE:}` environment variable to `true` or `false`. By default, the view cache is disabled.
+- Optionally, you can require `tempest/console`, which will provide you with the `vendor/bin/tempest view:clear` command to clear view caches. If you don't install `tempest/console`, you'll have to manually clear view caches on deployment by removing the `.tempest/cache/views` directory.
+
 ## `tempest/event-bus`
 
 Tempest's event bus can be used as a standalone package, in order for event handlers to be discovered, you'll have to boot Tempest's kernel and resolve the event bus from the container: