Redesign Plan & Consistency Audit

2012 Jeep Liberty 4WD V6-3.7L — Service Manual Modernization

Prepared for Marcus · Source: Operation CHARM archive (static HTML) · Companion file: Liberty-Service-Redesign-Mockup.html

This plan turns the archived CHARM manual — a sprawling, ad-injected static site of several thousand pages — into a clean, mobile-first reference you can actually use with greasy hands in the driveway. It covers what the archive is, every consistency problem found, a proposed reorganization (two options, as requested), the new mobile design, and a phased path to roll the redesign across the whole manual.

The decisions you picked: deliver a plan + clickable mockup this round · a mobile-app-style experience · audit + auto-fix the safe mechanical issues · and present both a cleaned version of the original hierarchy and a new task-based structure. This document and the mockup reflect those choices.

1What the archive actually is

The folder is a verbatim scrape of Operation CHARM's manual for this one vehicle. It is a static HTML site — every page is an index.html inside a deeply nested folder — generated from a small set of repeating templates. There is no database, no build system, and no search.

Two parallel hierarchies

The same vehicle is documented twice, under two top-level sections whose category lists don't match:

Repair includes categories that Parts does not (Power & Ground Distribution, Diagrams, Specifications, Technical Service Bulletins, Application & ID, Diagnostic Trouble Codes). A reader looking at a Radiator must mentally stitch together two separate trees to see its procedure, its part number, and its labor time.

Seven page templates

TemplateWhat it holdsExample
Section landingGiant collapsible nested menu (one ~90k-token file)Parts and Labor home
Category / subsystemMenu of childrenCooling System
Component hubLinks to its sub-topicsRadiator
ProcedureNumbered steps + WARNING/CAUTION/NOTE + figuresRadiator – Removal
Parts InformationData table: Part, Mfr, OEM #, Price, NotesRadiator parts
Labor TimesData table: Op, Std hrs, Warranty hrs, Skill, NotesRadiator labor
ImagesDiagram with clickable pixel-positioned hotspotsCooling System images

Scale (estimate): ~17 shared systems, each with multiple subsystems and dozens of components, every component carrying up to four leaf pages (procedures, parts, labor, images). That puts the archive on the order of 2,000–4,000 individual HTML pages. (Exact count pending — the file-count needs the code sandbox, which is offline this session; it does not affect anything below.)

2Consistency audit

Findings are grouped and rated HIGH MED LOW. "Auto-fix" items are mechanical and safe to script during the rebuild; none touch the engineering content itself.

