Make.md for Obsidian: Notion-Like Workspace Setup Guide

Quick Answer: Make.md is a comprehensive Obsidian plugin that transforms the application’s native markdown interface into a Notion-like workspace. It replaces standard folders with dynamic “Spaces,” introduces seamless inline block editing, and adds visual “Context” blocks for database-like functionality, all without sacrificing the security, privacy, and speed of local plain-text files.

Obsidian has long been the gold standard for personal knowledge management, prized for its local-first architecture and future-proof plain text files. However, its native interface is highly traditional. New users, particularly those migrating from modern workspace tools, often struggle with Obsidian’s reliance on rigid folder structures, syntax-heavy file embedding, and the steep learning curve required to build dashboards using code-centric plugins.

Many users want the visual hierarchy, intuitive drag-and-drop mechanics, and slash-command editing of Notion, combined with the unparalleled speed and local ownership of Obsidian. Achieving this balance natively requires stitching together a dozen different plugins, managing conflicting CSS snippets, and constantly tinkering with settings just to maintain basic functionality.

Make.md exists to solve this precise workflow bottleneck. Instead of acting as a single-feature utility, Make.md is a complete environment overhaul. It restructures how you navigate your vault, edit your text, and organize metadata, bridging the gap between flat markdown files and a relational database workspace. This guide breaks down the core features of Make.md, provides a structured setup process, and evaluates the technical tradeoffs of running such a heavy modification on your local vault.

What is Make.md? Core Features Explained

Make.md operates on three foundational pillars designed to abstract away the underlying markdown syntax while retaining its structural integrity. Understanding these features is critical before reorganizing your vault.

Spaces: Reimagining File Navigation

In standard Obsidian, notes are managed via the native file explorer, which strictly mirrors your operating system’s folder directory. Make.md replaces this with “Spaces.” A Space acts as a dynamic container that can group notes by folders, but also by tags, frontmatter properties, or manual curation. This allows a single note to exist in multiple logical Spaces without duplicating the actual markdown file on your hard drive, mirroring Notion’s flexible page hierarchy.

The Flow Editor: Inline and Block-Based Editing

Obsidian natively requires you to open linked notes in separate tabs or panes to edit them. You can embed a note using the ![[Note Name]] syntax, but this embed is strictly read-only unless you switch contexts. The Make.md Flow Editor fundamentally changes this behavior by introducing seamless inline editing. When you embed a note using the Flow Editor, it renders as an editable block directly within your current document. You can modify the embedded file without ever leaving your primary workspace. Additionally, the Flow Editor brings slash commands (/) to Obsidian, allowing you to quickly insert tables, callouts, and media without memorizing markdown syntax.

Context Blocks: Visual Databases

For users relying on the Dataview plugin to build tables and track metadata, the coding requirement can be tedious. Make.md introduces Context blocks, which provide a visual interface for managing frontmatter and note properties. Similar to Notion databases, Context blocks allow you to view note metadata as tables, lists, or galleries. You can edit properties directly within the table cells, and the plugin automatically updates the YAML frontmatter of the corresponding markdown files.

Setting Up Make.md in Your Vault

Transitioning to Make.md requires a deliberate setup process to ensure it plays nicely with your existing notes. It is highly recommended to test the plugin in an isolated vault before enabling it on your primary database.

1. Installation: Navigate to Obsidian’s Community Plugins settings, disable Safe Mode, and search for Make.md. Install and enable the plugin.
2. Initial Indexing: Upon activation, Make.md will begin indexing your vault. For a vault of 1,000 to 3,000 notes, this background process takes roughly 30 to 60 seconds. Do not begin heavily editing files during this initial scan.
3. Configuration Toggles: Go to the Make.md settings panel. The plugin is modular. If you only want the visual folder structure, you can enable Spaces while disabling the Flow Editor. For the full Notion-like experience, ensure Spaces, Flow, Context, and Maker Mode are all toggled on.
4. Hiding the Native Explorer: To prevent UI clutter, collapse or hide Obsidian’s default File Explorer tab in the left sidebar, relying entirely on the new Spaces menu provided by Make.md.

Replacing Folders with Spaces

The most immediate visual change when adopting Make.md is the sidebar navigation. Spaces eliminate the strict hierarchy of standard directories.

When setting up Spaces, start by creating a “Root Space” for your primary workflow—for example, “Active Projects.” Instead of moving physical files into this Space, you can configure the Space to automatically pull in any note tagged with #project/active or any note containing the frontmatter property status: active.

This dynamic routing is particularly useful for task management and daily tracking. You can pin frequently used Spaces to the top of your sidebar, and customize each Space with unique icons and cover images. If you prefer manual organization, Make.md allows intuitive drag-and-drop ordering, bypassing the alphabetical sorting limitations of native Obsidian.

Replicating Notion Databases with Context Blocks

Context blocks serve as the engine for replacing Notion’s relational databases. If you manage a content calendar, CRM, or reading tracker, Context blocks simplify the workflow drastically compared to writing Dataview queries.

