The full path to a business website that holds together — plan the content, structure the site, design the components, write the page copy, then ship it as one coherent whole.
A company website built page by page becomes a patchwork — copy that argues with itself, navigation no one can follow, and a fourth slightly different button. The fix isn't more pages, it's a structure underneath them. This project builds a complete business website as one coherent whole: decide what the site says and why, organize it into an architecture people and crawlers can navigate, design a component system so every page feels like the same product, write the copy that actually converts on the pages that matter, and ship it. It can include landing pages, but it's deliberately broader than a single one — a full business website, not a documentation site and not an SEO page farm — and each stage connects to a NewPrompt workflow you can run on its own. You own the brand, the claims, and the visual design; the project gives the site a spine so it reads as one company instead of five.
Each stage runs a NewPrompt workflow, with a supporting resource and tool. Work them in order — the output of each stage feeds the next.
See the execution map →Plan what the site says and why
Before any page, decide the content: who the site is for, what it needs to say to them, and which pages serve a real business goal. A website without this becomes a sitemap of guesses.
Structure the site
Turn the content plan into an information architecture — the pages, how they group and nest, and the navigation that lets a visitor reach any of them without guessing.
Design the UI components
Break the screens into a reusable component system — the buttons, cards, sections, and layouts every page shares — so the site stays consistent as it grows instead of fragmenting into one-off pages.
Write the page copy
Write the copy that carries the high-stakes pages — the value proposition, the hero, the calls to action — so the homepage and landing pages sell the outcome instead of just describing the company.
Ship the site
Cross from built to live — check release readiness, plan the deploy and a rollback, and decide what to watch — so launch day is deliberate instead of a scramble.
A company website that reads as one coherent product — a content plan tied to goals, a navigable information architecture, a reusable component system, conversion copy on the pages that matter, and the whole thing shipped — instead of a pile of pages that drifted apart as they were added.
No — this is a content and marketing site: plan, structure, design components, write copy, ship. For application logic and APIs, use the API Backend project.
The journey covers UI component structure and page copy with AI, so you can go far without one — but you bring the brand and the final taste.
A planned, structured, written, and shipped company website — its content and information architecture decided deliberately, not improvised.
Prepare your business goals, target audience, and brand voice and claims before you begin. Stage one plans the site's content around those, so vague positioning stalls it. You don't need pages drafted, a designer hired, or a platform picked yet, because structure, components, and copy come in later stages.
Yes, this blueprint works with WordPress, Webflow, or any no-code builder. The content plan, information architecture, component system, and page copy it produces are stack-independent, so they drop into a hosted CMS or custom code alike. You pick the platform and build the pages; the blueprint gives them a shared spine.
A company website MVP should include a home page, one or two core offering pages, and a clear call to action carrying real conversion copy, not lorem ipsum. Run the five stages against just those pages, and structure the information architecture and components so you can add pages later without the site drifting apart.
Decide what to publish and why before you write a word — set the business goals and audience, map needs to topics, brief the priority pieces, then turn it into a content plan you publish against.
Organize a site so people and crawlers find things — inventory the content, group it into a real hierarchy, design the sitemap and navigation, then document the information architecture for the build.
Structure a UI so it stays consistent as it grows — inventory the screens, break them into reusable components, specify the component system and its rules, then review the structure for drift.
Write a landing page that converts, not one that just describes — sharpen the value proposition, draft the hero and benefits, answer objections at the CTA, then A/B the variants to pick the stronger.
Cross the gap between 'tests pass' and 'safe in production' — assess release readiness, plan the deploy and its rollback, and set up the monitoring and launch checks before you ship, not after.
A sequential prompt workflow for content strategy: audience first, then goals, competitor gaps, topic clusters, defensible angles, and a publishing plan with a review loop.
A reference document is only as useful as its addressability. Heavy § labeling turns a nine-section reference into something every answer can point into.
Make AI act as a software engineer — design, implementation, and testing trade-offs — instead of a generic assistant that writes whatever you ask.
Make AI act as a copywriter that sells — clarity over cleverness, benefit-first, one clear action — instead of producing flat, generic marketing text.
SHIP or DO NOT SHIP: twelve checks on failure modes, observability, rollback, and load — the review that happens before the incident.
Turn website goals, audiences, content types, and conversion paths into a sitemap and information-architecture spec: navigation, a page inventory, hierarchy, URLs, user journeys, and an internal-linking plan.
Turn UI requirements and component needs into a design-system spec: a component inventory with states, variants, responsive behavior, accessibility requirements, microcopy rules, and developer handoff notes.
Turn product positioning into above-the-fold hero copy: a headline, subheadline, primary and secondary CTA, a trust cue, an objection-handling line, and three alternative headline angles to test.
Break a big goal into a sequential prompt workflow — each step with an objective, prompt, and expected output.
Build prompts that produce documents in a fixed structure — headings, sections, and tables.
Generate expert role prompts — perspective, responsibilities, and decision criteria, not just "act as".
Rewrite a weak prompt into a stronger one — vague wording fixed, gaps filled, goal unchanged.
Above the fold you get one headline, one line, and one button — and the pull is to spend all three on how good the product is, or on a metric nobody can back. Here is how to write landing page hero copy with AI: an outcome the reader wants, grounded in the facts you actually have.
Practical project ideas you can build from this base project path — each opens in the Project Advisor.
The full path to pages that rank at scale, not penalty bait — map the intents, build the data set, structure it, template the page, then QA before publishing hundreds.
The full path from idea to a shipped SaaS MVP — define and scope the requirements, design the architecture, API, and data model, then build it reviewed, tested, secured, cost-controlled, and deployed.
The full path to docs people can actually navigate — plan the doc set, structure the site, write the guides and the API reference, then ship it as a coherent documentation site.
The full path to a content operation that runs, not a pile of posts — set the editorial strategy, research the topics, build a reusable template, then produce and QA structured pieces on repeat.