docs(user): document all share theme attributes

docs/User Guide/User Guide/Advanced Usage/Sharing/Exporting HTML for web publish.md

@@ -10,7 +10,7 @@ Apart from the enhanced security, these HTML files are also easy to deploy on
 > 
 > The process is [automated](https://github.com/TriliumNext/Trilium/blob/main/apps/edit-docs/src/build-docs.ts) by importing the Markdown documentation and exporting it via a script to the static web format.
 
-## Differences from normal sharing and export
+## Differences from normal sharing
 
 Apart from normal <a class="reference-link" href="../Sharing.md">Sharing</a>, exporting to static HTML files comes with a few subtle differences:
 
@@ -38,4 +38,8 @@ Once installed simply:
 
 1.  Extract the exported .zip file.
 2.  Inside the extracted directory, run `http-server`.
-3.  Access the indicated address (e.g. [http://localhost:8080](http://localhost:8080)).
+3.  Access the indicated address (e.g. [http://localhost:8080](http://localhost:8080)).
+
+## Automation
+
+<a class="reference-link" href="../ETAPI%20(REST%20API).md">ETAPI (REST API)</a> could potentially be used to automate an export on a scheduled task.

docs/User Guide/User Guide/Advanced Usage/Sharing/Reverse proxy configuration.md

@@ -0,0 +1,18 @@
+# Reverse proxy configuration
+It might be desirable to only expose the share functionality of Trilium to the Internet, and keep the application accessible only within a local network or via VPN.
+
+To do so, a reverse proxy is required.
+
+## Caddy
+
+```
+http://domain.com {
+  reverse_proxy /share http://localhost:8080/share
+}
+```
+
+This is for newer versions where the share functionality is isolated, for older versions it's required to also include `/assets`.<sup><a href="#fn2b8mg20aol8">[1]</a></sup>
+
+1.  <sup><strong><a href="#fnref2b8mg20aol8">^</a></strong></sup>
+    
+    [https://github.com/orgs/TriliumNext/discussions/7341#discussioncomment-14679897](https://github.com/orgs/TriliumNext/discussions/7341#discussioncomment-14679897)