viewpane.app

About

The product site for ViewPane, built so a visitor can decide in under thirty seconds whether the app earns a spot on their phone. No marketing fluff, no hero video, no autoplay-everything: a clear value prop, technical features written for people who run their own stack, the pricing on the page rather than in a modal, and full setup docs, a press kit, a news feed and a structured bug-report form behind it. We run Frigate at home ourselves, which is where the copy comes from.

Technical Highlights

• Astro 7 static — no SSR, no client framework
• More than twenty pages — landing, full docs, news, press kit, blog with RSS, privacy, terms, report-a-bug, the Android test signup, and their thanks pages
• Real app-icon favicon + theme-color meta — no external font/icon requests
• Zero JS at runtime — every animation is CSS; no Vue/React/Svelte
• No analytics, no telemetry, no third-party SDKs — same posture as the app it markets
• Hardcoded production URLs in astro.config.mjs so social cards and OG meta resolve correctly from any deploy preview

Hosting & Domain

• Netlify static deploy — local-built dist/, uploaded as a draft deploy, checked in a real browser, then published
• Porkbun DNS — ALIAS at apex → apex-loadbalancer.netlify.com, CNAME www → Netlify subdomain
• Auto-issued Let’s Encrypt SSL covering apex + www
• .app TLD HSTS preload — every connection forced to HTTPS at the browser level, no mixed-content fallback possible

Notify list

The “get notified” section is deliberately plain. iOS visitors get Apple’s App Store badge. Android visitors get a “coming soon to Google Play” badge backed by a one-line mailto: to our inbox for the day the listing opens. No ESP, no list-management vendor, no tracking pixel. Same minimal-trust posture the app sells: if the marketing site itself collected emails through a third-party platform, the privacy pitch would be hollow.