Roof trace component
Selected base direction. Needs refinement, then lock before generating versions.
RoofHero visual system · current working master
This HTML companion mirrors the current MD and is the visual working source of truth for RoofHero brand-system iteration. Keep referencing and iterating on this file instead of creating one-off working files.
00 · Relationship
Roover’s master file is the structural inspiration. RoofHero should use the same discipline, but translate every component into homeowner-facing trust and conversion.
01 · Build map
Blank areas are intentional. Where a RoofHero version does not exist yet, the Roover pattern is included only as inspiration and the task is called out.
Selected base direction. Needs refinement, then lock before generating versions.
Roover inspiration: paper output for job packs, estimates, comparisons, and timelines.
Task: create RoofHero version that makes “we reviewed your roof first” feel tangible.
Roover inspiration: phone journey and amber path line between steps.
Task: create RoofHero version: Address → Roof Review → Clearer Scope → Local Pricing Path.
Roover inspiration: live badge, powered badge, scope-confirmed badge.
Task: create RoofHero evidence chips for ads and site modules.
Roover inspiration: utility line icons with one amber signal.
Task: create RoofHero icons for roof, scope, measurement, address, access, review, pricing path.
Early V1 exists. Next version should be generated from locked graphics, not manually improvised.
02 · Trace family
This section mirrors Roover’s trace workshop idea, but the RoofHero translation is calmer and more homeowner-facing: evidence diagram, not live engine.
Formula: pampas technical grid + soft roof plane + blaze perimeter trace + dark ridge lines + one or two proof chips.
Roover has a mature trace system: hero trace, journey path trace, UI trace, measurement lines, animated dot, and readout cards.
RoofHero task: translate this into static-friendly homeowner proof first, then add restrained motion after the component is locked.
03 · Surfaces
The Roover master has dark blueprint, light blueprint, and paper output. RoofHero needs a similar surface system translated for trust, ads, and homeowner clarity.
Use in Roover for live engine work: scanning, mapping, routing.
RoofHero task: define dark trust/ad surface.
Use in Roover for calmer explanation and technical detail.
RoofHero task: define proof grid surface.
Use in Roover when a job pack, estimate, comparison, or timeline has been produced.
RoofHero task: define Roof Review packet/report surface.
04 · Next tasks
Each item should become a focused component chat, then a locked HTML/SVG template, then generated variants.