ObsidianMD

4105 readers

1 users here now

Unofficial Lemmy community for https://obsidian.md/

founded 1 year ago

MODERATORS

grabyourmotherskeys@lemmy.world

Pexily@lemmy.world

Obsidian for Writing Manuals (lemmy.world)

submitted 1 year ago by hutchmcnugget@lemmy.world to c/obsidianmd@lemmy.world

59 comments fedilink hide all child comments

Is Obsidian a good tool to use for writing technical manuals? I would like to write an Operation Manual for municipality's water system. There will be embedded screenshots and some links to other sections of the document.

Ideally we could "publish" to offline html. The customer would also like a printed manual.

If Obsidian is no good, I would love suggestions on software you have used to write short manuals with pictures, preferably not Word.

you are viewing a single comment's thread
view the rest of the comments

[–] laurelinae@lemmy.world 1 points 1 year ago (3 children)

You miss the point. The same argument could be brought forth against any other commercial license, like MS Office. But you are right, the answer is: none and I consider myself a FOSS advocate, but this is not the world we live in. Obsidian Dev Team puts in work and for them to be able to continue doing so, they need compensation, it's work after all.

Most software doesn't even differentiate between private and commercial use or let's you pay for both, but makes private use cheaper. What obligation does Obsidian suddenly have to be free for commercial use? It's already free for private use, educational purposes and even for freelance work. If someone is making money using a tool, then why is it ridiculous to pay for the tool?

[–] effingjoe@kbin.social -1 points 1 year ago (2 children)

Are you serious? I explained it in the comment you replied to.

[–] laurelinae@lemmy.world 1 points 1 year ago (1 children)

No, you didn't or I counter-argued and you seem to not have understood my question in the new context that I provided.

[–] effingjoe@kbin.social 1 points 1 year ago

I am no longer going to maintain two forked discussions. Let's combine these into one.