# Current-site audit

## Inventory

- Public sitemap: 20 routes spanning seven primary pages, one restore case study, one state summary, eight generated home-lab records, one Microsoft 365 proof map, and one RCA record.
- Supporting public routes: operations proof, evidence-library index, compatibility evidence index, resume PDF, screenshots, Markdown, CSV, JSON, and DOCX artifacts.
- Shared assets: circular JF logo, profile illustration, restore screenshots, social preview, global CSS, page CSS, and progressive JavaScript.

## Baseline findings

- Strong content density and evidence depth, but the repeated neon hero/card treatment made pages feel like one template with different copy.
- Projects and Proof delayed useful content below oversized introductions; action hierarchy was inconsistent.
- Evidence strength was difficult to scan because claims, methods, results, and limitations did not share a consistent structure.
- The Dashboard emphasized presentation more than source-derived coverage and integrity measurements.
- Generated evidence pages retained stable source links, but their wrapper language overemphasized source authority rather than artifact contents.
- The prior social preview used a starfield/cyber aesthetic and outdated cloud-first positioning.
- Lazy-loaded images briefly reported zero natural width before entering the viewport; direct requests confirmed the inspected assets returned successfully.

## Risks addressed

- Removed recency as a proof signal while preserving real dated repository paths.
- Preserved resume chronology under the policy exception.
- Kept unsupported and inconclusive outcomes visible.
- Retained static hosting, stable URLs, progressive enhancement, and generator-controlled evidence pages.