Seldeen.com

Problem

A small legal practice needs very little from a website, and what it needs has to be right. The site has to explain the work plainly without overstating anything. Its contact form also invites strangers to describe legal problems before any attorney-client relationship exists, so the form has to set that expectation and handle what arrives with care. Tracking, plugins, and third-party embeds add risk to a job this small without adding anything a visitor needs.

What it does

Seldeen.com is the public brochure site for William Seldeen, a Los Angeles attorney connected to the lab. It introduces the practice and gives prospective clients a clear way to get in touch.

One long homepage: counseling, approach, and experience, followed by how to get in touch.
Inquiry form: name, email, an optional phone number, and a brief description of up to 3,000 characters, with no attachments. Phone and email sit beside it as alternatives.
Expectations stated up front: the form asks for general information only, warns against sending confidential details, and says an inquiry does not create an attorney-client relationship.
Forgiving errors: a failed submission keeps what the visitor typed and moves focus to what needs fixing.
Notices and privacy: one short page says what the site is, what it collects, and how that information is used.

Why it matters

Most of the care in a site like this is in what it leaves out. Seldeen.com is a working reference for treating a small public website as software: reviewed releases, automated checks, and only the moving parts that earn their place. It also continues the lab’s interest in the everyday work of legal practice, here on the side a prospective client sees.

Current status

Live — publicly available at seldeen.com and accepting inquiries. It is one production site for one practice, shown as a reference build rather than a packaged product.

Approach

The public pages are static HTML generated ahead of time, and only the contact page runs code on the server. The homepage loads only files from its own domain, and a strict content security policy enforces that. There are no analytics, advertising tags, or third-party fonts. The one outside service is Cloudflare Turnstile, on the contact page only, which filters automated submissions.

The form is the only moving part, so it gets most of the attention. Each submission passes field limits, a CSRF check, a honeypot, Turnstile, and a rate limit, then goes out as authenticated email. The application does not store or log the inquiry itself. Configuration and the mail code sit outside the web root, and each release publishes an explicit list of files from an exact, reviewed commit.