Introduction
O2 is a tool that converts Obsidian Markdown files into the syntax of other platforms.
Previously, converted files were automatically moved to an archive. If you wanted to revise the document, you had to open the blog platform project in a code editor or move the archived document back, which was inconvenient. This often led to discrepancies between the original Obsidian document and the published version as more revisions were made.
Given that blog posts often undergo frequent revisions shortly after being published, it was necessary to implement a loose synchronization state that allows for some level of revision within Obsidian and frequent updates to the blog platform.
Therefore, starting from version 2.0, converted files are no longer moved to an archive. The conversion process now creates a copy in place, allowing you to continue revisions within Obsidian. If you no longer wish to make changes in Obsidian, you can manually exclude the document from the ready directory.
You can enable the Auto archive
toggle to use an automatic backup feature similar to the previous version.
Prerequisites
Vault Structure
Your Obsidian Vault should have the following structure:
Your vault
├── ready (Path for documents you want to convert)
├── archive (Optional. Backup path for converted documents)
└── attachments (Path for attachments)
Other directories will be ignored.
You can change the default path names in the settings.
Usage
- Move the note you want to convert to the
ready
folder. - Use the
cmd + p
shortcut in Obsidian to run theO2: convert to Other Platform
command. - The document will be converted to the syntax of the platforms defined in the settings.
- The document is converted through a copy, so the original remains unaffected.
- If the
Auto archive
toggle is enabled, the converted document will be moved to thearchive
folder.
- O2 follows the PARA paradigm, where documents are not fixed to a specific category and can be moved to different categories as needed.
- If we relied solely on front matter for categorization, we would need to scan the front matter of all documents to find those to convert, which could cause performance issues for users with a large number of documents. By using a dedicated directory for conversion, O2 efficiently narrows the search scope.