RiskPilot Website FR GitHub

Site and documentation roadmap #

This roadmap concerns riskpilot.site, not the functional roadmap of the application. It prioritizes documentary quality, referencing, security and maintainability without promising a date.

Base delivered #

  • canonical permalinks and XML/TXT sitemaps;
  • pre-rendered documentary content in each HTML page;
  • Open Graph, Twitter and Schema.org metadata;
  • local search and navigation by categories;
  • menu mapping verified against the deposit;
  • automatic source checks, canonical and JSON-LD;
  • SRI integrity of CDN libraries;
  • Apache security, cache and compression headers;
  • removal of deployment examples and dead pages.
  • error pages 400/401/403/404/429/500/503 without technical leak;
  • local controls of build, SEO and static security;
  • Structured FAQ, enriched manifest and accessible interactive components.
  • post-deployment control of TLS status, headers and certificate.
  • PNG social card and PWA 192/512 icons checked automatically;
  • Lighthouse budgets and local axis audit on representative pages.
  • RFC 9116 security contact with OpenPGP key and controlled expiration.

Priority 1 — Publication and measurement #

  1. Validate the domain in Google Search Console and Bing Webmaster Tools.
  2. Submit sitemap.xml and monitor crawling, canonical and excluded pages.
  3. Measure Core Web Vitals on mobile and desktop.
  4. Fix broken links and 404 responses before each post.
  5. Periodically check the www redirect and TLS certificate.

Priority 2 — Synchronization with product #

  1. Automatically compare React routes with document mapping.
  2. Detect controllers or pages without associated guide.
  3. Save the audited application commit in each documentary version.
  4. Generate a feature → screen → API → guide → test matrix.
  5. Add a mandatory documentary review to menu changes.

Priority 3 — Reference documentation #

  1. Generate the API reference from a versioned OpenAPI contract.
  2. Add versioned and redacted screenshots.
  3. Document each workflow with prerequisites, roles, statuses and errors.
  4. Publish a user-oriented changelog.
  5. Maintain a matrix of supported Docker versions, browsers and dependencies.

Priority 4 — Security and publication chain #

  1. Add local HTML validation control and external links.
  2. Scan dependencies and periodically check SRI fingerprints.
  3. Reduce CDN dependency by evaluating self-hosting of resources.
  4. Test CSP, HSTS, anti-framing, MIME types and cache policy on real hosting.
  5. Produce an SBOM and sign release artifacts when the channel allows it.

Priority 5 — Performance and accessibility #

  1. Automate Lighthouse and focus on representative pages.
  2. Budget HTML, CSS, JavaScript weight and rendering time.
  3. Optimize the social map and images in suitable formats.
  4. Test keyboard, screen readers, contrast and reduced motion.
  5. Measure documentary research and enrich queries without results.

End criteria #

An evolution is only documentedly complete if the guide, navigation, search engine, permalinks, structured data and automatic controls are consistent with the published code.