peaxkl
We built something to help with that [1].
It was also pretty handy for importing existing documentation from obscure providers without having to build an integration for each of them.
We also added WebMCP [2] for agents to consume our public documentation/help center, but we haven't seen it used yet.
An API would work for all of these cases too, but since customers are using it in their AI tools anyway, MCP is just simpler for them.
[1] https://www.happysupport.ai/en [2] https://developer.chrome.com/docs/ai/webmcp
[1] https://handy.computer/ [2] https://github.com/cjpais/Handy
The taste goes in the direction of ClubMate, but has a stronger tea taste than the original ClubMate. I think reasons for that are the reduced amount of sugar and the fact that ClubMate uses natural flavor in their tea extract.
It took me 4-5 tries to get to a recipe that tastes good. Earlier tries involved cooking the mate, which led to a bitter taste. Cold brewing led to way better results.
Here is my current recipe for 5 bottles (á 0,5l):
- 60g mate tea leaves (coarse) [1]
- 500ml water
- 65g cane sugar
- 1 squeezed lemon
- soda water
1. Add 60g of mate to a 500ml bottle and fill up the rest with water
2. Let it sit in the fridge for 12-24h
3. Then strain the mate from the liquid
4. Use a filter cloth or a tea towel (soak with water first) to filter out the remaining suspended solids
5. Put sugar and the lemon juice together into a pot and start caramelizing the sugar
6. Then add the filtered mate tea and take the pot from the stove
7. Now distribute it equally on the 5 bottles and fill up the rest with soda
The mate tastes less sweet than the original mate, but is still a great drink to keep you awake.[1] Mate tea that I'm using: https://www.amazon.com/Playadito-Traditional-Colonia-Liebig-...
The tool makes it super easy to create help articles in any language, just by clicking through a process. The first results are super promising!
Creating and maintaining an up-to-date help center is a huge hassle. In many companies there is no one that really feels obligated to take care of it.
We want to optimize this process:
- Creation: Just click through your process. We take a screenshot on every click and generate a full written article with screenshots and a GIF. You can also talk while recording to add additional context.
- Maintenance: Connect to your tools (GitHub, Asana, Slack, …) and we automatically suggest changes to your docs if your product changes.
- Consumption: Users can consume the content as they like: Read the docs themselves or ask a Q&A bot.
At the moment the creation and consumption parts are already working well. Now I’m working on the maintenance part.