A kanban-style drag-and-drop custom view for Obsidian Bases that allows you to organize your notes into columns based on any property.
Screen.Recording.2026-03-24.at.19.20.30.mov
- Dynamic Column Generation: Select any property from your base to generate kanban columns automatically
- Drag and Drop: Move cards between columns with smooth animations
- Column Reordering: Drag columns by their handle (⋮⋮) to reorder them to your preference
- Column Color Themes: Assign colors to columns using the color picker button for visual categorization
- Column Order Persistence: Your column order is saved per property and persists across sessions
- Property Selection: Choose which property determines your columns (e.g., "Status", "Priority", "Category")
- Uncategorized Entries: Notes without a value for the selected property are automatically grouped in an "Uncategorized" column
- Property Display: Selected properties are shown on each card for at-a-glance context
- Custom Card Titles: Display a frontmatter property as the card title instead of the file name — useful when files share a common name (e.g.,
README.md) across folders - Property Word Wrap: Toggle property text wrapping on cards to handle long property values
- Click to Open: Click any card to open the corresponding note (Cmd/Ctrl+click to open in new tab)
- Visual Feedback: Clear visual indicators during drag operations
- Responsive Design: Works well on different screen sizes
- Download the latest release from the Releases page
- Extract the plugin folder to your vault's
.obsidian/plugins/directory - Reload Obsidian
- Enable the plugin in Settings → Community plugins
-
Clone this repository:
git clone https://github.com/xiwcx/obsidian-bases-kanban-custom-view.git cd obsidian-bases-kanban-custom-view -
Install dependencies:
npm install
-
Build the plugin:
npm run build
-
Link or copy the plugin folder to your vault's
.obsidian/plugins/directory
- Create or open a Base in Obsidian
- Add a view and select "Kanban" as the view type
- Select the property you want to use for columns (e.g., "Status") in the "Group by" option
- Your notes will be automatically organized into columns based on the selected property's values
- Drag cards between columns to update the property value
- Click any card to open the corresponding note (Cmd/Ctrl+click to open in new tab)
- Drag columns by their handle (⋮⋮) to reorder them - your preferred order will be saved
- Optionally, select a property in "Card title property" to display that property's value as each card's title instead of the file name
If your base has a "Status" property with values "To Do", "Doing", and "Done":
- Select "Status" in the "Group by" dropdown
- Three columns will appear: "To Do", "Doing", and "Done" (plus an "Uncategorized" column for notes without a status)
- Drag cards between columns to change their status
- Click any card to open the note (Cmd/Ctrl+click to open in new tab)
- Drag columns by their handle to reorder them - your order preference will be remembered
If your project folders each contain a README.md with a title property:
- Select
titlein the "Card title property" dropdown - Cards will display the
titleproperty value instead of "README" - If a note is missing the property, the file name is used as a fallback
- Node.js (v24)
- npm
npm run buildnpm run devThis will watch for changes and rebuild automatically.
npm testnpm run typecheckThis project uses ESLint for linting and Biome for formatting. They are intentionally kept separate.
Lint (reports rule violations):
npm run lintLint with auto-fix:
npm run lint:fixFormat (rewrites files):
npm run formatCheck formatting (exits non-zero if unformatted; used by CI and the pre-commit hook):
npm run format:check- The plugin uses the
.obk-CSS class prefix (Obsidian Bases Kanban) for all view UI classes to avoid collisions with other plugins and themes.
-
Update version: Manually update the version in
manifest.jsonfollowing Semantic Versioning. -
Update package.json: Ensure the version in
package.jsonmatches the version inmanifest.json(the CI workflow will verify this). -
Update versions.json: Add an entry mapping the new version to the correct
minAppVersioninversions.json. -
Push to main: Push your changes to the
mainbranch. The GitHub Actions workflow will automatically:- Run tests and verify that
manifest.jsonandpackage.jsonversions match - Verify that the version exists in
versions.json - Build the plugin (runs
npm run build) - Extract the version from the built
dist/manifest.json - Create a git tag matching the version exactly (no
vprefix) if it doesn't already exist - Create a GitHub release and upload
main.js,manifest.json, andstyles.cssas release assets
Note: The release workflow only runs on pushes to
main(not on pull requests). You can also trigger it manually from the GitHub Actions tab. - Run tests and verify that
-
Submit to Obsidian Community Plugins (first release only):
- Follow the Obsidian plugin submission guidelines
- Submit a PR to the obsidian-releases repository
Contributions are welcome! Please feel free to submit a Pull Request.
This project is licensed under the MIT License - see the LICENSE file for details.
- Built with SortableJS for drag-and-drop functionality
- Inspired by the need for better task management in Obsidian Bases