To create a database view, create a new note and type /context. Select the target Space you want to visualize. Make.md will generate a table displaying all notes within that Space, using their frontmatter keys as column headers.

You can instantly switch this view from a standard Table to a Gallery (which pulls the first image from each note as a cover card) or a Board view (replicating a Kanban setup based on a specific property, like status). The major advantage here is bidirectional editing. If you change a project’s status from “In Progress” to “Completed” within the Context table, Make.md silently writes that change into the source note’s YAML frontmatter. This ensures your data remains portable and entirely self-contained within standard markdown files, entirely independent of the plugin’s proprietary code.

Mastering the Flow Editor and Inline Blocks

The Flow Editor dramatically reduces the friction of context switching. If you are drafting a comprehensive research report, you likely need to reference and combine multiple atomic notes.

By typing /flow and selecting a file, Make.md inserts the entire document seamlessly into your current view. Unlike a standard embed, this block is fully interactive. You can delete paragraphs, rewrite sentences, and add new tags to the embedded note without leaving your master document.

This functionality is paired with the “Blink” feature, activated by Ctrl + Space (or Cmd + Space on Mac). Blink serves as an omnipresent command palette and quick-capture window. You can search for a note, append a quick thought to it from the Blink overlay, and close it, all while your main workspace remains untouched. The slash command menu also democratizes complex markdown syntax, making the insertion of multi-column layouts, callout boxes, and custom formatting accessible via a simple keystroke.

Practical Advice: Tradeoffs and Performance

While Make.md provides an exceptional visual and functional upgrade, transforming a lightweight text editor into a comprehensive workspace environment introduces inevitable technical tradeoffs.

Performance Overhead Because Make.md heavily modifies Obsidian’s Document Object Model (DOM) to render inline editors and complex tables, users on older hardware or those managing massive vaults (10,000+ notes) may notice increased latency. Specifically, switching between large Context tables can introduce a 1 to 2-second rendering delay. Scrolling through a document with dozens of nested Flow embeds requires more RAM than scrolling through plain text.

Plugin Conflicts Make.md overrides core UI elements. As a result, it frequently conflicts with other plugins that modify the file explorer or editor views. Plugins like File Explorer Note Count, Custom File Explorer sorting, or advanced Hover Editor setups will likely break or behave unpredictably when running alongside Make.md. Furthermore, custom CSS themes that heavily style the native file tree will not apply properly to the Make.md Spaces sidebar.

Portability and Lock-in It is vital to understand the difference between data lock-in and visual lock-in. Your data remains perfectly safe; Make.md stores all properties as standard YAML frontmatter and text as standard markdown. However, if you disable the plugin, your visual workspace—the specific layout of your Context boards, your curated Spaces, and your inline editable embeds—will revert to standard markdown folders and basic syntax. The aesthetic setup is locked to the plugin, even if the underlying data is not.

The Final Verdict: Workspace Integration

Make.md successfully achieves what it sets out to do: it provides a robust, Notion-like user experience layered safely over local, plain-text markdown files. For users who rely heavily on visual organization, drag-and-drop database management, and block-based editing, it is arguably the single most impactful plugin available in the Obsidian ecosystem.

It is best suited for project managers, content creators, and former Notion users who require a high degree of visual polish and hierarchical flexibility to function effectively. Conversely, purists who prefer raw markdown, rely heavily on custom coding via DataviewJS, or demand absolute zero-latency performance above all else may find the environment overly abstracted and resource-intensive. Evaluate your workflow demands carefully, but for those seeking a unified, aesthetic workspace, Make.md delivers an unparalleled structural overhaul.

Frequently Asked Questions

Does Make.md modify my original Markdown files?

Make.md does not use proprietary file formats. All text edits are saved as standard markdown. When you use Context blocks to edit database fields, the plugin simply writes or updates standard YAML frontmatter at the top of your existing .md files.

Will Make.md slow down my Obsidian vault?

For average vaults (under 5,000 notes), performance impact is minimal. However, because it relies on heavy DOM manipulation to render inline files and database tables, users with massive vaults or older devices may experience slight rendering delays when opening complex Context views.

Can I use Make.md alongside Dataview?

Yes, the two plugins can coexist. Dataview remains excellent for complex, read-only algorithmic queries across your vault, while Make.md Context blocks are better suited for visual, editable database management.

Is the Make.md plugin available on mobile?

Make.md is available on the Obsidian mobile app and functions similarly to the desktop version. However, due to the limited screen real estate and lower processing power of mobile devices, navigating large Spaces and rendering wide Context tables can be cumbersome compared to the desktop experience.

How do I uninstall Make.md safely?

Simply disable and uninstall the plugin from the Community Plugins menu. Your folders will return to the native File Explorer, your Context tables will disappear (but the YAML data remains in the files), and your Flow embeds will revert to standard Obsidian embed syntax. No data is lost in the removal process.

---

Related Reading

• Copilot for Obsidian Complete Guide: Chat With Your Notes
• HoverNotes for Timestamped Video Notes in Obsidian: Complete Guide