Moderne Infografik eines gantt diagramm template als Produkt-Roadmap mit den Bereichen Now, Next und Later, Quarter-Spalten, Team-Swimlanes und verbundenen Feature-Karten. Der dunkle Neon-Look mit klaren Boxen, Status-Labels und Timeline-Achsen vermittelt eine hochwertige SaaS- und Entwicklerblog-Ästhetik.
Re-render this exact infographic with every label, heading and caption translated. We re-use all the original attributes (topic, style, palette, …) and only swap the language. Currently in German.
Tech architecture infographic titled "Gantt Diagram Template" using HOW-IT-WORKS adapted as a product roadmap board: a structured now / next / later layout combined with a three-horizon timeline (1 year / 3 years / 5 years). Show labeled BOXES and feature cards arranged in columns and swim lanes, connected by ARROWS to indicate progression, dependency, and delivery flow. Include quarter columns and a clear timeline axis for near-term planning, then horizon markers for mid-term and long-term strategy. Main composition: three large vertical sections labeled Now, Next, Later. Inside them, place organized feature BOXES for a realistic roadmap of a gantt diagram template product. Add swim lanes by team such as Product, Design, Frontend, Backend, Integrations, and Growth where applicable. Each box must contain: a small generic icon, a canonical English feature name, and a one-line role description in English. Use status pills with sharp readable labels: Planned, In Progress, Shipped. Use arrows between relevant boxes with short English labels describing what moves forward, such as "user feedback", "design specs", "API payload", "timeline settings", "template data", "export file", "release build". Recommended realistic feature boxes: "Basic Gantt Layout — Editable task timeline for project planning", "Quarter Timeline View — Switch roadmap by quarter", "Milestone Markers — Highlight key delivery dates", "Dependency Links — Visual task relationships", "Drag-and-Drop Bars — Adjust schedule directly on canvas", "Team Swim Lanes — Group work by team or owner", "Template Presets — Start from common planning setups", "Progress Tracking — Show completion by task", "CSV Import — Load tasks from spreadsheet data", "PDF Export — Share roadmap snapshots", "Comments Panel — Capture planning notes", "Permission Roles — Control editor access", "Baseline Comparison — Compare planned vs actual dates", "Portfolio View — Roll up multiple project timelines", "Custom Fields — Track extra metadata", "Public Share Link — View-only roadmap access". Keep names realistic and not overpromising. Timeline structure: in the Now section show quarter columns such as Q1, Q2, Q3, Q4 with feature cards spanning across columns like a gantt-style board. In the Next section show a 3-year horizon with grouped initiatives and milestone markers. In the Later section show a 5-year horizon with broader strategic themes and fewer detailed cards. Quarter and horizon labels must be accurate and visually consistent. Use subtle connectors from short-term shipped items to medium-term expansions to long-term platform capabilities. Add a numbered legend (1-7) walking through the request lifecycle in English: 1. Capture roadmap themes and planning goals. 2. Prioritize near-term features into quarter slots. 3. Group medium-term initiatives by team and horizon. 4. Mark delivery status with Planned, In Progress, and Shipped. 5. Connect dependent features across horizons. 6. Publish a clean executive view of the timeline. 7. Update roadmap as delivery data and feedback arrive. Visual style: modern startup, dark mode neon palette, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a dark charcoal or near-black background with neon cyan, electric blue, violet, magenta, and lime accents. High contrast, crisp UI-card styling, glowing edges, sharp status labels, elegant gridlines, precise spacing, polished SaaS product aesthetic, confident and forward-looking mood. Use generic interface icons only, no brand logos. Render as a premium product strategy infographic rather than a marketing poster. 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.
Tell us why this image is inappropriate. A description is required — generic submissions are dismissed. Confirmed reports are resolved within 24 hours.