Migrating from DokuWiki to Obsidian
The author migrated notes from DokuWiki to Obsidian for better usability, using a script for conversion and preferring Git for backups, resulting in a smoother note-taking experience.
Read original articleThe author shares their experience of migrating personal notes from DokuWiki to Obsidian, highlighting the reasons for the switch and the steps involved in the migration process. DokuWiki, while effective, was underutilized by the author, who preferred the simplicity of Markdown files and the user-friendly interface of Obsidian. The migration was straightforward due to DokuWiki's use of plaintext files, which facilitated easy transfer. The process involved copying the data folder to a local machine, converting DokuWiki syntax to Markdown using a script, moving media files, and verifying the final output in Obsidian. After a year of using Obsidian, the author finds it to be a smoother experience, emphasizing the importance of backing up notes, which they manage through a Git repository instead of relying on third-party services. The post aims to assist others considering a similar migration.
- The author migrated notes from DokuWiki to Obsidian for better usability.
- The migration process included copying files, converting syntax, and moving media.
- A script was used to automate the conversion from DokuWiki to Markdown.
- The author prefers using a Git repository for backup over third-party services.
- The transition to Obsidian has resulted in a smoother note-taking experience.
Related
My weekend project turned into a 3 years journey
Anthony's note-taking app journey spans 3 years, evolving from a secure Markdown tool to a complex Electron/React project with code execution capabilities. Facing challenges in store publishing, he prioritizes user feedback and simplicity, opting for a custom online deployment solution.
Node 18 Ate My Website
The author upgraded their Next.js website to Node.js 18, facing issues with deprecated dependencies. They rebuilt the site with TypeScript, Contentlayer, Tailwind CSS, and Vercel Analytics, emphasizing simplicity and emerging technologies.
I Use Obsidian
Jason A. Heppler praises Obsidian for historical research, noting its plain text format, mobile interface, community, plugins, and seamless desktop-to-mobile experience. He organizes notes with folders, tags, and plugins like DataView.
Switching from Arch to NixOS
The author discusses their transition from Arch Linux to NixOS, highlighting improved system configuration management, challenges with documentation, and a smooth setup process, while noting a steep initial learning curve.
Archiving and Syndicating Mastodon Posts
The article details archiving Mastodon posts to a personal website using the PESOS model, emphasizing online presence, automation, and content organization through a custom tool developed in Go.
- Several users suggest alternatives to Obsidian, such as TiddlyWiki, Foam, and BookStack, highlighting their own positive experiences.
- There is discussion about the usability and readability of the platforms, with some users expressing frustration over interface issues.
- Users share tools and scripts for converting DokuWiki content to Markdown, emphasizing the importance of open formats for data portability.
- Comments highlight the balance between proprietary software and open-source alternatives, with some praising Obsidian's approach to user satisfaction.
- Some users mention the collaborative potential of Markdown files stored in Git repositories, enhancing decentralized knowledge sharing.
By making a great product, they attract users. Usually the main argument against software like this is vendor lock-in. But by using open formats, there's always an escape hatch. If they decided to squeeze their users, I suspect a decent open source alternative would pop up very quickly. In the meantime, casual open source alternatives are very unlikely to catch up in terms of quality and features, because they don't have a funded team working on them full time.
On the flipside, Obsidian is incentivized to keep their customers happy, because their moat isn't so large as to allow complete complacency.
Overall some of the best aligned incentives I've seen. Though it does make me sad because I feel like we almost never see this good of balance in open source software.
To write Markdown in DokuWiki, the "DokuWiki Commonmark Plugin" [0] is pretty great.
To use it, tips are:
- REQUIRED: On the top line of each page, put `<!DOCTYPE markdown>` (using the new toolbar button or typing it in). So that Dokuwiki knows the page is in markdown.
- STRONGLY SUGGESTED: In the Dokuwiki Config, set the `maxseclevel` to 0. Since the Commonmark markdown plugin currently unfortunately sort of messes up edit-section.)
That's basically it. Makes the Dokuwiki files that much more immediately-portable, in theory.
And since we have a WordPress site, Dokuwiki is about a 30-second installation away.
Looking into the project governance/maintenance it looks sturdy- while seemingly one person does a lot of the work, there's a community there. It appears to me, a newcomer, like a project that could last a very long time while being boring and doing exactly what it needs to, no more and no less.
As for the subject of the post itself; for a single person personal wiki, I'd also use Obsidian. I love that I can sync it to my phone with Syncthing, which is a mild pain but free!
It's nice to be able to have it publicly available and accessible from any internet connection.
I used to use DokuWiki about 15 years ago (~2008) to document the IT systems at a biomedical informatics department.
Related
My weekend project turned into a 3 years journey
Anthony's note-taking app journey spans 3 years, evolving from a secure Markdown tool to a complex Electron/React project with code execution capabilities. Facing challenges in store publishing, he prioritizes user feedback and simplicity, opting for a custom online deployment solution.
Node 18 Ate My Website
The author upgraded their Next.js website to Node.js 18, facing issues with deprecated dependencies. They rebuilt the site with TypeScript, Contentlayer, Tailwind CSS, and Vercel Analytics, emphasizing simplicity and emerging technologies.
I Use Obsidian
Jason A. Heppler praises Obsidian for historical research, noting its plain text format, mobile interface, community, plugins, and seamless desktop-to-mobile experience. He organizes notes with folders, tags, and plugins like DataView.
Switching from Arch to NixOS
The author discusses their transition from Arch Linux to NixOS, highlighting improved system configuration management, challenges with documentation, and a smooth setup process, while noting a steep initial learning curve.
Archiving and Syndicating Mastodon Posts
The article details archiving Mastodon posts to a personal website using the PESOS model, emphasizing online presence, automation, and content organization through a custom tool developed in Go.