Builders: Do you have support docs? How often do you update it?
Joseph Lee
7 replies
One of the biggest hassles/headaches when it comes to shipping quickly is how quickly docs can go out of date.
For instance, if any design, text, or flow changes, someone needs to remember to go back and update all relevant pages.
How do folks handle this today?
Replies
Solomon Bush@solomon_bush
Log Harvestor
Launching soon!
Actually just finished my API docs. Check them out!
https://www.logharvestor.com/doc...
Share
Supademo
@solomon_bush very cool!
Launching soon!
I'd love to hear everyones feedback on this. We're in the process of building out our support docs. Doing so with Intercom and are waffling between a few different ways of structuring them. They will likely need to be updated (added to) after every new user facing iteration.
Hard to find a way around this but if someone has one - I'm all ears.
Supademo
@dzaitzow will do - feel free to follow along on our progress by hitting notify here :)
https://www.producthunt.com/prod...
Supademo
@dzaitzow a lot of our customers are using Supademos embedded within docs like Gitbook, Zendesk, Confluence, etc.
They find that spending 2 mins to create an intuitive click-through is faster than screenshot+typing up text.
One thing we’re considering is how to have these auto update after being embedded :)
Launching soon!
@supademo_joe hmmmm maybe that makes sense. Have core elements that won't be changing remain the same (maybe even relatively vague) and amend click through product tours for new / amended features.
Let me know how far you get re: auto updating. Intercom seems pretty solid for a lot of this stuff but I don't think their AI integration has anything to do with internal doc creation - more of an advanced AI bot for customer facing stuff / scanning relevant docs to product curated responses. So if we're not creating robust support docs / amending them regularly - might be a wasted tool (or worse a tool that provides inaccurate information haha)
Supademo