OpenGantt

approvedunreviewed

by jebby

Create interactive Gantt charts from YAML in your notes.

↓ 32 downloadsUpdated 3d agoUnlicense

OpenGantt logo OpenGantt

Website Obsidian Plugin GitHub Release Build License GitHub Stars

A lightweight, YAML-driven Gantt chart for the browser, Obsidian, and desktop.

🌐 OpenGantt Website Β· πŸ“ Obsidian Plugin Β· πŸ“¦ GitHub Releases

OpenGantt turns a small YAML definition into an interactive Gantt chart with planned work, actual work, live progress, hierarchical tasks, custom columns, printing, and export.

It can be used in three ways:

  • 🌐 Standalone web app β€” use OpenGantt directly in your browser or as a self-contained HTML application.
  • πŸ“ Obsidian plugin β€” embed Gantt charts directly inside Markdown notes.
  • πŸ–₯️ Desktop application β€” package the same frontend as a native Tauri application.

The chart data remains plain YAML, making it easy to read, edit, search, diff, back up, and keep alongside the project it describes.


✨ Features

πŸ“… Gantt charts

  • Planned and actual task bars
  • Live progress for open tasks
  • Day, week, month, and year scales
  • Today indicator
  • Task hierarchy with expandable/collapsible rows
  • Milestones
  • Planned vs. actual comparison
  • Actual bars with optional diagonal hatching
  • Automatic progress calculation
  • Task status and schedule variance

πŸ“Š Customisable task table

The table alongside the timeline can display:

  • Task name
  • Progress
  • Planned start/end dates
  • Actual start/end dates
  • Planned duration
  • Actual duration
  • Schedule variance
  • Status
  • Notes
  • Custom YAML fields

Columns can be reordered, hidden, or added from the chart interface.

Any additional property placed on a task automatically becomes available as a custom column.

πŸ“ YAML-driven

Charts are defined using simple YAML:

scale: week
mode: both
title: Example project

rows:
  - label: Stage 1 - Planning
    plan: [2026-09-07, 2026-09-12]
    fact: [2026-09-07, 2026-09-14]

    children:
      - label: Collect requirements
        plan: [2026-09-07, 2026-09-09]
        fact: [2026-09-07, 2026-09-10]

      - label: Write specification
        plan: [2026-09-10, 2026-09-12]
        fact: [2026-09-11, 2026-09-14]

  - label: Stage 2 - Development
    plan: [2026-09-15, 2026-10-10]
    fact: [2026-09-15]

Because the chart is represented as text, it works particularly well with Git, Markdown, Obsidian, and other text-based workflows.


πŸš€ Quick start

🌐 Web version

Open OpenGantt in your browser β†’

The web version runs directly in your browser with no installation required.

It provides:

  • YAML editing
  • Open
  • Save
  • Save As
  • Obsidian block copying
  • Example chart
  • Printing
  • PNG export
  • SVG export
  • CSV export
  • Timeline scaling
  • Plan / Actual / Both modes
  • Table and column controls

The repository also contains a self-contained standalone application:

dist/Gantt.html

Simply open it in a modern browser.

No server is required and the standalone build does not need an internet connection.

πŸ“ Obsidian

OpenGantt is available through the Obsidian Community Plugins.

Install it from:

Settings β†’ Community plugins β†’ Browse β†’ OpenGantt

Alternatively, you can build and install the plugin manually using the development instructions below.

πŸ–₯️ Desktop

OpenGantt can also be packaged as a native desktop application using Tauri 2.

See Building the desktop application for instructions.

Keyboard shortcuts

ShortcutAction
Ctrl / Cmd + OOpen
Ctrl / Cmd + SSave
Ctrl / Cmd + Shift + SSave As
Ctrl / Cmd + PPrint

πŸ“¦ Installation

Requirements

For using the web application

No installation is required.

Open:

https://jebbycodes.github.io/OpenGantt/

in a modern browser.

Alternatively, download or clone the repository and open:

dist/Gantt.html

For using the Obsidian plugin

Install OpenGantt from the Obsidian Community Plugins.

No additional dependencies are required for normal plugin use.

For development

The JavaScript build system requires:

The Obsidian plugin build uses esbuild.

For building the desktop application

The desktop version uses:

  • Node.js
  • npm
  • Rust
  • Cargo
  • Tauri 2

The Rust project specifies a minimum Rust version of 1.77.2.


πŸ› οΈ Development setup

Clone the repository:

git clone https://github.com/JebbyCodes/OpenGantt.git
cd OpenGantt

