Clinic website
A site the practice does not have to operate
The practice answers a set of questions once. That answer becomes a config file, and the config becomes a static website under the practice’s own brand — no page builder, no plugin updates, no vendor badge in the footer.
Nothing of ours appears on a page a patient sees. If every clinic site looked like Nitentia we would be selling a template.
Why a config file, and not an editor
The document is the site
Everything that makes one practice different from another — its professionals and their registrations, its services, its hours, its address, its accent colour — is a field in one document. Change the document, rebuild, done. There is no second place where the truth lives.
- A field that is required is required by the schema, not by a checklist.
- The same document drives the site, the structured data and the contact path.
- You can read it. It is not a database export.
Static, because a clinic site has no reason to run a server
Pages are built once and served from a CDN. There is no cold start on the first visit of the morning, nothing to patch on a Sunday, and no idle cost sitting in a bill for a page that had eleven visitors on Tuesday.
What every generated site carries
The people, with their registration
Each professional appears with their name, role and professional registration number. The number is mandatory in the schema — a public dental page without it is a violation in both markets we serve.
A contact path that works on a phone
WhatsApp first, because in Brazil it is not one channel among several — it is the channel. Controls are 44px, because they get tapped standing up.
Structured data, generated from the same config
The practice, its address, its opening hours and its services are emitted as JSON-LD from the document that already describes them, so the markup cannot contradict the page.
Its own brand, not ours
Ground, ink and accent come from the practice’s theme. The design system underneath is shared; the appearance is not.
A page that finishes loading
No third-party fonts, no tag manager, no chat widget loading three more scripts. What arrives is HTML, one stylesheet and the practice’s own images.
An enquiry that goes somewhere
The contact form posts to the patient inbox with its source attached, rather than to an email address nobody reads on a Saturday.
From conversation to live site
1
The interview
Half an hour of questions about the practice. No forms to fill in.
2
The config
We write the document and send it back for correction. You read it in plain language.
3
The check
The CLI refuses the config until it is complete and compliant. This is not a review step; it is a gate.
4
The build
The site is generated and published. Changing it later is changing the document.
About the website
Can I edit the site myself?
Yes — through the clinic portal, which edits the same config the build reads. What you cannot do is remove a field the rules require, because the schema will not accept it.
Does it work on my own domain?
Yes. The site is served under the practice’s domain, with the certificate handled for you.
What about before-and-after photographs?
In Brazil their use in dental advertising is restricted, and the restriction is on the practice, not on us. The generator does not offer a gallery for them, which is a deliberate refusal rather than a missing feature.
How fast is it, really?
It is HTML and one stylesheet from a CDN, with self-hosted subsetted fonts. There is no framework to boot before the text appears.
See a generated site next to the config that made it
The most convincing part of the demo is watching the document and the page be the same thing.