If you are building a customer facing app which needs a docs page to guide your customers, for example to outline your app’s API, or to show “how to use” instructions, then I recommend adding an AI bot to your docs page.
I have just been integrating my app with a complex 3rd party platform and API. When I had some issues, instead of just scouring their docs page and banging my head against my keyboard, I simply told their DocBot my problem and it gave me the answers.
It seems such an obvious idea. But this is seriously going to change how documentation pages are built and used in future!!
1 Like
Honestly, I’ve gone to ChatGPT for more answers on GCP, AWS, and Wix than I do their own Docs because they make it way more complex than it has to be. This is definitely the way.
Are there any AI Bots you’ve tried? Better yet, have you used any to build your own docs pages?
This is great, thank you very much and it inspired me
Notion is probably a good option for this as well - honestly we’re using Notion for everything (other than Replit of course!)
@shawn93 I’ve built a couple of RAG-based bots inside Replit apps from scratch, but not used any off-the-shelf bot builders. There are plenty of ready-made solutions out there you could plugin to your app, but isn’t that cheating? 
You’re a vibe engineer, so get your Replit keyboard out and starting chatting to the agent 
@richarddenton84, personally, I’m wanting to reduce my use of bloated, over-priced, 3rd party SaaS tools
I’m a vibe engineer, so if Replit’s up for building something, then game on…
Agreed in general but Notion’s the exception. It’s quick and easy to do most things and the AI capability is great.
I really like this approach. Adding an AI bot to documentation pages seems super practical—especially when dealing with complex APIs. Instead of digging through dense docs, the bot can provide targeted answers, making the learning curve much easier.
1 Like
Hi-followed another convo about your RAG/Replit journey; how did you end up doing your RAG pipeline?