libre gantt produktová roadmapa jako technický infographic

Tech architecture infographic titled "Libre Gantt Product Roadmap" using HOW-IT-WORKS archetype adapted as a product roadmap horizon layout. Create a blueprint schematic roadmap for the next quarter (next 3 months) with a clear horizontal timeline axis and three horizon sections labeled in English: "Now", "1 Year", "2 Years+". Emphasize the "Now" section with detailed quarter columns for the next 3 months, while "1 Year" and "2 Years+" show smaller forward-looking placeholders. Include swim lanes by team with labeled boxes for realistic Libre Gantt workstreams: "Frontend UI" — "Task views, forms, and interaction polish"; "Scheduling Engine" — "Dates, dependencies, and timeline calculations"; "Import / Export" — "CSV and common file interchange support"; "Collaboration" — "Comments, sharing, and multi-user workflow"; "Platform / DevOps" — "Packaging, builds, and deployment reliability"; "Documentation" — "User guides and onboarding content". Render feature cards or pill-shaped boxes inside the lanes, each with a small icon, feature name, and one-line role description in English. Use realistic feature names only, such as "Task dependency editing" — "Create and update predecessor links"; "Baseline view cleanup" — "Improve schedule comparison clarity"; "CSV import mapping" — "Match incoming columns to fields"; "Print layout fixes" — "Make exported charts fit pages"; "Dark mode contrast pass" — "Improve readability in low light"; "Undo / redo stability" — "Reduce state loss during edits"; "Shared project links" — "Enable read-only project access"; "Docker image refresh" — "Update build and runtime environment"; "Getting started guide" — "Short onboarding for first project setup". Add status indicators on each feature card with sharp English labels: "Planned", "In Progress", "Shipped". Connect related boxes with arrows showing sequencing and dependency direction, with short English arrow labels such as "UI update", "dependency data", "CSV fields", "export output", "release package", "docs update". Include supporting component boxes to keep it in tech-diagram form: "Web App" — "Browser-based project planning interface"; "Project Store" — "Persists tasks, dates, and metadata"; "Export Service" — "Generates printable and file outputs"; "Build Pipeline" — "Validates, packages, and publishes releases"; "Docs Site" — "Hosts guides and release notes". Show arrows between these boxes and roadmap items where technically sensible. Add a numbered legend 1-7 in English walking through the lifecycle of roadmap delivery: 1. "Plan quarter priorities from current user needs" 2. "Assign features to team swim lanes" 3. "Mark current implementation status" 4. "Link dependent work across components" 5. "Deliver tested changes through build pipeline" 6. "Publish shipped features and documentation" 7. "Show longer-horizon ideas separately from current quarter". Visual style: blueprint schematic, minimal monochrome palette, dark navy or charcoal background with white and light gray linework, subtle grid, technical drafting accents, precise strokes, clean spacing, sharp status pills, calm engineering mood. Use 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.