EditorialDiagram
Diagrams

Product & Planning

Editorial Gantt Chart Designer — No Shadows, No Mermaid Slop

Read a ten-day example launch schedule with eight tasks across Discovery, Build and Release. A shared date axis makes overlap visible while one launch bar provides focus without adding a tangle of dependency arrows.

Explore the example for free
100%
Example preview
A ten-day launch plan with parallel work.Illustrative January 5–14, 2026 schedule. One day equals 64 pixels; each task has its own 40-pixel row.A ten-day launch plan with parallel work.ILLUSTRATIVE SAMPLE / ENGINEERDISCOVERYBUILDRELEASEJAN 5JAN 7JAN 9JAN 11JAN 13JAN 15Illustrative January 5–14, 2026 schedule. One day equals 64 pixels; each task has its own 40-pixel row.Discovery2dScope review2dPrototype3dAPI implementation3dInterface build3dIntegration2dAcceptance QA2dLaunch1d
Checking geometry…

Take it with you

Free PNG includes an EditorialDiagram watermark.

Thin lines. Considered type. No shadows.

Layout Grammar & Anti-Patterns

Four rules for this diagram

  1. 01

    Keep task names in a separate left column and use one shared left-to-right date axis. Bar width is duration multiplied by the common time pitch.

  2. 02

    Give each task a 40px row with a centered 24px-high bar. Keep dates on the axis or in a tooltip rather than repeating them inside every bar.

  3. 03

    Group tasks into named phase zones. Keep the view to twelve tasks and no more than five parallel tracks within one phase.

  4. 04

    Highlight one key deliverable. Use dependency arrows only when they are essential, and distinguish a fixed example date from a live today marker.

Three mistakes to avoid

  • Equal-width bars for unequal durations imply a schedule that the source does not contain.
  • Dependency-arrow tangles and more than twelve tasks overwhelm the temporal comparison.
  • A live-looking today marker on a fixed illustrative schedule misleads the reader about project status.

Engineer vs. Executive

The two renders use the same illustrative source. Executive mode groups detail deliberately; read the captions before using an overview for a technical review.

Engineer / source detail
A ten-day launch plan with parallel work.Illustrative January 5–14, 2026 schedule. One day equals 64 pixels; each task has its own 40-pixel row.A ten-day launch plan with parallel work.ILLUSTRATIVE SAMPLE / ENGINEERDISCOVERYBUILDRELEASEJAN 5JAN 7JAN 9JAN 11JAN 13JAN 15Illustrative January 5–14, 2026 schedule. One day equals 64 pixels; each task has its own 40-pixel row.Discovery2dScope review2dPrototype3dAPI implementation3dInterface build3dIntegration2dAcceptance QA2dLaunch1d

Eight tasks retain their explicit dates and durations on a shared 64-pixel-per-day axis.

Executive / decision overview
A ten-day launch plan with parallel work.Four phase-level bars preserve the schedule window. Engineer mode shows all eight dated tasks.A ten-day launch plan with parallel work.ILLUSTRATIVE SAMPLE / EXECUTIVEJAN 5JAN 7JAN 9JAN 11JAN 13JAN 15Four phase-level bars preserve the schedule window. Engineer mode shows all eight dated tasks.Discovery3dBuild5dRelease preparation3dLaunch1d

Four phase-level bars preserve the January 5–14 planning window and the launch focal point.

When to use another diagram instead

Swimlane Diagram

Use swimlanes to assign process ownership without implying task durations.

Flowchart

Use a flowchart for conditional execution order rather than dated work.

Architecture Delta Diagram

Use a delta to explain the resulting before/after system change, alongside the implementation schedule.

Questions about this diagram

What dates and duration scale does the example use?

It is a fixed illustrative January 5–14, 2026 plan, not a live project feed. Each calendar day is 64 pixels and every task uses its explicit source start date and duration. The today marker is disabled so the sample cannot imply current project progress.

Do overlapping bars imply a dependency or a critical path?

No. Overlap means the dated work occurs in parallel. The example highlights Launch as the focal deliverable, but it does not calculate a critical path or prove prerequisites. Add explicit source dependencies only when they are part of your real plan.

How does the Executive schedule preserve the project window?

Discovery, Build, Release preparation and Launch become four phase-level bars. Their dates cover the same ten-day window while summarizing the eight individual tasks. Engineer mode is the appropriate view for reviewing the source task starts, durations and parallel tracks.

Worked examples use illustrative data. Edited sources require an AI provider; cached previews are ready immediately.

Cached examples are free. Starter Pack is $9.9 once; Pro Pass is $8.9 per month. Every generation costs 10 credits, including one automatic geometry repair. Pricing