Bouda kácí

Website of Tomáš Bouda's tree-felling and tree-care business — https://boudakaci.cz.

The pages are hand-written HTML, CSS and JavaScript with no framework and no build step. A small ASP.NET Core application (.NET 10) serves them and adds what a static host could not:

• POST /api/poptavka — the contact form, e-mailed through Resend, with a confirmation to a customer who left an e-mail, or a text to one who left a mobile number (through SMSbrána.cz, SMS Connect API, Site:Sms:Login/Password)
• POST /api/resend/inbound — Resend's signed webhook (Svix) for mail received at any address of boudakaci.cz (the domain's MX points to Resend); the e-mail with its attachments is fetched from Resend's receiving API and forwarded to Site:Resend:To with the original sender as reply-to. Needs Site:Resend:WebhookSecret and a full-access API key; once set, customers reply to the confirmation at poptavka@boudakaci.cz
• When to fell kdy-kacet.html — the months for felling and a seasonal scene (kdy-kacet.js: sawing in the dormant season, checking the nest with binoculars while birds nest, measuring the trunk for the permit in autumn, a Christmas tree in December; ?mesic=1–12 opens another month)
• Advice /rady and /rady/{slug} — articles written as Markdown in Content/rady/*.md (front matter title, description, slug; a ## Časté otázky section with ### question items becomes the FAQ, anything after it closes the article). Rendered with Markdig into Templates/rada.html and listed in the sitemap; a new file is picked up without a restart
• Structured data — the home page and the articles carry an FAQPage built from their own FAQ markup, and the LocalBusiness areaServed follows the districts served set in the admin (Site/StructuredData.cs)
• Contacts kept from harvesters — no page carries the phone or the e-mail (not even the structured data): the links lead to /#kontakt and show a mask („605 870 •••“). After the first genuine interaction of a person (mouse movement, touch, key, wheel; isTrusted) script.js asks /api/kontakt (from Site:Business) and fills in the tel:, WhatsApp and mailto: links and the shown numbers; a tap before that waits for them and then dials. The same idea as in the arborist catalogue (Arboriste, ContactGuard)
• Price page cenik.html and permit guide povoleni-ke-kaceni.html; prices come from the admin
• Municipality pages /kaceni-stromu/{obec} built from the published jobs (template Templates/obec.html), and a generated /sitemap.xml
• Map page mapa.html — the districts of Plzeňský kraj the business serves and the municipalities where work is done, on Mapy.com tiles
• Admin /admin — one password: jobs from the inquiry to the finished work, with their photos (map + gallery), felling permit applications (PDF for the municipal office), the price list and the served districts
• GET /health — status and version for the deploy and the VPS dashboard
• a log (daily files + the admin Logs page)

It runs as one Docker container on the VPS (37.205.12.163) behind the shared nginx.

Repository

The pages carry two placeholders the application fills in when serving them: __GA_MEASUREMENT_ID__ (GA4 ID from configuration; anything else leaves analytics off) and __APP_VERSION__ (from the build).

Running locally

dotnet run --project src/BoudaKaci.Web --launch-profile boudakaci

The site answers on http://localhost:5270. Settings come from appsettings.json, overridden by src/BoudaKaci.Web/appsettings.Local.json (git-ignored) or environment variables:

The API keys never reach the browser: tiles (/api/tiles/{z}/{x}/{y}) and the municipality search (/admin/api/obce) go through the application.

Tests

dotnet test BoudaKaci.slnx

They cover the contact form (validation, honeypot, photo limits, HTML escaping, rate limit, Resend failures), page serving with the placeholders, security and cache headers, health, the tile proxy, sign-in and the job admin down to what the public map shows. The pipeline runs them before every deploy.

Site visits and the price calculator

A job has a site visit („obhlídka“, Visits/, tables site_visits and visit_trees, schema 10) at /admin/zakazka/{job}/obhlidka: the facts Tomáš collects at the tree — date, address, one-way distance, access (trailer to the tree or carrying so many metres), wires nearby (power lines show a red warning: he does not work near them), and one card per tree: species (picker from Permits/TreeNames.cs), height, circumference at 130 cm (the diameter is derived), the fruit-tree exemption, the kind of work (FellGround, FellSectional, Prune, DeadBranches, Reduction), what is near the tree, the state of the wood, what happens to the wood and brush, the stump height, the hours on the tree and of cleanup (prefilled from the settings by kind and height band, in admin.js and again on the server when posted empty) and whether a helper is needed. VisitTree.NeedsPermit is derived: circumference over 80 cm, not an exempt fruit tree, and the tree is to be felled. The form is built for a phone (one column under 700 px, plain POST, no script needed).

Visits/VisitCalculator.cs is pure and turns a visit, the calculator settings, the felling ladder and the price cards into proposed quote lines, each with an explanation: felling from the ground is the ladder row for the diameter (the label is parsed: „do 30 cm“, „31–50 cm“, „nad 70 cm“); sectional felling, or any felling near a target, is charged as hours of Tomáš and the helper with the risky row as the floor plus a risk surcharge in percent of that row; pruning is the „Prořez“ card per tree, or the same hourly scheme when climbing (over 6 m or near a target); cleanup is the sum of processing hours at the hourly rate; carrying, hauling („Odvoz“ card per trailer load) and travel beyond the included kilometres follow. Bad wood adds its percentage; estimated work lines are rounded to the settings' step; travel under 100 CZK is dropped with a note. The page shows the total and the margin check (price per hour on site against the hourly rate). Settings live in Ceny → „Kalkulačka obhlídky“ (table calculator_settings, one JSON document, Visits/CalculatorSettings.cs holds the defaults from the October 2026 price sheet). tests/BoudaKaci.Web.Tests/VisitCalculatorTests.cs pins the worked examples A–E of that sheet.

„Vytvořit nabídku z obhlídky“ saves the form and opens a new quote with the proposed lines (VAT handling as any quote); „Založit žádost o povolení“ starts a permit application with the trees that need one, the job's customer as owner and the visit's TreeMap link. When the visit has a TreeMap share link, the page re-reads the share on every opening (and on „Načíst stromy z TreeMapu“): one tree per shared tree keyed by TreeMap's tree id — new ones are added with species, circumference, height, the note „TreeMap strom N, štítek …“ and the kind of work mapped from the proposed measure (S-KV/S-KSP → from the ground, S-KPV/S-KPP → in parts, S-RB → dead branches, reductions → reduction, other S-R*/O-* → pruning; measures already done or deleted are ignored); existing ones get their species, circumference and height refreshed, their pricing facts are never overwritten, nothing is deleted. A share that does not answer leaves the stored trees and shows a quiet note.

