Is this project open source? Yes (AGPL-3.0)
Is this project completely free? Yes
Is this project vibe-coded beyond the author’s ability to comprehend how it works? No
Community Directory: Rich Table
Hey everyone 
Native Obsidian tables are plain GFM — no cell merges, no click-to-edit, no status columns. I built Rich Table to fix that. After months of daily use for project tracking I’m happy to share it.
Rich Table renders interactive tables inside a rich-table fenced code block. Everything is stored as plain text in your vault — no database, no proprietary format.
Key features
Cell merging — define merges in YAML, or drag-select cells and click Merge. Overlapping merges auto-expand to a valid bounding box, so you can never create a broken state.
Typed columns — attach a type to a column and values become colored pill badges. Click to switch values from a dropdown. Built-in: task-status (todo / pending / in-progress / done / cancel), priority, boolean, rating, effort, approval, date. Custom types configurable in settings.
Inline editing — single-click any cell to edit. Full [[wikilink]] autocomplete with heading (#) and block reference (^) support.
Cell styles — double-click any cell for a panel: background color, text color, font size with live preview. Also works on drag-selected ranges.
Drag to reorder — drag handles on row left / column top to reorder. Merges and per-cell styles remap automatically.
Title & footer — add a title above and notes below the table, both click-to-edit inline.
Quick example
---
title: Sprint Board
columns:
- { name: Task, width: 200 }
- { name: Status, type: task-status }
- { name: Priority, type: priority, align: center }
merges:
- A2:A3
styles:
- { target: "1:1", bold: true, bg: "#e8f0fe" }
footer: "Updated weekly · click any cell to edit"
---
| Task | Status | Priority |
| -------- | ------- | -------- |
| Design | done | high |
| Build | pending | medium |
| Test | todo | low |
Still v0.1.x — bug reports and feedback very welcome. Roadmap in the README (sorting, filtering, conditional formatting, and more coming).
— as the plugin has grown and more features piled on top of that original format, the codebase has gotten more complex, and that’s naturally brought a higher chance of edge-case bugs (especially around styles, merged cells, and row/column operations interacting with each other). So I’m actively working on making the foundation more robust and maintainable