2027 Raider ICE Data Book
Turning dense engineering spec data into a designed product — searchable, navigable, and printable.
Engineering spec data for the Raider truck lived as raw tables, PDFs, and engineer notes — accurate but unusable. Finding a single value meant hunting through documents. The job was to turn that dense data into something a user can read, search, and print without losing fidelity.
It's the proof point most designers can't show: information design as a deliverable, with the discipline to track content parity against the engineering source so nothing is lost in translation.
Structure the whole subsystem map
20+ section pages cover every subsystem — cab, cab-interior, cab-electrical, chassis-frame, axles-suspension, brakes-steering, drivetrain, engines, transmission, fuel-system, air-system, paint-wheels, instrumentation, standard-equipment, safety, and more. The structure itself is the first design decision.
Build search into the document
A 120KB search-index.json makes the entire spec book searchable across all content — so a user finds a value in seconds instead of scanning pages. Search isn't a feature bolted on; it's how the document is meant to be used.
One source, two outputs
A full-book.html for online reading and a print-all.html for a clean printable PDF — the same content serving screen and paper without a second authoring pass.
The deliverable is a navigable system over engineering data, with parity tracked against the source so the designed version stays trustworthy.
| Artifact | Purpose |
|---|---|
| 20+ subsystem pages | One screen per system, consistently structured |
| search-index.json | Full-text search across the book (120KB) |
| full-book.html | Continuous online reading view |
| print-all.html | Clean printable / PDF output |
| _parity_audit_report | Tracks content parity vs. engineering notes |
Search in action
Type a term and the book filters to matching spec entries instantly — the core interaction that turns a static reference into a tool.
Index / table of contents
A clear entry point into 20+ subsystems — the map that makes a dense reference feel navigable.
Subsystem pages
Engines and instrumentation are the most visually dense; the layout system keeps even the heaviest spec tables legible.
Print output
print-all.html produces a clean, paginated document — the spec book as a physical artifact when a dealer or engineer needs paper.
The arc is the whole story: raw data in, a designed product out.
Hunt through PDFs & notes
Search the index, seconds to answer
Scattered files, no system
20+ consistent subsystem pages
Email a PDF
One source → web + print
A reference that engineers and dealers can actually use — and a clean third proof of capability beyond UI and full-stack: information design.
Subsystem sections
Search index, full-text
Outputs from one source (web + print)
Audited against engineering source
Original wireframes and end-to-end UI/UX in Figma, information architecture, the searchable document system, the web + print output pipeline, and the parity audit against engineering notes.
Fortris.ai Marketing Site
Want something like this?
Start a conversation→