libre gantt produktová roadmap infografika na 2 roky

Tech architecture infographic titled "Libre Gantt Product Roadmap" using HOW-IT-WORKS archetype, adapted as a kanban-style roadmap board for a two-year planning horizon. Create a structured product-planning infographic with labeled BOXES and ARROWS, rendered as a clean editorial roadmap system: three primary vertical board sections named Now, Next, Done, combined with quarter-based timeline columns spanning 2 years: Q1, Q2, Q3, Q4, Year 2 Q1, Year 2 Q2, Year 2 Q3, Year 2 Q4. Add horizontal swim lanes by team where applicable: Product, Core Scheduling, Collaboration, Integrations, UI/UX, Infrastructure. Each feature appears as a card or pill with a status indicator badge: Planned, In Progress, Shipped. Use realistic Libre Gantt feature names only, no hype: Task Dependencies, Baseline Comparison, Milestone View, Resource Allocation, Critical Path Improvements, CSV Import, PDF Export, Calendar Sync, Role Permissions, Drag-and-Drop Timeline Editing, Undo History, Performance Optimization, Accessibility Audit, Localization Support, Kanban-Gantt Linking, Recurring Tasks, Comment Threads, Public Read-Only Share Links, Dark Mode Polish, Plugin API Research. Each card is a labeled BOX with a small icon, canonical English name, and one-line role description in English, for example: "Task Dependencies — Link tasks with finish-to-start scheduling rules". Connect related boxes with ARROWS to show delivery flow and dependency direction across horizons, with short English arrow labels such as "depends on", "feeds release", "UX prerequisite", "backend support", "shipped in quarter". Include supporting system-style boxes for roadmap context: Backlog, Active Development, QA Review, Release, Customer Feedback, each with icon, name, and one-line English role description, connected by arrows indicating lifecycle flow. Add a numbered legend 1-7 in English explaining the planning lifecycle: 1. Ideas enter Backlog, 2. Priorities move to Now, 3. Teams build In Progress items, 4. Dependencies unlock later work, 5. QA validates release readiness, 6. Features move to Done after shipment, 7. Feedback informs the next quarter. Quarter labels and horizon markers must be accurate and clearly aligned to the two-year span. Status labels should render sharp and readable. Visual style: warm boutique, refined and slightly premium developer-blog editorial feel, navy base with warm accent palette such as terracotta, amber, muted coral, sand, and soft cream highlights, subtle paper texture, soft shadows, balanced whitespace, elegant flat or light-isometric tech-diagram composition. Include timeline axis, swim lane separators, tidy vector icons, crisp card hierarchy, and a realistic product strategy mood. editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. 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.