New Website Build
A website built from scratch on Laravel 12, Livewire 3, and Tailwind 4 — discovery, design, deployment, tests, runbook. Built to inherit.
<p>This is the greenfield engagement. The buyer is a business that wants its first real website or its first non-template website, built by an engineer who will hand back a codebase that does not need a specialist to maintain. The deliverable is the deployed site, the Pest test suite, the CI pipeline, the schema graph and sitemap generators wired into the build, and the README runbook a second engineer can execute.</p>
<p>The parent — <a href="/services/web-development">Website Creation & Redesign</a> — sets the four-artifact perimeter; this page is the greenfield shape of the work. Redesigns are scoped on the sibling <a href="/services/web-development/redesign-modernization">Website Redesign & Modernization</a> page.</p>
<h2>What "real website" means</h2>
<p>A real website earns traffic by being technically sound, content-rich, fast, accessible, and structured for the search engines and AI crawlers that send the traffic. It does not depend on a plugin marketplace, a template subscription, or a third-party page builder that may be acquired and sunsetted next quarter. The data lives in a real database with real relationships. The pages are generated from that database, not hand-edited in a CMS that loses the formatting on copy-paste.</p>
<h2>Discovery</h2>
<p>One to two weeks. Information architecture — the page types, the URL structure, the navigation hierarchy. Content inventory — what exists, what needs to be written, who is writing it. Design direction — palette, typography, voice, component vocabulary. Performance and accessibility budgets agreed in writing. Search Console verification and AI-bot policy scoped before the first sprint.</p>
<h2>Build</h2>
<p>Laravel 12 with Livewire 3 for any interactive surface, Tailwind 4 for styling, Flux UI where the component vocabulary fits, Pest 4 tests, Pint-enforced style. Authentication via Fortify where the site needs accounts. Sanctum for any API surface. Queues for anything that takes longer than a request cycle. Schema graphs generated from the database. Sitemap regenerated on publish.</p>
<h2>Deploy</h2>
<p>Provisioned hosting (Forge, Vapor, or the buyer's existing platform). CI pipeline that runs Pest and Pint on every push and blocks merges on red. Search Console verification. Post-launch runbook covering deploy, rollback, common operational tasks, and the inevitable "the newsletter signup form is acting weird" Tuesday-morning question.</p>
<h2>What I ship</h2>
<ul>
<li><strong>Discovery deliverables.</strong> Information architecture, content inventory, design direction, budgets, in writing.</li>
<li><strong>The site itself.</strong> Laravel 12 + Livewire 3 + Tailwind 4 build with Pest 4 tests, Pint style, schema graph, sitemap generator.</li>
<li><strong>Authentication and account surface.</strong> Fortify, Sanctum for APIs, role and permission policy.</li>
<li><strong>Deployment.</strong> Provisioned hosting, CI pipeline, Search Console verification, AI-bot policy in robots.txt.</li>
<li><strong>Runbook.</strong> README a second engineer can execute, with deploy, rollback, and common-task procedures.</li>
<li><strong>30-day post-launch support window.</strong> For the questions that surface after the first content-update cycle.</li>
</ul>
<h2>Where it fits</h2>
<h3>First real website</h3>
<p>The business is past the Squarespace-template phase. The brand has matured; the operations have grown; the workflows the site needs to host are beyond what a template will support.</p>
<h3>Replacement for a third-party page builder</h3>
<p>The site is on Webflow, Wix, or a similar builder. The builder works until it does not — the day the buyer needs a workflow the builder does not support, or the day the builder's pricing changes.</p>
<h3>From WordPress, fresh start</h3>
<p>The buyer has been on WordPress for a decade. The plugin debt is unmanageable. Rather than untangle, the buyer wants a fresh build with the existing content migrated and the dead plugins left behind. (If preserving SEO equity is the priority, the sibling <a href="/services/web-development/redesign-modernization">Redesign & Modernization</a> page covers the 301-map shape.)</p>
<h2>How I work</h2>
<p>Discovery delivers the written plan before the first sprint. Implementation runs in two-week sprints with a working demo at the end of each. Pest tests are written alongside features, not bolted on. Pint runs on every commit. The principal carrying the work is described <a href="/about">on the about page</a>; patterns from prior builds live in the <a href="/research">research notes</a>.</p>
<h2>Engagement model</h2>
<p>Discovery runs one to two weeks. Build runs six to twelve weeks depending on scope. Handover includes the deployed site, the test suite, the runbook, and a 30-day post-launch support window. To scope a new website build, <a href="/contact">get in touch</a>.</p>