Install the JavaScript dependencies:

npm install

The dependencies and available npm scripts are defined in package.json.


🧱 Building

OpenGantt has separate build processes for the standalone application and the Obsidian plugin.

Standalone application

Build the browser version with:

npm run build:app

This runs build-app.mjs.

The build produces:

dist/
β”œβ”€β”€ Gantt.html
└── index.html

Gantt.html is the standalone application intended to be opened directly.

index.html contains the same generated application and serves as the frontend entry point used by Tauri.

Offline operation

The standalone application bundles its required JavaScript, CSS, and js-yaml dependency into the generated HTML.

Nothing needs to be downloaded when the generated file is opened.


Obsidian plugin

Build the Obsidian plugin with:

npm run build

The build produces:

main.js
styles.css

manifest.json is already present in the repository and is copied alongside those files when the optional vault path is supplied.

The build script bundles the plugin while leaving Obsidian, Electron, CodeMirror, and Lezer packages external because they are provided by the Obsidian host application.

Automatically install into an Obsidian vault

Pass the path to your Obsidian vault:

npm run build -- "/path/to/your/vault"

For example, on Windows:

npm run build -- "C:\Users\YourName\Documents\Obsidian Vaults\My Vault"

The build script installs the plugin into:

<vault>/.obsidian/plugins/gantt/

The resulting directory contains:

<vault>/.obsidian/plugins/gantt/
β”œβ”€β”€ main.js
β”œβ”€β”€ manifest.json
└── styles.css

The repository also contains a Windows helper:

BUILD-AND-INSTALL.bat

which can be used to automate the installation process where available.

Manual installation

If you build without specifying a vault:

npm run build

copy:

main.js
manifest.json
styles.css

to:

<vault>/.obsidian/plugins/gantt/

Then open Obsidian and go to:

Settings β†’ Community plugins β†’ enable OpenGantt


πŸ–₯️ Building the desktop application

OpenGantt uses Tauri 2 for its desktop shell.

The Tauri configuration specifies:

  • Application name: OpenGantt
  • Version: 1.2.0
  • Frontend directory: dist/
  • Frontend build command: npm run build:app

After installing the required Rust/Tauri tooling, build the desktop application with:

npx tauri build

Tauri will first run:

npm run build:app

and then package the generated dist/ frontend into the native application.

For development with the Tauri shell:

npx tauri dev

The exact native output location depends on the platform and Tauri's build configuration.


πŸ§ͺ Testing

Run the project's test suite with:

npm test

The test command currently runs tests covering:

  • Model behaviour
  • Timeline calculations
  • Table columns
  • Export functionality

The individual test files are:

test/model.test.mjs
test/timeline.test.mjs
test/columns.test.mjs
test/export.test.mjs

The available test command is defined directly in package.json.


πŸ“ YAML reference

Top-level options

The following options can be placed alongside rows:

OptionValuesDefaultDescription
scaleday, week, month, yeardayTimeline scale
modeplan, actual, bothbothWhich bars to display
height200–1600520Chart height in pixels
padding0–3657Empty days around the chart
hatchtrue, falsetrueDiagonal hatching on actual bars
progresstrue, falsetrueShow progress for open actuals
collapsedtrue, falsefalseStart with parent rows collapsed
columnsColumn namesSaved layoutSelect and order table columns
tabletrue, false, hiddenSaved layoutShow or hide the task table
titleTextFile nameTitle used for print/export

Example

scale: month
mode: both
height: 700
padding: 14
hatch: true
progress: true
collapsed: false
title: EPQ Project

rows:
  - label: Research
    plan: [2026-09-07, 2026-10-10]
    fact: [2026-09-07]

Task properties

Each task can contain:

PropertyDescription
labelTask name
planPlanned start/end dates
factActual start/end dates
childrenNested tasks
notesAdditional information

Additional properties become custom table columns.

For example:

rows:
  - label: Write literature review
    plan: [2026-10-01, 2026-10-14]
    fact: [2026-10-02, 2026-10-17]
    owner: Alex
    priority: High

This automatically makes owner and priority available as table columns.


Planned dates

A normal planned task uses two dates:

plan: [2026-10-01, 2026-10-14]

A single planned date creates a milestone:

plan: [2026-10-14]

Actual dates

A completed or ongoing task can have an actual start and end:

fact: [2026-10-02, 2026-10-17]

An open task can contain only its actual start:

fact: [2026-10-02]

Open actual tasks extend to the current date and can display their calculated progress.


Hierarchical tasks