The round trip with TreeMap (0.19+) needs no copying of links. While the visit has no share link, „Otevřít v TreeMapu“ is the deep link {Site:TreeMap:BaseUrl}/#new?name=<job title>&parent=<Site:TreeMap:JobsProject>&return=<absolute URL of the visit page> (Permits/TreeMapLinks.cs; the return URL is built from the request, so it works on localhost too). TreeMap creates — or reuses by exact name under that parent — the job's project, makes its share token and, on „Zpět do administrace“, navigates back to the visit page with ?share=<token>. The page validates the token (24 characters of [A-Za-z0-9_-]), stores {BaseUrl}/#share=<token> as the visit's TreeMap link (creating the visit row when none exists yet), runs the usual sync and redirects to the clean URL with the note „Projekt z TreeMapu připojen, stromy načteny“; an invalid token is ignored with a quiet note. Once a share link is stored, the plain „Otevřít v TreeMapu ↗“ opens it and the deep link stays available as „Založit nový projekt v TreeMapu“. TreeMap accepts only boudakaci.cz and localhost as return hosts (RETURN_HOSTS in its app/src/config.js).

Customer source, inquiry details and statistics

A job carries Source (Jobs/JobSource.cs: google, seznam, bazos, web-direct, referral, municipality, facebook, partner, repeat, other; schema 12) and a free-text SourceNote, edited on the job form and shown as a chip in the job list, which /admin?zdroj=<source> filters (- = jobs without a source).

