Adams Internal
Medicine

Overview

A healthcare website where the design problem was trust.

Adams Internal Medicine was not a landing page exercise. It was a full practice website for Dr. Stamatina Adams, a board-certified internal medicine physician preparing to open a Dallas-area office in August 2026. The site needed to introduce the physician, explain the practice, support new and existing patients, and give people enough confidence to request an appointment.

The work sat at the intersection of web design, content strategy, healthcare compliance, mobile UX, and plain-language patient communication. A visitor might arrive from Google, a referral, a business card, a hospital conversation, or a family member sharing the link. The site had to make sense in all of those situations.

The result is a static, Netlify-ready website with deep service pages, appointment request flows, patient resources, forms, billing information, accessibility support, metadata, security headers, and a visual system designed around calm clinical credibility.

Brief

The assignment was bigger than announcing a new office.

A new practice website has to do several jobs at once. It has to tell patients whether the practice is accepting them, clarify what services are offered, explain how appointments work, and establish that the physician is qualified without turning the page into a résumé dump.

The opening date also mattered. The booking experience needed to create appointment requests, not pretend the office was already operating. That distinction shaped the language, form states, and confirmation copy across the site.

Content Strategy

The content had to answer patient questions before they became phone calls.

The content strategy followed one simple rule: if a reasonable patient would ask it before booking, the site should try to answer it in plain language. That pushed the project beyond a homepage, about page, and contact form into a broader system of service pages, intake support, FAQs, policies, forms, billing guidance, and health-condition explainers.

The voice needed to feel professional without sounding like a hospital system. It had to explain clinical scope, insurance, billing, refills, communication expectations, and transfer-of-care logistics without overpromising outcomes or making legal language feel hostile.

Information Architecture

The site structure had to support different levels of urgency.

Not every visitor arrives with the same intent. A prospective patient may need to compare physicians. An existing patient may need refill instructions. Someone helping a parent may need forms and address information. A mobile user may need one button: call the office.

Build System

Static architecture kept the site fast, inspectable, and stable.

The site was built as hand-authored HTML, CSS, and JavaScript. That decision kept the project simple to deploy, simple to audit, and less dependent on third-party scripts. For a medical practice, that matters: the website should not be fragile just because a framework, plugin, or analytics tag changes.

Compliance

The legal pages were part of the product, not decoration.

Healthcare websites have a different baseline than ordinary marketing sites. Privacy, accessibility, medical disclaimers, cookie behavior, Texas health-privacy obligations, and appointment language all affect whether the site is safe to publish.

The compliance work also improved the experience. A patient should not need to understand legal acronyms to know what information is collected, how appointments are requested, or where to find the paperwork they need.

Evaluation

The final site was judged from more than one stakeholder angle.

The project was reviewed through 19 lenses, including patient trust, mobile usability, accessibility, security, compliance, search readiness, content depth, physician credibility, and long-term maintainability. That kind of review matters because a technically valid site can still fail if the wrong stakeholder does not trust it.

Mobile Experience

The small-screen version had to handle the most stressful patient moments.

Mobile was not treated as a compressed desktop site. A patient might be checking the address from a car, trying to call from a waiting room, reading service information while comparing providers, or filling out forms from a phone because that is the device they have available.

That meant the mobile experience needed visible hierarchy, readable cards, clear touch targets, practical footer organization, and appointment language that did not hide the office-opening constraint. Small layout choices mattered: where the back button appears, how booking steps collapse, where phone links sit, and whether long policy or billing copy stays readable without creating horizontal scroll.

Takeaways

A medical website is a trust system disguised as a website.

The strongest part of the project is the connection between content depth and practical patient behavior. The site does not depend on one impressive homepage. It earns trust through repeated small answers: what the practice does, what it does not do, how to book, how to prepare, how to contact the office, and what to expect next.

That makes the design problem more interesting than visual polish alone. The interface has to be calm, the content has to be specific, the mobile path has to be obvious, and the legal infrastructure has to be present without overwhelming the person who just wants care.