Looked through the forums. Nothing intersects exactly
What I’m trying to do
I am creating a knowledgebase to share with other students but only in a read-only setting. I know I can simply publish, but none of the options (including static-site options or Obsidian’s own Publish platform) gives you the feel of the app itself. Also taking advantage of the many community plugins.
Having user permissions don’t seem to be an option. Technically I can have everyone launch in presenter view and never switch to edit view but that’s not ideal since human error is always triumphant.
The other option is to make “production” and “backup” copies of the vault. I could set up a one-way sync and let users only use the production vault, but that’s also less than ideal.
Essentially an “Obsidian-lite” for just review of content while editing and addition of updated content is done in the full client.
Yes, both of these requests look to create a focused restriction (specific file/folder).
But I think a completely read-only instance of Obsidian opens a whole unique experience. It’s more like a museum tour. You can’t mess around with the artwork but the way you can explore the art remains rich and the ability for discovery better than a static site.
Right now, Obsidian is an amazing experience for the creator. But I think it can also be a tremendous asset as a vehicle to distribute knowledge as well. Imagine an entire presentation being developed in Obsidian where you could explore the framework that the author is conveying.
Of course, you may then want to take some notes along the way…