Libre gantt produktová roadmapa jako tech infografika

Tech architecture infographic titled "Libre Gantt Product Roadmap" using HOW-IT-WORKS archetype adapted as a roadmap dashboard: a dark dashboard product-planning board for Libre Gantt across an 18-month horizon, organized into clear quarter columns on a horizontal timeline axis and grouped into horizon bands: Now, 1 Year, 2 Year+. Show swim lanes by team where applicable: Core App, Scheduling Engine, Import/Export, Collaboration, UX/UI, Infrastructure. Render labeled BOXES as feature cards and milestone modules connected by subtle ARROWS to show dependency and delivery flow direction from left to right. Each box must include an icon, a feature name in English, and a one-line role description in English. Use realistic, non-hyped feature names such as: Task Dependencies, Baseline Tracking, Critical Path View, CSV Import, PDF Export, Theme Customization, Resource Assignment, Keyboard Shortcuts, Undo History, Print Layout, Multi-language UI, Project Templates, Progress Roll-up, Read-only Share Link, Performance Optimization, Plugin API Research, Offline Draft Support, Accessibility Improvements. Add compact status pills on each card with sharp readable labels: Planned, In Progress, Shipped. Include quarter headers accurately spaced for an 18-month span, for example Q3 2026, Q4 2026, Q1 2027, Q2 2027, Q3 2027, Q4 2027, with horizon separators matching Now / 1 Year / 2 Year+. Use ARROWS between related cards labeled in English with dependency text such as "depends on data model", "enables export", "uses scheduling engine", "requires UI refactor", "feeds progress metrics". Add supporting system-style boxes around the roadmap board to make it a proper tech infographic: Product Vision, User Feedback, Engineering Backlog, Release Planning, QA Validation, Stable Release. Each supporting box has an icon, canonical English name, and one-line role description. Connect them with arrows labeled "feature request", "prioritized items", "release candidate", "bug fixes", "shipped update". Add a numbered legend 1-7 in English walking through the delivery lifecycle: 1. Collect user feedback, 2. Prioritize backlog, 3. Plan by quarter, 4. Develop features, 5. Validate in QA, 6. Ship stable release, 7. Measure adoption and feed roadmap. Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Dark dashboard UI background, soft pastel palette accents, muted navy/charcoal canvas, pastel cyan, lavender, mint, peach, and soft yellow for cards and status indicators, crisp grid, subtle glows, precise alignment, product-management infographic mood, polished but realistic. Include timeline ticks, quarter separators, horizon labels, team swim-lane dividers, compact metrics chips such as "scope", "priority", "target quarter" in English. Avoid overpromising, keep feature scope believable for an open-source Gantt product. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks Status labels rendered sharp. Realistic feature names — no overpromising. Quarter / horizon labels accurate.