plausible · metmarkosaric · May 8, 2026 · May 8, 2026
diff --git a/docs/authors.md b/docs/authors.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Our team
 ---
 

diff --git a/docs/buttondown.md b/docs/buttondown.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add the script to Buttondown
 ---
 

diff --git a/docs/carrd-integration.md b/docs/carrd-integration.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Adding Plausible to Carrd (and tracking custom events)
 ---
 

diff --git a/docs/community-integrations.md b/docs/community-integrations.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Community integrations
 ---
 

diff --git a/docs/contribute.md b/docs/contribute.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to contribute
 ---
 

diff --git a/docs/custom-automatic-link-tracking.md b/docs/custom-automatic-link-tracking.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Tracking clicks on cloaked affiliate links and other pretty URLs
 ---
 

diff --git a/docs/custom-domain.md b/docs/custom-domain.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Serve the script from your domain as a first-party connection
 ---
 

diff --git a/docs/custom-locations.md b/docs/custom-locations.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Specify a custom location to aggregate pages that contain identifiers
 ---
 

diff --git a/docs/custom-pageview-props.md b/docs/custom-pageview-props.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Custom properties for pageviews
 ---
 

diff --git a/docs/custom-query-params.md b/docs/custom-query-params.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Tracking custom query parameters
 ---
 

diff --git a/docs/data-pipelines.md b/docs/data-pipelines.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Viewing Plausible stats elsewhere
 ---
 

diff --git a/docs/discourse-integration.md b/docs/discourse-integration.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add the script to your Discourse community
 ---
 

diff --git a/docs/docusaurus-integration.md b/docs/docusaurus-integration.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add the script to your Docusaurus site
 ---
 

diff --git a/docs/excluding-localstorage.md b/docs/excluding-localstorage.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Opt out and exclude your visits from the analytics by setting a localStorage flag in your browser
 ---
 

diff --git a/docs/excluding-pages.md b/docs/excluding-pages.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Exclude specific pages from being tracked
 ---
 

diff --git a/docs/get-started-with-postman.md b/docs/get-started-with-postman.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to get started with the Stats API using Postman
 ---
 

diff --git a/docs/ghost-integration.md b/docs/ghost-integration.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add the script to your Ghost site
 ---
 

diff --git a/docs/google-tag-manager.md b/docs/google-tag-manager.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add the script to your site using Google Tag Manager
 ---
 

diff --git a/docs/hash-based-routing.md b/docs/hash-based-routing.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Hashed page paths
 ---
 

diff --git a/docs/hubspot-analytics.md b/docs/hubspot-analytics.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add Plausible Analytics to your HubSpot site
 ---
 

diff --git a/docs/hugo-integration.md b/docs/hugo-integration.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add the script to your Hugo site
 ---
 

diff --git a/docs/internal-link-click-tracking.md b/docs/internal-link-click-tracking.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Internal link click tracking
 ---
 

diff --git a/docs/javascript-snippet.md b/docs/javascript-snippet.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Where do I find my JavaScript snippet?
 ---
 

diff --git a/docs/manual-link-tagging.md b/docs/manual-link-tagging.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Paid campaigns, UTM tags and conversion attribution
 ---
 

diff --git a/docs/mediawiki-integration.md b/docs/mediawiki-integration.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add Plausible to your MediaWiki instance
 ---
 

diff --git a/docs/nextjs-integration.md b/docs/nextjs-integration.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to add the script to your NextJS site
 ---
 
@@ -10,7 +11,7 @@ You can add the script directly to your head through "next/head" or react-helmet
 
 ## Serving the Plausible script
 
