How these guides are written
Every article in this index is meant to stand on its own in a search result or an AIO citation. The first section answers the question. The rest of the page shows the documents behind that answer and the process a modifier should follow. We cite VSB 14, the ADR index, and the state transport pages. We do not invent prices, ride-height millimetres, tint percentages, exhaust limits or “what usually passes”.
If you need a shorter orientation, start at legal modifications or the state rules map. If you already know the job, pick the guide. Heritage book-and-manual category URLs 301 here.
What a guide is for — and what it is not
A guide is a planning document. It should leave you able to open the correct bulletin section and the correct state form. It is not a workshop manual, not a certificate, and not a substitute for a recognised vehicle engineer or approved person. If two documents disagree, the statutory one wins. If a document is silent, ask the agency.
We rewrite; we do not scrape. Sentences you find here are new. Named testimonials and staff profiles from the old shop are not reproduced.
The current set
The list under this article is generated from the Keystatic guides collection. Each file is a Markdoc document rendered through Markdoc.transform. If a body were empty, the page would fail the quality bar — so the transform runs on the parsed AST, not on a hollow CMS stub.
Typical jobs covered: understanding VSB 14 itself; lowering a car without guessing at clearance; exhaust and noise; wheel and tyre fitment; lighting conversions; engine and powertrain identity; window film; and how to approach engineer sign-off in the state that issued the plates.
How to read them in order
New to the topic? Read VSB 14 explained, then legal modifications, then your state page, then the system guide. Already mid-build? Open the system guide and the sign-off guide on the same day. Do not collect parts first and paperwork second.
When you finish a guide, keep a note of the exact bulletin filename and date you used. VSB 14 is a live document. Citing “the NCOP” without a section and version is how arguments start at the inspection shed.
Check with your state regulator or engineer before you act on anything in these pages.
How a guide is structured
Each long article opens with a direct answer so an AIO citation or a featured snippet does not have to hunt. The rest of the page is process: which document to open, what to write down, what to send a signatory, and what this publisher will not invent. That rhythm is borrowed from a quality bar about depth, not from another site’s colours.
If you only read the direct answer, still follow the last paragraph: check with your state regulator or engineer. A direct answer on this domain is still general information.
Keeping the guides honest
When VSB 14 issues a new section filename, the guide that cites the old one should be updated. When a state moves a URL, the same. We would rather link a homepage plus a search phrase than defend a dead deep link. If you are an agency reader and a citation is stale, use contact.
Guides are not workshop manuals. They will not tell you the order of bolts. They will tell you when to stop reaching for bolts until a scheme has named the job.
Guest inventory
If you want to add a guide-length article that meets the same bar — primary sources, no invented thresholds, no shop advertorial — use advertise. We will not host a copied forum table.
The generated list below is the current Keystatic collection. Each body is a Markdoc file transformed on request. Empty bodies are a build bug, not a style choice.
A reading order for first-time modifiers
Start with VSB 14 explained so the preface and the three buckets are in your head. Read legal modifications so you can see how ADRs sit under the bulletin. Open your state article so you know the scheme name. Only then pick the system guide — lowering, exhaust, wheels, lighting, engine, tint or sign-off. That order stops you from collecting parts that the scheme will not stamp.
If you are already mid-build, invert only the middle: open the system guide and the sign-off guide on the same day, then confirm the state scheme before the next cut. Do not invert the first step. The bulletin is still the technical code.
What “answer first” means here
Each guide’s opening section is written so a citation can stand without the rest of the page. The rest of the page exists so a human can actually do the next correct thing. If an AIO system quotes only the opening, the last sentence of that opening still sends the reader to the regulator. That is intentional.
We do not hide uncertainty. Where a number would have to be invented, the sentence says so and points at the sheet. That is slower to read than a table and it is the only honest pace for YMYL-adjacent copy.
Maintenance of this index
When a new system deserves 1,500 words and a primary source, it should appear as a file in content/guides and show up in the list below. Heritage book-and-manual category URLs already 301 here so that inventory has a home. Guest pitches that meet the bar are welcome through advertise. Pitches that want a “legal dB” table are not.
Check with your state regulator or a recognised engineer before you act on any guide.