IssueSeverityEvidenceFix
Injected promo / ad box on every content page ("LEMON … manuals through 2025")HIGHIdentical floaty-message block + JS in every page; links point to external sites that resolve to missing-page hereStrip the block and its lemon-* JS. Auto-fix
Dead navigation linksHIGHBreadcrumbs link to /Jeep/ and /Jeep/2012/ (don't exist in a single-vehicle archive); missing-page, .zip and torrent linksRebuild breadcrumbs from the local tree; drop external/dead links. Auto-fix
Multi-level URL-encoding in links + mixed link stylesHIGHDouble/triple encoding (%2520, %252C); some links deep-link with #hash into the mega-menu, others hit a folder index directlyNormalize to clean relative slugs; one consistent link model. Auto-fix
Encoded folder names on diskMEDDirectories literally named Parts%20and%20Labor, Engine%2C%20Cooling…, %2F, %28Slugify folders (e.g. parts-and-labor). Auto-fix
Duplicate / cross-listed componentsHIGHWater Pump & Water Pump Gasket appear under both Cooling System and Engine; "Four Wheel Drive Selector Switch" and "Transfer Case Actuator" each live under 3 paths. The site's own About page admits "multiple pages … may point to the exact same content."One canonical component page + cross-reference links. Auto-fix (with a review pass)
Divergent taxonomies (Repair 25 vs Parts 18)HIGHTwo different category sets for one vehicle; Repair-only categories never appear in PartsUnify to one system taxonomy; attach Repair + Parts + Labor under each component (see §3). Auto-fix
Redundant / garbled categoryMED"A L L Diagnostic Trouble Codes ( DTC )" (letter-spaced) coexists with a normal "Diagnostic Trouble Codes"Merge into one "Diagnostic Trouble Codes (DTC)". Auto-fix
Uneven nesting depthMEDCooling System ▸ Radiator is 4 levels deep; Drive Axles ▸ Axle Shaft Assembly ▸ CV Joint Boot is 6Normalize to System ▸ Subsystem ▸ Component ▸ Topic. Auto-fix
Non-semantic markup / accessibilityMEDHeader cells use <td> not <th>; steps built from &#09; tab hacks + indent-N classes; image hotspots are empty pixel-positioned anchors; no alt, no landmarks, missing lang; /style.css absolute path breaks offlineSemantic HTML5, real <ol>/<th>, labeled responsive hotspots, alt text. Auto-fix
Mobile usability (the core brief)HIGHTiny monospace; fixed footer overlaps content; ad box reflows the page; breadcrumb overflows the screen; pixel hotspots don't scale; no searchMobile-first responsive system + search (see §4). Rebuild
No shared template / weightLOWEvery page re-embeds the full header, breadcrumb, and ad inline; fold state in sessionStorageSingle template + generated pages + one search index. Rebuild

3Reorganizing the hierarchy — two options

As requested, here are both a cleaned version of the existing structure and a new task-based structure. My recommendation is to ship them together as a hybrid: the task-based layer on top, the cleaned system tree underneath, and a unified component page that ends the Repair-vs-Parts split.

Option A — Cleaned system hierarchy

Keep CHARM's engineering categories, but merge the two divergent trees into one, de-duplicate, fix names, and normalize depth.

2012 Jeep Liberty ├─ Engine, Cooling & Exhaust │ ├─ Engine │ ├─ Cooling System │ │ ├─ Radiator ← one page: │ │ │ Procedures · Parts · Labor · Diagram │ │ ├─ Thermostat │ │ └─ Water Pump de-duped │ └─ Exhaust System ├─ Transmission & Drivetrain ├─ Brakes & Traction Control ├─ Steering & Suspension ├─ Starting & Charging ├─ Heating & Air Conditioning ├─ Restraints & Safety ├─ Body & Frame · Lighting · Glass · Wipers ├─ Instrument Panel & Gauges · Cruise ├─ Accessories & Optional Equipment └─ Electrical: Power/Ground, Relays, Modules, Sensors & Switches

~17 unified systems · consistent 4-level depth.

Option B — Task-based structure

Organize around the job you're trying to do. "Repair by System" drops straight into Option A's tree.

2012 Jeep Liberty ├─ 🛢️ Maintenance │ fluids · filters · belts · plugs · schedule ├─ 🩺 Diagnostics │ DTCs · symptoms · TSBs · module locator ├─ 🔧 Repair by System → (Option A tree) ├─ 🔌 Wiring & Diagrams │ power · ground · schematics · connectors ├─ 📐 Specs & Torque │ capacities · fasteners · clearances ├─ 📦 Parts & Labor │ catalog · OEM #s · labor times └─ 🆔 Your Vehicle Application & ID · VIN · RPO

Matches how people approach a repair; best on a phone.

Recommended — the hybrid (what the mockup shows). Task-based top level for discovery, the cleaned system tree for browsing, and a single Component hub per part that unifies what the original site split across two sections:
Overview + specsProceduresParts (OEM #s)Labor timesDiagram
This single move removes the biggest source of duplication and the two-tree confusion at once.

4The redesign — mobile-first design system

The mockup (Liberty-Service-Redesign-Mockup.html) is an interactive prototype of the screens below. Open it in a browser — it's clickable, includes a dark-mode toggle for night/garage use, and pulls in the real Cooling-System diagram and Radiator-removal photos from the archive.

Principles

Screens in the prototype

Home / dashboardLive searchSystem browse (drill-down)Component hub (tabs)Procedure reader

Design tokens

TokenValueUse
Accent#d4691a amberPrimary actions, active state, step numbers
Ink / secondary#16202c / #56627aBody text, metadata
Semanticred / orange / blueWARNING · CAUTION · NOTE callouts
Radius · shadow12–16px · softCards, list rows, tiles
TypeSystem sans stackReplaces the original monospace
ThemeLight + DarkDark mode for low-light work

5Rollout — from prototype to the full manual

The redesign is template-driven, so the whole archive can be regenerated by script rather than edited by hand. Recommended sequence:

1
Parse & extract
Walk every index.html, classify it into one of the 7 templates, and extract clean structured data (component, system path, steps, callouts, tables, image refs, cross-links) into JSON. Output: a single normalized dataset + an inventory report.
2
Clean & de-duplicate
Apply the §2 auto-fixes: strip the ad, drop dead links, decode/slugify names, merge duplicate components, unify the two taxonomies, normalize depth. Produce a diff/changelog for your review before anything is published.
3
Build the component model
Merge each component's Repair + Parts + Labor + Images into one record (the hub). Resolve cross-references to canonical slugs. Generate the search index.
4
Generate the site
Render the mobile design (this prototype's templates) for all systems, components, and procedures. Static output — fast, offline, hostable anywhere, or installable as a PWA for phone use.
5
QA & verify
Automated link-check (zero dead links), template-coverage report, image-resolves check, accessibility pass, and a manual spot-check of a sample from each system. Sign-off before replacing the original.

6Decisions & open questions for you


Companion file: Liberty-Service-Redesign-Mockup.html — open in any browser; best viewed on a phone or in a mobile-sized window. No content was altered in the source archive; both deliverables are new files added alongside it.