The latest articles on DEV Community by Ali Güçlü (@aliguclu). https://dev.to/aliguclu https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3980090%2Fd70ec163-e1ca-4d67-8198-379418929699.jpg https://dev.to/aliguclu en Ali Güçlü Thu, 11 Jun 2026 20:04:10 +0000 https://dev.to/aliguclu/obsidify-for-mac-is-live-turn-markdown-vaults-into-publish-ready-websites-4c95 https://dev.to/aliguclu/obsidify-for-mac-is-live-turn-markdown-vaults-into-publish-ready-websites-4c95 <p>Obsidify for Mac is now live on the App Store.</p> <p>I built Obsidify for people who already work with Markdown: developers, technical writers, documentation teams, product teams, creators, and Obsidian users who want a clearer path from local notes to publish-ready websites.</p> <p>Most Markdown workflows start locally.</p> <p>You have folders, README files, GitHub docs, knowledge base notes, or an Obsidian vault. At some point, some of that content needs to become a public website, documentation site, wiki, blog, or product knowledge base.</p> <p>That transition is often messy.</p> <p>Obsidify is designed as a focused Mac publishing workspace for that step.</p> <h2> What Obsidify does </h2> <p>Obsidify helps you:</p> <ul> <li>Select local Markdown folders and vault-style content</li> <li>Prepare README files, docs, and GitHub-oriented documentation</li> <li>Structure content as a blog, wiki, documentation site, or knowledge base</li> <li>Review headings, sections, and organization before publishing</li> <li>Use AI-assisted workflows for summaries, introductions, rewrites, and structure improvements</li> <li>Track publishing status from a focused Mac workspace</li> </ul> <h2> What Obsidify is not </h2> <p>Obsidify is not a general note-taking app.</p> <p>It is not trying to replace your Markdown editor or your Obsidian vault.</p> <p>The goal is narrower:</p> <p>Take Markdown content that already exists and help prepare it for publishing.</p> <h2> Why I built it </h2> <p>I wanted a workflow where Markdown files, vault folders, and developer docs could move from local content to website output without losing structure.</p> <p>Obsidify is built around that publishing step.</p> <p>It keeps the source folder visible, helps organize the content, and creates a more repeatable path from notes and docs to publish-ready website output.</p> <h2> Who it is for </h2> <p>Obsidify is for:</p> <ul> <li>Developers publishing technical docs</li> <li>Technical writers working with Markdown</li> <li>Product teams maintaining knowledge bases</li> <li>Creators turning notes into blogs or wikis</li> <li>Obsidian users who want a publishing-focused workflow</li> <li>MCP and AI-assisted workflows that need a clear publishing destination</li> </ul> <h2> Launch </h2> <p>This is the first public Mac release.</p> <p>Obsidify for Mac is now available on the App Store:</p> <p><a href="https://apps.apple.com/us/app/obsidify/id6773428570?mt=12" rel="noopener noreferrer">https://apps.apple.com/us/app/obsidify/id6773428570?mt=12</a></p> <p>I would be happy to hear feedback from Markdown-first users, technical writers, and developers who publish documentation.</p> markdown github ai