Use children to create nested tasks:

rows:
  - label: Stage 1 - Research
    plan: [2026-09-07, 2026-10-01]

    children:
      - label: Find sources
        plan: [2026-09-07, 2026-09-14]

      - label: Evaluate sources
        plan: [2026-09-15, 2026-09-21]

      - label: Write notes
        plan: [2026-09-22, 2026-10-01]

Parent rows can be expanded or collapsed using the chart controls.


πŸ“Š Table columns

The chart includes several built-in columns.

ColumnYAML nameDescription
ProgressprogressPercentage of planned time elapsed
Start plannedplanStartPlanned start date
End plannedplanEndPlanned end date
Start actualactualStartActual start date
End actualactualEndActual end date
Planned daysplanDaysPlanned duration
Actual daysactualDaysActual duration
VariancevarianceDifference from planned completion
StatusstatusCurrent task status
NotesnotesTask notes

For example:

columns:
  - progress
  - planEnd
  - actualEnd
  - variance
  - status

You can also use:

columns: none

to hide the table columns.


πŸ’Ύ Saving and file formats

OpenGantt can work with several file types.

InputSave behaviour
.mdReplaces only the selected Gantt block
.yaml / .ymlSaves YAML
.txtSaves YAML using the same extension
Other text filesSaves YAML using the original extension

When editing a Markdown note containing a Gantt block, OpenGantt preserves the rest of the note.

This includes:

  • Frontmatter
  • Headings
  • Other Markdown content
  • Other code blocks
  • Content after the Gantt chart

If a Markdown note does not contain a Gantt block, OpenGantt can add one without replacing the rest of the document.


πŸ–¨οΈ Print and export

OpenGantt supports printing and several export formats.

Print

The print renderer:

  • Prints the complete chart rather than only the visible portion
  • Includes expanded rows
  • Includes the selected columns
  • Supports the current chart scale and mode
  • Uses a light print-friendly colour scheme
  • Splits long charts across pages
  • Repeats the heading on subsequent pages
  • Avoids cutting rows between pages
  • Numbers pages

You can use your browser's Save as PDF option to create a PDF.

Export formats

The export panel supports:

  • PNG β€” raster image
  • SVG β€” editable vector image
  • CSV β€” spreadsheet-compatible task data

CSV exports include every task, including tasks hidden by collapsed parent rows.


πŸ“ Obsidian usage

OpenGantt can render charts directly inside Obsidian Markdown notes.

Install OpenGantt from the Obsidian Community Plugins, then add a gantt code block:

```gantt
scale: week
mode: both

rows:
  - label: Stage 1 - Planning
    plan: [2026-09-07, 2026-09-12]
    fact: [2026-09-07, 2026-09-14]

    children:
      - label: Research
        plan: [2026-09-07, 2026-09-09]

      - label: Planning
        plan: [2026-09-10, 2026-09-12]
```

The YAML is visible while editing the Markdown source and is rendered as a chart in Reading View.

Alternative code-block name

If another Obsidian plugin already uses the gantt code-block name, OpenGantt can use:

```epq-gantt
rows:
  - label: Example
    plan: [2026-09-07, 2026-09-12]
```

πŸŽ›οΈ Obsidian controls

The Obsidian chart toolbar provides:

  • Day / Week / Month / Year
  • Plan / Actual / Both
  • Expand all
  • Collapse all
  • Table
  • Columns
  • Legend
  • Print
  • Export
  • Full screen
  • Reset

The chart uses its own dark Gruvbox-inspired colours regardless of the active Obsidian theme.

Full-screen mode uses browser fullscreen where supported. On environments where browser fullscreen is unavailable, OpenGantt expands within the available Obsidian window.


πŸ—οΈ Project structure

