The one thing I don't get though is who leaves their documentation artifacts to a SaaS? You're a pricing change / company collapse / systems outage / unacceptable ts&cs change away from losing your docs.
Right. It's okay to leave written documentation on SaaS (e.g. Notion), because the text is the artifact. If they're shutting down, or I don't like them anymore, I just move the text. But if Ilograph goes down, all I have is useless YAML.
Our team went through this thought process when we decided to open source our text-to-diagram language, users need to be able to reproduce their docs even if we shut down (https://github.com/terrastruct/d2).
> But if Ilograph goes down, all I have is useless YAML.
Depends. If you're using Ilograph Desktop [0], an outage won't affect you. And both with Ilograph Desktop and paid versions of the web app, you can export your diagrams to standalone HTML files. These artifacts will live forever.
I moved from Notion because of too many bugs, outage is just one of many scenarios where you'd want to bail, and not a primary one because it's not like a diagram service is in the customer path.
The HTML files are also not enough for me. It's like a bricked artifact. I can't modify my diagrams anymore. Like if I adopted a company's programming language and they assured me my assembly code artifacts will live forever.
The one thing I don't get though is who leaves their documentation artifacts to a SaaS? You're a pricing change / company collapse / systems outage / unacceptable ts&cs change away from losing your docs.