section_view: proof
Work.
- 002
enshroudedserverconfig.com
A config editor for Enshrouded dedicated servers. Makes an invalid file impossible to export.
status: live Astro · Svelte · Cloudflare D1client
Studio product (self-initiated)
scope
Editor, accounts, sharing, search
stack
Astro SSR · Svelte 5 · D1 + Drizzle
measurement
GA4 via GTM, Consent Mode v2
source
Public on GitHub
status
Live
brief
Enshrouded runs its dedicated servers off one JSON file. If that file contains a single syntax error, the game silently wipes it back to defaults. Hours of tuning, gone, with no error message.
This tool replaces hand-editing entirely. Every setting is edited through a validated form, so an invalid export is structurally impossible. Accounts, sharing, likes, and forking sit on top, so a good config can spread instead of living in one player's folder.
shipped
- An editor for every field in enshrouded_server.json, driven by one schema that defines the validation, types, UI ranges, and export shape
- Six presets, Relaxed through Hardcore, as tuned starting points
- Sign-in with Discord or Google, OAuth only, so there are no passwords to store or leak
- Publish, fork, and like shared configs, with full-text search across all of them
- The same measurement discipline as this site: consent-gated GA4 via GTM, nothing loads before acceptance, GPC and DNT always honored
- A test suite over the schema bounds, presets, export, and secret-stripping
the_numbers
invalid_exports
0
the schema makes a broken config file impossible to produce
presets
6
every one derived from the same schema
sign_in_providers
2
Discord and Google; no stored passwords
third_party_before_consent
0
same rule as this site
check_it_yourself
- The live site lets you build a config, download the file, and share it.
- The source is public on GitHub, including the analytics spec and deploy docs.
- 001
forrestblade.com
The studio's own site, run as case study zero: measured, documented, checkable.
status: live Astro · Tailwind · Cloudflareclient
Forrest Blade (studio site)
scope
Marketing site, analytics, forms
timeline
Two weeks
stack
Astro · Tailwind · Cloudflare
measurement
GA4 via GTM, Consent Mode v2
status
Live
brief
The studio needed a marketing site with two jobs: explain the offer in plain language, and demonstrate the measurement setup that comes with every build. Since there was no client work to show yet, the site itself had to carry the demonstration.
shipped
- The core pages: home, services, work, about, and the audit form
- GA4 and Google Tag Manager configured with a documented event spec
- Consent banner wired so no third-party script loads before acceptance
- Form delivery to CRM and inbox, with failed deliveries saved
- Search engine groundwork: titles, sitemap, structured data, previews
- Handoff documentation, published as the measurement page
the_numbers
first_party_js
~13 KB
total JavaScript written for the site
fonts
< 90 KB
self-hosted fonts, no CDN
third_party_before_consent
0
scripts loaded before consent*
hosting_cost
$0/mo
static hosting on Cloudflare
*One exception: the spam-check widget on the audit form, which only loads there.
results
The site is newly live, and these figures are being collected now. They will be published here once there is enough traffic for them to mean something.
- visitors_30d collecting
unique visitors, by source
- consent_rate collecting
share of visitors who accept analytics
- cta_to_form_rate collecting
clicks that turn into form starts
- audit_requests collecting
submitted requests (the key event)
check_it_yourself
- The home page prints your visit's events on screen as they happen.
- The measurement page documents the full event spec and the consent approach.
- Lighthouse in your browser's devtools checks the speed and accessibility scores.