Better developer onboarding

[missytake]

• the forum category is not a good entry point for "example bots". let's call the menu item "forum" instead.
• let's point to the example bots instead: https://github.com/deltachat-bot/echo

[missytake]

Some further ideas for bots.delta.chat from simon, let's go with this:

• [x] Landing page: What are deltachat bots? why are they cool?
• [x] How to deploy an existing Bot
• [x] quickstart -> echo bot: https://github.com/deltachat-bot/bot-pages/pull/45
• [ ] core concepts: setup/configure, send message to new contact, modify a group, react to events (with short example code in multiple languages)
• [ ] (Later) Getting started with simplebot
• [ ] (Later) Guides/Tutorials
• [ ] How we did the "login with deltachat" bot / "how to link your webservice to dc"
• [ ] webxdc enabled example bot
• [ ] .... add more whenever we feel like it, since the tutorials are just markdown with optionaly a bit of javascript we can even use markdown slide generators to make short video tutorials in the style of what "no boilerplate" does with his rust videos (https://www.youtube.com/c/NoBoilerplate)
• [ ] (Maybe) a showcase for existing bots?

[missytake]

I'd add:

• [ ] how to run a python bot with a flask HTTP server, as a subprocess as part of gunicorn (see mailadm)
• [ ] how to run a python account without deltabot (though maybe that should go to py.delta.chat instead)

[missytake]

The current https://bots.delta.chat/development.html page mostly is a description of the core and which bindings you can use to talk to it (a bit outdated maybe). I would rename this page to "Delta Chat APIs" and extend it with the "core concepts" (setup/configure, send message to new contact, modify a group, react to events).