An inquiry from the contact form is attributed automatically. script.js remembers, for the browser session only (sessionStorage), the first page of the visit with its query string, document.referrer and utm_source / utm_medium / utm_campaign, and posts them with the inquiry (landingPage, referrer, utm* — hidden fields, nothing the visitor sees changes). JobSource.FromAttribution maps them: utm_source wins when present, otherwise the referrer's host (google.* → Google, seznam.cz / firmy.cz / mapy.cz → Seznam, bazos.cz → Bazoš, facebook.* / instagram.* → Facebook, no referrer or boudakaci.cz → web přímo, anything else → jiné).

Alongside, Inquiries/InquiryMeta.cs stores non-identifying details of the visit in inquiry_meta (one row per inquiry job): the device class (phone / tablet / desktop), the browser family with its major version, the OS family, the primary language tag of Accept-Language, the landing page, the referrer, the UTM values and the timestamp. The IP address and the raw user-agent string are not stored (the address only passes through the in-memory rate limiter as before). The details are shown only on the job detail in the admin, collapsed as „Technické údaje poptávky“; they are not in the public API (/api/galerie), the quote or the log, and they go with the job when it is deleted.

/admin/statistiky (Jobs/JobStatistics.cs, pure) shows per month for the last 12 months (with a CSS bar each) and per year: inquiries (jobs by their month), accepted, done and rejected, revenue (the latest quote of each done job; 0 without a quote), hours on site (the visit's estimated hours) and realised CZK/h over the done jobs that have both; the sources with count, done, conversion and revenue; the devices of inquiries from the form. „Stáhnout CSV“ (?handler=Csv) exports the jobs with source, quote total, hours and device as a semicolon-separated UTF-8 file.

Places, distances and PDF text

• Municipality search (/admin/api/obce, Maps/MapyClient.cs): Mapy.com suggest with type=regional.municipality and type=regional.municipality_part, limit=15, locality=cz and preferNear = the geocoded base address (Plzeň when it cannot be geocoded); answers in Plzeňský kraj are listed first, a part shows the municipality it belongs to („Horušany — část obce Nýřany, okres Plzeň-sever, Plzeňský kraj“), and the main part of a municipality is not listed twice.
• Visit address and distance: a new visit's address starts as the job's municipality (a job keeps no street; the street goes into the job notes and is added on the visit). On save, while the distance is empty or the address changed without a new distance typed, the one-way driving distance is computed through Mapy.com — the base address (Site:Business:BaseAddress, else Address) is geocoded once and cached for a week, the visit address is geocoded (or the job's municipality centre is used when the address is just the municipality), and routing/route with routeType=car_fast gives the length, rounded to whole km. „Přepočítat vzdálenost“ forces it. Without a Mapy.com key the distance stays as typed and the save shows a quiet note.
• PDF text (Pdf/PdfText.cs): QuestPDF draws only with the shipped Barlow faces and, since 2026.9, a missing glyph aborts the document. Every text in the quote and permit PDFs passes PdfText.Safe at render time: coverage is read from the TTF files (all weights), and characters they lack become readable stand-ins — ⌀ → Ø, → → ->, ✓ → ano, the narrow no-break space → a space — or are dropped. Barlow lacks ⌀ ∅ → ← ↗ ✓ and U+202F; it has the Czech letters, – — „ “ × ≥ ≤ ½ ° ² ³ … · €.

Price quotes

A job has price quotes (Quotes/, table quotes, schema 9): /admin/zakazka/{job}/nabidka prefills the customer, the place and the next number of the year (2026-001); items come from the price list (the felling ladder and the cards) through a picker or are typed in, with prices including VAT like the price list. …/nabidka/{id}/pdf renders an A4 PDF (QuestPDF) with the logo (Templates/logo-bouda-kaci.webp), supplier with IČO and DIČ (Site:Business), customer, items, the tax base and VAT worked out from the gross total, the note and the validity. Tomáš sends it himself.

Felling permit applications

/admin/povoleni keeps applications Tomáš prepares for customers: owner, parcel, trees, reasons, photos and the share link of the TreeMap project. /admin/povoleni/{id}/pdf renders one PDF (QuestPDF, Community licence) with the application (§ 8 of Act 114/1992, § 4 of Decree 189/2013), a QR code of the TreeMap link (QRCoder), the power of attorney to sign and the photos; empty fields print as dotted lines. The typeface is Barlow from Templates/fonts (OFL). Tomáš's details as the representative come from Site:Business in configuration. The applications hold personal data of the owner (name, date of birth, address) — delete them once the permit is settled.

When the cadastral area and the parcel number(s) are filled in, the PDF also gets an excerpt of the cadastral map (Permits/CadastralMap.cs): the area and the parcel outlines come from the ČÚZK RÚIAN map server (ags.cuzk.gov.cz/arcgis/rest/services/RUIAN/MapServer, layers 7 and 5), the map image from the cadastral WMS (services.cuzk.gov.cz/wms/wms.asp, layer KN, EPSG:5514); the parcels are drawn in red with SkiaSharp. No key is needed. The excerpt is cached for an hour; /admin/povoleni/{id}/katastr.png shows it in the admin. When ČÚZK does not answer or the parcel is not found, the PDF is printed without it.

When the application has a TreeMap share link, Permits/TreeMapClient.cs reads the project through TreeMap's public share API (GET /api/shares/{token}, no sign-in) and the trees within 300 m of the parcel are drawn as numbered dots with a legend. GPS positions are converted to S-JTSK in Permits/Sjtsk.cs (Helmert + Křovák, EPSG method 9819). The button „Načíst stromy a fotky z TreeMap“ saves the form, replaces the tree rows with the trees of the share and downloads their photos (the tree photo and inspection photos, {photoBase}/{photoId}) into the permit photos; each imported photo remembers its origin (permit_photos.source = treemap:<id>, schema 7), so loading again adds only new ones.

E-mail

All mail of boudakaci.cz runs through Resend; Tomáš's own mailbox stays email@tomasbouda.cz (WEDOS), read in Gmail.

There is no mailbox at boudakaci.cz: every address of the domain ends up in the forward, so tomas@, poptavka@ and any other address work alike.

How it is set up

1. Resend → Domains: boudakaci.cz verified for sending (SPF/DKIM records in DNS, send.boudakaci.cz MX for bounces).
2. Resend → Emails → Receiving: receiving on for boudakaci.cz; the root MX record is Resend's.
3. Resend → Webhooks: endpoint https://boudakaci.cz/api/resend/inbound, event email.received. Its signing secret (whsec_…) is RESEND_WEBHOOK_SECRET in the Azure DevOps group bouda-kaci-deployment (→ Site:Resend:WebhookSecret). The endpoint checks the Svix signature and refuses deliveries older than 5 minutes.
4. Resend → API Keys:
   • the site's key (RESEND_API_KEY) has full access — reading received mail needs it, a sending-only key gets 401/403 from the receiving API;
   • Gmail has its own sending-only key for boudakaci.cz, so it can be revoked without touching the site.
5. Gmail → Settings → Accounts → Send mail as → Add another address: Tomáš Bouda <tomas@boudakaci.cz>, SMTP server smtp.resend.com, port 465 (SSL) or 587 (TLS), user resend, password = Gmail's Resend key. Gmail's verification code sent to tomas@boudakaci.cz arrives through the forward. When answering a forwarded e-mail, pick tomas@boudakaci.cz in the From field — Gmail offers email@tomasbouda.cz by default, because that is where the forward was delivered.

/health shows the state in the entry inbound. A forward that fails is logged (Admin → Logy) and the e-mail stays in Resend under Emails → Receiving; a webhook delivered twice is forwarded once. Mail coming from the site's own sender address is not forwarded, so a bounce cannot loop.

Measuring inquiries

script.js sends GA4 events once the visitor has accepted analytics: generate_lead for a sent inquiry, click_phone and click_whatsapp for the contact links (with link_location). Mark them as key events in GA (Admin → Events) to count them as conversions.

Map and jobs

• District boundaries: wwwroot/data/okresy.geojson — Plzeňský kraj, its seven districts and the nine neighbouring ones (Cheb, Sokolov, Karlovy Vary, Rakovník, Beroun, Příbram, Strakonice, Písek, Prachatice) from ČÚZK INSPIRE Územní správní jednotky (CC BY 4.0), simplified to about 100 m (148 kB).
• Which districts are served is set in the admin (Okresy) and stored in the database; the map draws the districts of the region always and a neighbouring one only when it is served.
• Photos belong to a job. The admin page shrinks them in the browser (which also turns HEIC into JPEG and applies the EXIF rotation) and the server writes a 3:4 thumbnail in two sizes and the whole photo for the lightbox, as WebP and JPEG, to {DataDirectory}/photos under a random name; /media/… serves them. The gallery shows published jobs with at least one photo.
• A job is entered with a municipality picked from the Mapy.com search, so its pin is always the centre of the village, never a house; the public API rounds it once more. Only published jobs are shown.
• Mapy.com asks for its logo and attribution on the map; mapa.js adds both.
• Jobs have a status: every inquiry from the contact form is stored as a job in Poptávka (InquiryJobs) with the customer's name, contact, message and photos, and the e-mail to Tomáš links to it. Tomáš accepts or rejects it, adds his own notes and photos to an accepted job and marks it done, which publishes it. Only a done, published job reaches the map, the gallery and the town pages, and only its photos marked Na webu — the customer's photos start private. The customer's details never leave the admin.
• A job can start a felling permit application (permits.job_id): office, owner and contact are filled in from the job and its photos are copied (new files, so deleting one side never breaks the other).

Deployment

Every push to main runs azure-pipelines.yml: tests, Docker image, smoke test, then deploy/deploy-vps.sh on the VPS over SSH as codexdeploy — the same scheme as the app store and Arbo. The script picks a free port (5184–5220, remembered in /opt/boudakaci/port), keeps the data in /opt/boudakaci/data, renders the nginx site, obtains a Let's Encrypt certificate for every name in vpsDomains and only passes a release whose /health answers Healthy.

Variable group bouda-kaci-deployment (Azure DevOps → Pipelines → Library):

The GA4 ID comes from the web-analytics group. A secret left out of a run keeps the value already deployed.

Moving the domain (Přechod domény)

Until boudakaci.cz points at the VPS, the pipeline deploys to boudakaci.tomlabs.xyz only (the *.tomlabs.xyz wildcard already points there; the staging site sends X-Robots-Tag: noindex). To move:

1. Check the staging site, sign in to /admin, add a job.
2. At WEDOS change boudakaci.cz and www.boudakaci.cz to A 37.205.12.163 and AAAA 2a03:3b40:fe:764::1. Keep the TXT records (Search Console verification, Resend SPF/DKIM).
3. When the names resolve to the VPS, set vpsDomains in azure-pipelines.yml to boudakaci.cz www.boudakaci.cz boudakaci.tomlabs.xyz, healthPath to /health, and push. The deploy extends the certificate to the new names.
4. Delete the Azure Static Web App.

Images and fonts

Images in assets/ are derived files; the masters are in originals/. Photos have the crop baked in to match the CSS (object-fit: cover), so no pixels are downloaded that are never shown; when an aspect ratio changes in CSS, regenerate the images. Variants are name-<width>.{avif,webp,jpg}; <picture> offers AVIF, WebP and JPEG as the fallback. They are generated with ffmpeg (or sharp, installed outside the repo).

Assets are cached for 30 days and fonts for a year, and file names carry no content hash: when replacing a photo, give it a new name, otherwise visitors keep the old one for a month.

The logo master is originals/logo-bouda-kaci.webp (the whole lockup with the name). The mark on the site is only its tree with the climber: assets/znak-96.png is transparent (originals/logo-strom-pruhledne.png, made by flattening the master onto white and keying the white out, so no dark fringe shows) and turns white on dark backgrounds through CSS (filter: brightness(0) invert(1)). The browser and phone icons znak-16/32/180/512.png sit on a solid light square (originals/logo-strom.png) so they stay visible on dark tab bars. Icons have new file names on every change — they are cached for 30 days. assets/favicon-32.png stays as a copy because an old release redirected /favicon.ico to it permanently.

The share image assets/og-image.jpg (1200×630, what Facebook and WhatsApp show) is rendered from tools/og-image/og-image.html (the site's fonts, the mark and originals/tomas-bouda-strom.jpg) with headless Edge; the command is in the file. The pages link it with a ?v= suffix — raise it when the image changes, because Facebook and WhatsApp cache the image by URL.

The fonts are Barlow (text) and Barlow Semi Condensed (headings), self-hosted. cd src/BoudaKaci.Web/wwwroot && node ../../../tools/fetch-fonts.mjs downloads them from Google Fonts and prints the @font-face block for styles.css. The *-latin-ext.woff2 variants are subset to Czech and Slovak letters with subset-font (npm install --no-save --no-package-lock subset-font, outside the repo); the *-latin.woff2 ones stay complete because they also cover what a visitor types into the form. Barlow is used up to weight 700; when the weights change, update FAMILIES in the script and the preload in index.html.

Print

print/vizitka.pdf is the business card (85 × 55 mm, 3 mm bleed, front and back) with a QR code to https://boudakaci.cz/recenze — the site redirects that to the Google review form, so a printed card survives a change of Google's link. It is rendered from tools/print/vizitka.html with headless Edge (the command is in the file); the HTML embeds its fonts, the mark and the QR code, so it shows the same in any browser or preview; tools/print/qr-recenze.svg is the QR code. Opened in a browser, the HTML shows both sides with the bleed tinted red and the trim line dashed.

print/letak.pdf is the A5 leaflet (148 × 210 mm, 3 mm bleed, one side) for letterboxes and noticeboards, from tools/print/letak.html in the same way; its QR code (tools/print/qr-web.svg) leads to boudakaci.cz. It carries no prices on purpose — they change in the admin, a printed leaflet does not. print/letak-a6.pdf is the same leaflet shortened for A6 (105 × 148 mm, 3 mm bleed), from tools/print/letak-a6.html: service names only and fewer points, so the smallest text stays at 7.5 pt.

print/listek-prochazka.pdf is an A6 note (3 mm bleed) for the letterbox of a house whose tree Tomáš noticed on a walk: ticked boxes for what is visible from the street (dry or hanging branch, fungi, crack, lean…), lines to write which tree, and a plain statement that it is an observation, not an expert assessment. Its QR code opens the contact form with utm_source=prochazka, which JobSource.FromAttribution turns into the source „Lísteček z procházky“ (walk), so the statistics show what the walks bring. Print it on uncoated paper so a pen writes on it.

Round stickers for the printer's template (sheet 64 × 64 mm, safety circle about Ø 60 mm): print/samolepka.pdf has the original logo on white, print/samolepka-tmava.pdf the site's colours — the logo in the cream #f3f1e9 (originals/logo-bouda-kaci-kremova.png) on the dark green (tools/print/samolepka.html, tools/print/samolepka-tmava.html). The background fills the whole sheet and the logo is 54 mm wide, so its widest part (the orange rules) stays 2 mm within the safety circle — the logo keeps its own lettering; the site's fonts are for text. Stickers 60 × 60 mm with a transparent background, to cut along the shape of the logo (or print on clear foil with a white underprint): print/samolepka-pruhledna.pdf has the original logo, which already has a transparent background, for light surfaces; print/samolepka-helma-bila.pdf and print/samolepka-helma-limetka.pdf have a light logo for dark surfaces such as Tomáš's dark green helmet — the dark green turned cream white or the site's lime, the orange kept (originals/logo-bouda-kaci-svetle.png, originals/logo-bouda-kaci-limetka.png, made by tools/logo-recolor; the command is in its Program.cs). print/samolepka-helma-nahled.png compares the three on dark green.

Content still to fill in

The sections #ceny (prices) and #reference (reviews) in index.html have a finished design but placeholder content, and therefore the hidden attribute. tools/check-placeholders.mjs fails the build if one of them is shown while it still contains TODO. Only real reviews may ever go into them or into the structured data — invented reviews break Google's rules.