Meridian Dental Template: Clinic Site With Patient Portal

Meridian Dental Template: Clinic Site With Patient Portal

Meridian Dental is one of the five multi page website templates in Zugo: a full clinic site with services, dentist profiles, insurance information, opening hours, an appointment request form and a patient portal behind a login. Cloning it into your own project is free and runs no model, so credits start at your first edit.

Here is what the template actually contains, which parts function, and the compliance question anyone building a medical site has to answer before publishing.

What is inside the Meridian Dental template?

The public site covers what a patient looks for, in the order they look for it. A banner announcing new patient availability, a hero with location and parking, a strip of trust points, five service cards, three dentist profiles with credentials and specialties, an insurance section, opening hours, an address block and an appointment request.

The service cards are numbered and each carries a short explanation plus a starting price. That combination is unusual on clinic sites and it is the strongest thing in this template, for reasons the next section covers.

The team section gives each dentist a photo slot, a qualification line, two specialty tags, a years of practice figure and a short personal description. It reads like a practice that wants to be chosen rather than one that merely lists staff.

Behind the portal link sits a login screen and a patient area with an at a glance overview, upcoming appointments, a twelve month treatment history table, a booking form and a documents list with intake forms, estimates and an insurance summary.

Why does the page put prices next to every service?

Because uncertainty about cost is the most common reason a person delays booking, and clinic websites usually answer everything except that. Meridian answers it in the service cards, then repeats it as a fee guide next to the insurance section.

The template also states what the fees mean: they are self pay rates, and insurance may cover most of preventive care. That sentence is doing more work than it looks like. A price without context creates a new worry; a price with context removes one.

When you rebrand this template for another practice, keep the structure even if your prices differ wildly. If you cannot publish figures, publish ranges, or publish what a first visit costs. Replacing the price block with "contact us for pricing" undoes the single best feature of the layout.

What works and what is placeholder?

Worth stating precisely, because a clinic site touches real appointments and real records.

The last row is not optional. The template ships with an invented review count, an invented wait time and a fictional address in Portland. Publishing those as your own claims is both misleading and easy to disprove, and for a healthcare business it is the kind of error that costs trust permanently.

What does the patient portal contain?

More than most people expect from a template, which is why it needs an honest frame. The portal has an overview greeting with an oral health score, a next visit counter, an upcoming appointments panel, a treatment history table listing procedures with provider and status, a booking form with service and time selection, and a documents area.

The booking form works as interface: choosing a service and a slot adds a request to the list and shows a confirmation saying the front desk will confirm within one business day. That flow is the correct model to copy, because it is honest about a human being in the loop rather than pretending a website can guarantee a slot.

Everything shown inside the portal is demo content for one fictional patient. It is a very good illustration of what a portal could be, and it is not a records system. The distance between those two things is the subject of the next section.

Can it handle real patient records?

Not as it stands, and this is where an honest answer matters more than an encouraging one.

Storing real patient health information carries legal obligations that vary by country, and in the United States that means HIPAA. Those obligations are about contracts, access controls, audit logging, breach procedures and vendor agreements, not about whether a page renders. No website builder, Zugo included, makes you compliant by generating a login screen.

The practical advice is straightforward. Use this template for the public site, which is where most of the value is anyway, and treat the portal as a demonstration or as a place for non sensitive things like forms to download and appointment requests. If you genuinely need clinical records online, that belongs in dedicated practice management software, or in a project reviewed by someone who does compliance for a living.

That boundary is not a Zugo limitation so much as a healthcare reality, but it is the one thing on this page nobody should discover after launch.

How do you turn Meridian into your own practice site?

You describe changes in chat and the site rebuilds. Five edits carry most of the way:

1. Practice and location: "rename to Riverbend Family Dental, move everything to Austin, update the address, hours and phone".
2. Services: "replace the five services with pediatric care, orthodontics, implants and emergency visits, with our prices".
3. Team: "three dentists and two hygienists, use these names, qualifications and biographies".
4. Insurance: "replace the insurer list with the plans we accept and remove the care plan block".
5. Tone: "warmer palette, larger type throughout, and rewrite the copy for anxious first time patients".

One change at a time, checking between each. Every rebuild is verified in a sandbox before it reaches you, so a build that fails to open is never delivered. For a broader walkthrough of this kind of site, how to build a dental clinic site with AI starts from a blank prompt instead of a template.

What does reshaping Meridian cost?

Cloning calls no model, so copying the site into your own project costs nothing.

The Free plan gives 5 credits, enough for the clone and one edit. Pro is $25 a month for 200 credits, Business is $99 a month for 800. On Pro that is roughly 66 edits, or about 16 multi page platforms in a month.

A full rebrand of a clinic site usually takes six to ten edits, because services, team, insurance and hours each need their own pass and each contains details only you know. That is still a fraction of one plan.

Who is this template right for?

Any small practice where patients choose the provider rather than being assigned one. Dentists obviously, but the structure transfers cleanly to physiotherapy, optometry, veterinary care, dermatology, chiropractic and most private clinics: services with prices, practitioners with credentials, insurance clarity, hours and a way to request a visit.

It fits a single practitioner just as well, with the team section reduced to one profile and more room for the personal story. It fits a hospital or a multi location group badly, because that needs location routing, department structure and far more navigation than five sections. A general version of the question is covered in how to build a medical practice site with AI.

What are the honest limits?

Three beyond the compliance point already made.

Requests are not a calendar. The form collects a preference and hands it to a human, which is the right model, but it is not integrated scheduling with real availability. Connecting to a live calendar system is a project, and how to build a booking site with AI covers what that involves.

Nothing sends itself until email is connected. Zugo integrates Resend for transactional mail, and until that is wired an appointment request sits in the interface rather than arriving in an inbox where someone will see it.

And very specific operational logic gets built through iteration rather than one prompt: insurance eligibility rules, recall reminders, multi practitioner availability. Zugo does not replace a development team on that class of work, and on a clinic site it very rarely needs to.

How do you publish it?

Publishing puts the site on an address like your-project.zugo.run in one action, and the build is checked in a sandbox first, so a site that does not render is not published quietly. A simple build takes about a minute; a multi page platform takes a few minutes.

A custom domain connects on paid plans, and for a clinic that is not cosmetic: patients treat the address as a credibility signal. Google Analytics will show whether people reach the booking section, which is the only conversion this site has. GitHub export hands over the source as a real repository, and Vercel deploys to your own account.

Where should you start?

Open the gallery, filter to websites, and compare Meridian with Noire, Forno, Northbound and River Park. They differ in structure rather than styling, and the closest structure saves the most edits.

Then make your first edit the practice details: name, address, hours, phone. Those are the facts a patient checks first, and once they are correct the rest of the site has something true to sit on. Prices and team profiles come second, palette last.

You can clone Meridian and start reshaping it at zugo.dev. The starting credits are enough to see your own practice name and services in place, with no card required.