-```jsx
+```jsx title="pages/index.jsx"
 import PlausibleProvider from 'next-plausible'
 
 export default Home() {
@@ -25,7 +26,7 @@ export default Home() {
 
 ## Sending custom events
 
-```jsx
+```jsx title="components/PlausibleButton.jsx"
 import {usePlausible} from 'next-plausible'
 
 export default PlausibleButton() {

diff --git a/docs/plausible-analytics-reviews.md b/docs/plausible-analytics-reviews.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Plausible Analytics reviews and in media
 ---
 

diff --git a/docs/plausible-analytics-self-hosted-guides.md b/docs/plausible-analytics-self-hosted-guides.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Plausible Community Edition (CE)
 ---
 

diff --git a/docs/proxy/guides/akamai.md b/docs/proxy/guides/akamai.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Proxying Plausible through Akamai
 ---
 

diff --git a/docs/proxy/guides/apache.md b/docs/proxy/guides/apache.md
@@ -10,7 +10,7 @@ Our managed proxy lets you send analytics through your own domain name as a firs
 
 ## Step 1: Enable the required modules
 
-```
+```bash
 sudo a2enmod proxy
 sudo a2enmod proxy_http
 sudo a2enmod ssl
@@ -32,7 +32,7 @@ the snippet specific for your site. It will look similar to the following:
 Your snippet will have a different script location than the example above. Look for the `https://plausible.io/js/pa-XXXXX.js` part in your snippet - that's the personalized location for your site's script. Mark it down for subsequent steps.
 
 ## Step 3: Update your config
-```
+``` title="apache-vhost.conf"
 <VirtualHost *:80>
   ServerName website.com
 

diff --git a/docs/proxy/guides/caddy.md b/docs/proxy/guides/caddy.md
@@ -28,7 +28,7 @@ Your snippet will have a different script location than the example above. Look
 
 Add the following to your Caddyfile:
 
-```
+``` title="Caddyfile"
 @plausible path /js/script.js /api/event
 handle @plausible {
 	# Use path from step 1

diff --git a/docs/proxy/guides/cloudflare.md b/docs/proxy/guides/cloudflare.md
@@ -21,7 +21,7 @@ In your Cloudflare account, click on the "Compute (Workers" > 'Workers & Pages'
 
 ## Step 2 (Optional): You can change your service name
 
-This is optional but you can change the service name to give your worker a more meaningful name. Do avoid words like 'plausible', 'analytics', 'tracking', 'stats', etc. as they may be blocked. It's also fine to keep the random name that Cloudflare generates by default. Then click on the 'Deploy' button.
+This is optional but you can change the service name to give your worker a more meaningful name. It's also fine to keep the random name that Cloudflare generates by default. Then click on the 'Deploy' button.
 
 <img alt="Deploy CloudFlare worker" src={useBaseUrl('img/deploy-cloudflare-worker.png')} />
 
@@ -46,17 +46,21 @@ Next click on the 'Edit Code' button, remove the default code that Cloudflare pr
 
 <img alt="Edit CloudFlare worker" src={useBaseUrl('img/edit-worker-code.png')} />
 
-We recommend you change the folder name in the first two lines in the code below. This makes your proxy more difficult to discover and block. We especially recommend you change the folder name in the two lines if you're not hosting your site on the Cloudflare CDN.
+:::tip
+Change the folder name in the first two lines of the code below. This makes your proxy harder to discover and block, especially if you're not hosting your site on the Cloudflare CDN.
+:::
 
 In the **ProxyScript** line, change `https://plausible.io/js/pa-XXXXX.js` to your script location from step 3.
 
 In the **ScriptName** line, change the `/js/` to whatever you wish. Say `/your-folder-name/`. Then the location in the code would be `/your-folder-name/script.js`.
 
 In the **Endpoint** line, change the `/api/` to whatever you want. It can be the same as above but you can also choose something different. If you choose `/your-folder-name/`, then the full location would be `/your-folder-name/event`.
 
-Do avoid words like 'plausible', 'analytics', 'tracking', 'stats', etc. as they may be blocked.
+:::warning
+Avoid words like 'plausible', 'analytics', 'tracking', 'stats' in path names as they may be blocked.
+:::
 
-```js
+```js title="cloudflare-worker.js"
 const ProxyScript = 'https://plausible.io/js/pa-XXXXX.js'
 const ScriptName = '/js/script.js';
 const Endpoint = '/api/event';

diff --git a/docs/proxy/guides/cloudfront.md b/docs/proxy/guides/cloudfront.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Proxying Plausible through CloudFront
 ---
 

diff --git a/docs/proxy/guides/deno.md b/docs/proxy/guides/deno.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Proxying Plausible through Deno Deploy
 ---
 

diff --git a/docs/proxy/guides/fastly.md b/docs/proxy/guides/fastly.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Proxying Plausible through Fastly
 ---
 

diff --git a/docs/proxy/guides/fresh.md b/docs/proxy/guides/fresh.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Proxying Plausible through Fresh
 ---
 

diff --git a/docs/proxy/guides/laravel.md b/docs/proxy/guides/laravel.md
@@ -29,7 +29,7 @@ php artisan make:controller PlausibleProxyController
 
 Add the following code to the controller, replacing `https://plausible.io/js/pa-XXXXX.js` with the script location from Step 1.
 
-```php
+```php title="app/Http/Controllers/PlausibleProxyController.php"
 <?php
 
 namespace App\Http\Controllers;
@@ -74,25 +74,27 @@ class PlausibleProxyController extends Controller
 
 Add the following routes to your `routes/web.php` file:
 
-```php
+```php title="routes/web.php"
 use App\Http\Controllers\PlausibleProxyController;
 
 Route::get('/js/script.js', [PlausibleProxyController::class, 'script'])->name('plausible.script');
 Route::post('/api/event', [PlausibleProxyController::class, 'event'])->name('plausible.event');
 ```
 
-Note that:
-
-- You can use whatever paths you like here. Do choose generic names. If you choose something like `analytics`, `stats` or `plausible`, it may get blocked.
+:::warning
+Use generic path names. Paths like `/analytics`, `/stats` or `/plausible` may get blocked by adblockers.
+:::
 
 
 ## Step 4: Exempt the event route from CSRF
 
-The Plausible script sends POST requests to the event endpoint, which Laravel's CSRF protection will block by default.
+:::warning
+Laravel's CSRF protection will block POST requests to the event endpoint by default. This step is required for tracking to work.
+:::
 
 In your `bootstrap/app.php` file, add the event route to the CSRF exceptions:
 
-```php
+```php title="bootstrap/app.php"
 ->withMiddleware(function (Middleware $middleware) {
     $middleware->validateCsrfTokens(except: [
         'api/event', // Add this line
@@ -104,7 +106,7 @@ In your `bootstrap/app.php` file, add the event route to the CSRF exceptions:
 
 Add the script tags to your application's HTML `<head>`, configuring the `src` and `endpoint` to match the named route from Step 3:
 
-```blade
+```blade title="layout.blade.php"
 <script async src="{{ route('plausible.script') }}"></script>
 <script>
   window.plausible=window.plausible||function(){(plausible.q=plausible.q||[]).push(arguments)},plausible.init=plausible.init||function(i){plausible.o=i||{}};

diff --git a/docs/proxy/guides/netlify.md b/docs/proxy/guides/netlify.md
@@ -37,7 +37,11 @@ Replace `https://plausible.io/js/pa-XXXXX.js` with script location from step 1.
 Note that:
 
 - The source paths identified here **must be** used when configuring the HTML script tag in the next section.
-- You can use whatever paths you like here (for example, here prefixing with `/your-subdirectory/`). Do choose a generic or irrelevant name. If you choose something like analytics, stats or plausible, it might get blocked.
+- You can use whatever paths you like here (for example, here prefixing with `/your-subdirectory/`).
+
+:::warning
+Avoid names like `analytics`, `stats` or `plausible` in your paths as they may get blocked.
+:::
 
 ## Step 3: Update your snippet
 
@@ -59,6 +63,8 @@ Deploy these changes to your Netlify site. You can verify the proxy is working b
 
 ## Troubleshooting
 
-If your `<script>` tag's `src` attribute is being manipulated to some unrecognised CDN URL, it's because you have the `Asset optimization` JS settings enabled in Netlify. Both the `Bundle JS` and `Minify JS` options must be de-selected to avoid interference with the proxied Plausible URL. 
+:::warning
+If your `<script>` tag's `src` attribute is being rewritten to an unrecognised CDN URL, you have `Asset optimization` JS settings enabled in Netlify. Both the `Bundle JS` and `Minify JS` options must be de-selected to avoid interference with the proxied Plausible URL.
+:::
 
-Prefer not to disable the `Asset optimization`? Try to use the absolute URL in the `src` attribute of your `<script>` (`https://yourdomain.com/your-subdirectory/js/script.js`).
+Prefer not to disable `Asset optimization`? Use the absolute URL in the `src` attribute instead: `https://yourdomain.com/your-subdirectory/js/script.js`.
diff --git a/docs/proxy/guides/nextjs.md b/docs/proxy/guides/nextjs.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: Proxying Plausible with Next.js
 ---
 

diff --git a/docs/proxy/guides/nginx.md b/docs/proxy/guides/nginx.md
@@ -25,7 +25,7 @@ Your snippet will have a different script location than the example above. Look
 
 ## Step 2: Update your Nginx config
 
-```
+```nginx title="nginx.conf"
 # Only needed if you cache the plausible script. Speeds things up.
 #
 # Note: to use the `proxy_cache` setup, you'll need to make sure the `/var/run/nginx-cache`

diff --git a/docs/proxy/guides/vercel.md b/docs/proxy/guides/vercel.md
@@ -37,7 +37,7 @@ Add a special `vercel.json` file in your application root:
 
 Add the following JSON to rewrite calls within your application to Plausible's resources:
 
-```json
+```json title="vercel.json"
 {
   "rewrites": [
     {
@@ -57,7 +57,11 @@ Replace `https://plausible.io/js/pa-XXXXX.js` with script location from step 1.
 Note that:
 
 - The source paths identified here **must be** used when configuring the HTML script tag in the next section.
-- You can use whatever paths you like here (for example, here prefixing with `/your-subdirectory/`). Do choose a generic or irrelevant name. If you choose something like analytics, stats or plausible, it might get blocked.
+- You can use whatever paths you like here (for example, here prefixing with `/your-subdirectory/`).
+
+:::warning
+Avoid names like `analytics`, `stats` or `plausible` in your paths as they may get blocked.
+:::
 
 ## Step 4: Update your snippet
 

diff --git a/docs/script-extensions-for-wp-plugin.md b/docs/script-extensions-for-wp-plugin.md
@@ -1,4 +1,5 @@
 ---
+displayed_sidebar: someSidebar
 title: How to use script extensions with the WordPress plugin
 ---