This is a question for those of you who use Obsidian Publish, as I’m considering getting it.
How do you prepare and organize your notes for publishing? What have you found works best organizationally? My vault has a bunch of technical notes I’ve created over the years, and I’d love to share them, but it seems I’d have to sanitize them somewhat of personal data. This is fine, and I’m okay doing this, but how do you handle situations where you may want to publish a document for the world to see and end up with two documents (one with private and one with public data)? Won’t that end up with duplicate data that you have to sort through every time you search for something in your vault?
For instance, let’s say I have a cool document on how to self-host some sort of cool software on my server. I documented as I went, but of course, screenshots and commands are specific to my server, and I certainly DON’T want to show that. So I spend the time to sanitize it, changing path names and specifics. Now I have two documents, the original and the new one for the public. I’m just imagining how 6 months from now I’ll end up with multiple overlapping documents content wise that I’ll have to manage.
I figure everybody else has some good ideas on how to manage/organize things if you plan on using Obsidian Publish.
Thanks!