What an HTML and CSS redesign includes

Layouts, email, and a live deploy — the difference between a design file and a site that actually ships.

A redesign that stops in a design file is a picture of a website. The useful version is the picture, the HTML and CSS, and a deploy onto the hosting you already have.

What an HTML and CSS redesign includes

What gets designed

The pass covers the pages people use: home, a service or product template, and the content patterns that repeat. Type, color, and spacing come from the brand, or they become the brand if one does not exist yet. The point is a system, not a single hero.

Email belongs in the same system when the campaign has to look like the site. A template built in HTML survives more inboxes than a screenshot pasted into a mail tool.

What gets built

Approved pages are written as HTML and CSS, checked in a browser, and put on your host. You get the files. A redesign that only exists inside one person’s Figma account is not finished.

Interactive pieces — a filter, a form, a small bit of JavaScript — are scoped as part of the page, not as a surprise app.

How to brief it

Name the site that is failing, the pages that matter, and whether email or print has to match. That is the scope. A fixed rate fits when the page list is closed. A subscription fits when the redesign is the start of a longer list.

The service is UX/UI and HTML. Start the conversation on contact if you already know which pages have to change.