I recently tried Publish, only to turn around and cancel. I figure I’d explain why, because I couldn’t find other discussion about this.
If there’s a setting I’m missing to avoid this behavior, let me know!
edit: my post sounds really down on Publish, but I do like it and I think it could be something I’d happily pay for.
Use case or problem
I want my published pages to always be rendered. If JS fails or disabled or disallowed, zero content is rendered:
I’m not opposed to JS! The opposite. But I’d rather see the initial document be enhanced with additional features like the map.
Surely this is affecting how Publish users’ pages are indexed by search engines, too.
Proposed solution
I don’t know how Publish works, but if I had to suggest something: render HTML on the server. Cache the hell out of it (invalidate on new publish - guessing this already happens with the .md blobs).
That way, publish.obsidian.md can send HTML down the pipe first. Then load up the user’s browser with assets.