Obsidian plugins with #bases#

The TaskNotes plugin turns each task into its own Markdown note and uses Bases queries to power list, kanban, calendar, agenda, and mini calendar views. It stores task data in YAML frontmatter, so tasks stay portable and easy to edit outside the plugin. Natural language entry helps create tasks quickly, while configurable properties let existing workflows map fields like due dates or custom metadata. It also handles recurring tasks with per instance completion, optional occurrence notes, time tracking, Pomodoro sessions, dependencies and computed formulas inside the bundled views. Calendar sync is available for Google, Microsoft or ICS sources and the plugin can connect to external tools through its HTTP API, CLI, browser extension and webhooks.

The Calendar Bases plugin turns Obsidian Bases results into a calendar so notes with date properties can be viewed where they belong in a month layout. It focuses on entries that already carry start dates and can also handle end dates when something spans more than one day. You can move items on the calendar to reschedule them and the plugin updates note frontmatter to match, which makes the view useful for planning as well as reviewing what is already in the vault. It also supports opening entries directly from the calendar and using context menus for related actions.

The Map view for Obsidian Bases plugin adds a geographical perspective to your notes by turning linked data in Bases into an interactive map. It allows you to display markers that update dynamically based on filters, making it easy to visualise note collections in spatial context. Markers can be styled with custom icons from the Lucide library and coloured using RGB, HEX, or CSS variables, offering strong visual cues for different categories. You can also load custom background tiles for a personalised map experience and define default zoom levels to control navigation. Coordinates can be stored as text, lists, or split into latitude and longitude properties, providing flexibility in data entry.

The Kanban Bases View plugin turns an Obsidian Base into a kanban board where notes are grouped into columns from any chosen property. You can pick fields like Status, Priority or Category, then move cards between columns with drag and drop to update that value directly from the board. Columns can also be reordered with a handle, and the chosen order is saved per property so the view stays consistent between sessions. Notes that do not have the selected value are collected into an Uncategorized column instead of disappearing. Clicking a card opens the note, which keeps the board useful as both a planning surface and a navigation layer. The plugin is mainly for managing Bases when your notes behave like tasks or tracked items.

The Bases Paginator plugin adds page navigation to Bases views so large result sets can be browsed without replacing native query controls. It provides first, previous, next and last page actions, page sizes from 1 to 1,000, support for grouped results and native rendering for links, tags, lists, images, formulas, dates, booleans and numbers. The view can keep headers sticky, place pagination above or below the table and exposes keyboard friendly controls with screen reader status and mobile sized touch targets. It works as a local, read only view, so searching, filtering, sorting and named views stay with native Bases. The plugin also preserves older saved options while leaving editing, row creation and other table only interactions to the native view.

The Base Board plugin gives Bases a property driven board view that behaves like a hands on Kanban workspace. It can build columns from frontmatter, move cards between them with drag and drop, rename cards or columns inline and open notes in a native floating editor. Cards can show metadata chips, tag filters, cover images and hover previews, while board level defaults let new notes inherit required properties and folders. It also keeps manual card order through a dedicated property, so layout decisions stay in the data instead of disappearing after a sort refresh. WIP limits and collapsible columns round out the view without hiding the underlying Markdown files.

The Canvas Bases plugin turns a live Bases view into a spatial board where rows become draggable, resizable file cards with grouping, manual cards, assignment zones and relationship edges. Query logic stays in the `.base` file, while the plugin stores board layout, colours and other canvas specific state separately. It can create or update `.canvas` snapshots from the active Bases view, preserve unrelated manual canvas content, and carry card styling into generated nodes. The board also supports inline body editing, pinned notes, text cards, zoom controls and drag based link creation between cards. TaskNotes support is capability based, so task badges, menus and task relationships appear when available without making the main Bases and Canvas workflow depend on it.

The Power Bases plugin extends the core Bases feature with six extra views: board, calendar, timeline, chart, gallery, and a much deeper table. It keeps rows as normal notes with frontmatter, so data stays portable and sync friendly across devices. The board supports drag moves, swimlanes, WIP limits and bulk actions. Calendar and timeline views write schedule changes back to notes, while charts render grouped data as plain SVG. The table adds more field types, rollups, summaries, formatting, CSV import and formula editing with live preview. Every edit is grouped into undoable batches, and most features work fully offline. Its only network use is optional address autocomplete for Place fields.

The Bases Charts plugin adds scatter, line and bar chart views to Bases. After choosing a Base, you can map number, date or string values to the X axis and numeric properties to the Y axis, then switch between chart types without leaving the view system. It also supports grouping, color based splits and multi chart modes that separate results by group or by property. The README stays narrow and practical, focusing on axis rules, supported field types and how chart panels are arranged. That makes it a small but direct layer for turning structured notes into visual comparisons inside a Base.

The Bases Toolbox plugin adds a wide set of tools around Bases and frontmatter properties. It can find and replace property values with history and selective revert, bulk edit the results of an open base, write rollups back into real properties and apply conditional formatting to rows or cells. It also handles CSV import and export, note merging, duplicate finding, filter toggling and a zoom editor for cell values. Beyond that, it includes a property index, property format doctor, companion notes for non markdown files, file metadata stamping and inline field migration. Everything runs locally, with no network access or telemetry and changes are logged where the feature supports revert.

The Link Structure plugin adds a Structure view for Bases that turns notes linked through an up property into a draggable tree. It visualizes link based hierarchies instead of folder paths, so one note can appear under multiple parents and files can stay connected without folder notes. Moving items in the tree updates links automatically, and holding Ctrl copies a note to another branch without removing it from the old one. You can move several notes together with Shift, reveal the active file in each matching branch, filter the view through standard Bases filters and create subnotes from the context menu. It also follows existing link format settings and optional Templater templates can conflict when files are renamed or moved from a template.

The Feed Bases plugin adds a feed style layout to Obsidian Bases, showing notes and their body content in one editable scrolling view. Notes stay tied to their source files, so changes made in the feed are saved back without a separate sync step. The view can be sorted by modified date, created date, or name, which makes it easier to scan recent work or keep a stable reading order. It also lets you open note titles directly and use context menu actions from the feed instead of switching back to a standard list. The plugin is focused on changing how Bases content is read and edited, not on adding a new storage format or separate workflow layer.