OpenGantt/
β”‚
β”œβ”€β”€ app/
β”‚   β”œβ”€β”€ app.css
β”‚   β”œβ”€β”€ shell.js
β”‚   └── shim.js
β”‚
β”œβ”€β”€ dist/
β”‚   β”œβ”€β”€ Gantt.html
β”‚   └── index.html
β”‚
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ model.js
β”‚   β”œβ”€β”€ timeline.js
β”‚   β”œβ”€β”€ columns.js
β”‚   β”œβ”€β”€ chart.js
β”‚   β”œβ”€β”€ export.js
β”‚   β”œβ”€β”€ main.js
β”‚   └── styles.css
β”‚
β”œβ”€β”€ src-tauri/
β”‚   β”œβ”€β”€ Cargo.toml
β”‚   β”œβ”€β”€ tauri.conf.json
β”‚   └── ...
β”‚
β”œβ”€β”€ test/
β”‚   β”œβ”€β”€ model.test.mjs
β”‚   β”œβ”€β”€ timeline.test.mjs
β”‚   β”œβ”€β”€ columns.test.mjs
β”‚   └── export.test.mjs
β”‚
β”œβ”€β”€ vendor/
β”‚   └── js-yaml.min.js
β”‚
β”œβ”€β”€ build-app.mjs
β”œβ”€β”€ esbuild.mjs
β”œβ”€β”€ package.json
β”œβ”€β”€ package-lock.json
β”œβ”€β”€ manifest.json
β”œβ”€β”€ main.js
β”œβ”€β”€ styles.css
β”œβ”€β”€ LICENSE
└── README.md

Important directories

PathPurpose
app/Standalone application's editor and browser shell
src/Core Gantt chart implementation
src-tauri/Tauri desktop application
test/Automated tests
vendor/Local third-party browser dependencies
dist/Generated standalone/Tauri frontend

Important build files

FilePurpose
build-app.mjsBuilds the standalone HTML application
esbuild.mjsBuilds the Obsidian plugin
package.jsonDefines dependencies and npm scripts
src-tauri/tauri.conf.jsonConfigures the Tauri application
src-tauri/Cargo.tomlDefines the Rust/Tauri package

πŸ”§ Available npm commands

CommandPurpose
npm installInstall development dependencies
npm run buildBuild the Obsidian plugin
npm run build:appBuild the standalone HTML application
npm testRun the automated tests

🧩 Architecture

OpenGantt uses a shared chart implementation across its different interfaces.

                    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                    β”‚      YAML data      β”‚
                    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β”‚
                               β–Ό
                    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                    β”‚   OpenGantt model   β”‚
                    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β”‚
                 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                 β”‚             β”‚             β”‚
                 β–Ό             β–Ό             β–Ό
             Browser        Obsidian       Tauri
             frontend        plugin        desktop
                 β”‚             β”‚             β”‚
                 β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β–Ό
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚ Gantt renderer   β”‚
                     β”‚ Timeline + table β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

The standalone builder embeds the application's JavaScript, CSS, and YAML parser into a single HTML file. The Tauri configuration then uses the generated dist/ directory as its frontend.


πŸ”— ts-gantt

OpenGantt is based on the ts-gantt project.

ts-gantt provides the underlying Gantt-chart concepts and rendering foundation, while OpenGantt adds its own:

  • YAML-driven format
  • Planned/actual/progress workflow
  • Gruvbox-inspired interface
  • Custom table columns
  • Tooltip system
  • Print renderer
  • Export system
  • Standalone application
  • Obsidian integration

The underlying ts-gantt project is MIT licensed. OpenGantt itself is released under the Unlicense.


🀝 Contributing

Contributions, bug reports, improvements, and feature ideas are welcome.

Before submitting a change:

  1. Fork the repository.

  2. Create a branch for your change.

  3. Install dependencies with npm install.

  4. Make your changes.

  5. Run the test suite:

    npm test
    
  6. Test the relevant build:

    npm run build
    

    or:

    npm run build:app
    
  7. Open a pull request with a clear description of the change.

For UI changes, include screenshots where useful.


πŸ› Reporting bugs

When reporting a problem, include as much of the following as possible:

  • Operating system
  • Browser or Obsidian version
  • OpenGantt version/commit
  • Whether you are using the web app, Obsidian plugin, or desktop application
  • The YAML that reproduces the issue
  • Console/build errors
  • Screenshots or recordings when appropriate

A minimal reproducible example makes debugging considerably easier.


πŸ“„ License

OpenGantt is released into the public domain under the Unlicense.

See LICENSE for the full license text.

OpenGantt incorporates the MIT-licensed ts-gantt project.


πŸ™ Acknowledgements

  • ts-gantt β€” underlying Gantt chart foundation
  • js-yaml β€” YAML parsing
  • Obsidian β€” Markdown knowledge-management platform supported by the plugin
  • Tauri β€” desktop application framework

⚠️ Project status

OpenGantt is an actively developed open-source project.

The repository currently contains a standalone browser application, an Obsidian plugin, and a Tauri desktop shell. Features and interfaces may change between versions.

The latest web version is available at:

🌐 https://jebbycodes.github.io/OpenGantt/

If you are using OpenGantt for important project planning, keep your YAML/Markdown source files under version control or maintain regular backups.

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.