Epic: Visualize library support schedules and PHP compatibility #125

Context

Readers need to compare planned library releases and support periods. PHP's Supported Versions page is the presentation reference, adapted to LongitudeOne's site colors and without relative durations.

Objective

Enable readers of every library roadmap to understand release schedules, support periods, and PHP compatibility through a consistent timeline and table.

Scope

All roadmap pages in longitude-one/spatial-docs, including libraries without a stable release.

• Show future releases, active support, and security-fixes-only periods.
• Generate standalone SVG timelines with Node.js during the site build.
• Provide a PHP.net-style table enriched with PHP compatibility, using absolute dates only.
• Use the site's colors and support its light and dark themes.
• Maintain one JSON configuration per library, shared by the timeline and table.
• Define one site-wide time window for all timelines.
• Use explicit support dates and null for unannounced information.
• Make each library roadmap its library-level index.md, replacing the previous landing page.
• Display a default message when roadmap configuration is missing or unpopulated.
• Link table branches to their documented version landing pages when available.

No MDX component is introduced. This Epic does not define a new support policy or invent dates. PHP's own support durations are not implicitly applied to LongitudeOne libraries.

Stories

• Story: Generate SVG support timelines with Node.js #126 Generate SVG support timelines with Node.js.

• Story: Integrate support timelines and tables into every library roadmap #127 Integrate support timelines and tables into every library roadmap.

• Story: Make roadmaps the library landing pages and link documented versions #131 Make roadmaps the library landing pages and link documented versions.

Completion Criteria

• All contributing Stories are completed.
• Every roadmap in scope consistently presents release schedules, support periods, and PHP compatibility.
• No unresolved work required by this scope remains.