[ender341341]

Howto is super important to me, it's absolutely bananas how many docs seem to assume you understand the whole library and don't explain any surrounding context or how things effect other things in the context.

Especially bad in 100% documention requirement shops where you get stupid things like '@param foo - Control <foo>' where having some examples would be much more useful than a wall of those parameter 'descriptions'.

[neom]

Is a chatbot kinda annoying then? Chat bot with a bit of a guide better? I presume you open docs ctrl F and search for whatever? Would you be annoyed trying to "search" with a chatbot? Tnx btw.

[benswerd]

Our chatbot isn't trying to answer questions as much as it is to point people in the right direction.

People have made chats that are better at actually solving problems but the usecase we targetted was I have a question how do I get to the answer. This works better than search, because it allows for semantics to work, for example when someone asks about SvelteKit, even though our docs don't mention it, the ai points towards the Vite docs.

[ender341341]

I definitely prefer it to to be text.

I'm not a fan of chat bots on random websites, but also my work is pretty regulated so as far as AIs go we're only supposed to use ones we have direct agreements with.

While I can just not put in anything protected I much prefer being able to point one of the bots we can use at docs and be able to provide it context for what I'm working on.