Thanks @Serge, it’s awesome to get an enterprise perspective. That’s a great point about the people writing the docs not being those creating the screenshots. That’s exactly how it was when I worked at FreeAgent (a 250+ person company).
I’m primarily aiming at small/1 person web apps, simply because that’s something I know about from running Saber. I found it hard to keep on top of docs, with screenshots and videos taking a lot of time. Of course in those companies it is mostly likely the same person writing the docs and taking screenshots.
That said if this tool could be useful to large companies that would also be great
The demo I’ve built is doesn’t interfere with the customer site at all, and doesn’t require a browser plugin. Instead it loads the site being documented in an iframe. Of course that could be a problem depending on the customer’s
Content-Security-Policy, I’m hoping for the majority of users it will be fine as they’ll be able to run the docs app on their own subdomain. Worst case scenario they’ll have to modify their
frame-src directive to include that domain.
When you say yearly licence do you mean for an entirely self-hosted on site version (ie: both the docs and the tool to create them are self-hosted)? As that’s a road I definitely do not want to go down. The back end service is required even if you’re exporting doc’s HTML for self hosting, as the screenshots and videos are initially saved locally as blobs, those blobs need to be uploaded to a server for the rest of the world to see.
Thanks again for filling in the form, and Open Source Drums looks really cool, I’ll definitely be following that