How we build the new site

Nine sections, one at a time, with the same nine steps every time. Written down so we can both hold me to it.

The Neuman Group · Prestige rebuild · for Dan to review

You said it plainly: when I build, there are usually a lot of bugs. You are right, and the last section proved it — I shipped four real defects before I caught them. The point of this plan is that every one of those four was found by a check, not by luck, and those checks now run on every section.

1.The nine sections, and the order

Order is not arbitrary. Each one is picked because the section before it settles something the next one needs.

#	Section	When	Why it sits here
1	Listings 17 pages built, live, crawled clean.	Done	Inventory. The thing everybody comes for.
2	Buy & Rent Tree already drawn. Not built.	Next	The biggest audience, and it feeds off Listings, so the two must agree.
3	Sell	After	Sellers are where listings come from. It is the money door.
4	Invest	After	The deepest content on the live site and the messiest — 14 pages that say the same thing four ways.
5	Manage	After	Property management. Small and self-contained.
6	Agents	After	Recruiting. Almost entirely new writing, so it needs you more than the others.
7	Relocate	After	Already a built page. Mostly re-homing it under Buy.
8	Home	Second to last	The front page can only be written once the seven doors behind it are real.
9	House-only	Last	The leftovers bucket. Whatever is still standing after eight passes.

Listings is finished and live now: the door plus seventeen pages under it. Map: prestigen.letaibuildit.com/tree.html

2.The nine steps, every section

Same recipe every time. You are needed at two of the nine steps, and both are short.

3.What has to be true before I call a section done

Not "it looks right". These are checks with an answer, and I show you the answer.

• Every link on the section opens something. Crawled, counted, zero dead.
• No page is wider than a phone screen. Measured, not guessed.
• Nothing is hidden behind the header or under a fold.
• Every number on the page can be traced to a file or a database row.
• No red-versus-green anywhere. Words and shapes carry the meaning.
• Every tool link is a full https:// address, so it cannot 404.
• The page was produced by a script, and the script is committed.
• The live Neuman site is untouched. Checked, not assumed.

If any one of these fails, the section is not done, and I say so rather than quietly moving on.

4.What actually went wrong last time

This is the honest part. Four real defects in the Listings section. All four are now impossible or caught automatically.

What broke	What it was	Why it cannot happen again
The breadcrumb could not be read	It sat at the very top of the page, underneath a header that is pinned there and 125 pixels tall. Seventeen pages, all wrong.	The breadcrumb is now placed below the hero by the script itself, so it cannot happen again on any future section.
Bold words broke onto their own lines	A styling rule meant for a heading was also catching ordinary bold text inside sentences.	Rule narrowed. It now applies to the heading only.
A style change did not appear	Cloudflare was still handing out the old stylesheet. The change was correct and invisible.	The stylesheet version number now gets bumped as part of the build, in all three places that carry it.
The example home was in the wrong county	The sample listing page pulled a real house — from Hendry County, which is nowhere we work.	The query is now fenced to Miami-Dade, Broward and Palm Beach, and to a normal price range.

Two of the four were invisible to the eye. That is the argument for step 6 — measuring the page instead of looking at it.

5.Rules that do not change

6.What could still go wrong

No plan removes risk. It just says who catches what.

Risk	Why it is real	What catches it
A tool on REmined changes or moves	The new pages link out to about forty live tools. If one gets renamed, that link dies quietly.	The crawl is a script. I can re-run it across the whole site any time, and it will name the dead link.
Another session edits the same files	Several of these run in parallel and they have overwritten each other before.	Read the file back after writing, and commit straight away. Both are now in the written rules for this folder.
We disagree about a page after it is built	Building the wrong thing is the expensive failure.	That is what step 3 is for. The tree is approved before anything gets built.
The honest caveats read as weakness	Some pages admit what our data cannot do.	Your call, page by page. I would rather you cut one than find out from a client.

7.What I need from you

Two moments per section. Nothing else.

When	What you do	How long
Step 3	Open the tree, approve the shape of the branch or tell me which box is wrong.	~10 min
Step 8	Open the real pages and tell me what is wrong.	~15 min

Everything between those two is mine.

8.Next move

If you are happy with this plan, the next section is Buy & Rent. Its branch is already drawn — step 2 is done, so it starts at step 3, with you looking at the shape.

Before any of that, I would like to grill you on this plan: a short set of direct questions so we find the places we disagree now, on paper, instead of halfway through section four.