[Roadmap] Documentation and Training

[jackgerrits]

[!TIP]

Want to get involved?

We'd love it if you did! Please get in contact with the people assigned to this issue, or leave a comment. See general contributing advice here too.

This roadmap is for our documentation effort. Point of Contact: @ekzhu @jackgerrits

There are two types of tasks: content tasks, and utility tasks.

### Content Tasks
- [ ] Azure Sample: AutoGen Tutorial: https://github.com/Azure-Samples/autogen-tutorial
- [ ] User Guide: Group Chat https://github.com/microsoft/autogen/issues/2243
- [ ] User Guide: Multi-Modal https://github.com/microsoft/autogen/issues/2142
- [ ] User Guide: Teachability 
- [ ] User Guide: RAG
- [ ] User Guide: Streaming
- [ ] User Guide: Logging and Observability https://github.com/microsoft/autogen/issues/2146
- [ ] User Guide: System Design https://github.com/microsoft/autogen/issues/1351
- [ ] User Guide: Complex Workflows https://github.com/microsoft/autogen/issues/2015
- [ ] Notebooks: https://github.com/microsoft/autogen/issues/2139
- [ ] Gallery: Replaced default images, invite community contributions
- [ ] Notebooks: audit notebooks for consistency of installation/config instructions
- [ ] https://github.com/microsoft/autogen/pull/2071
- [ ] https://github.com/microsoft/autogen/issues/2465

### Utility Tasks
- [ ] Notebook testing in CI
- [ ] Notebook gallery browsing page with interactive views.
- [ ] https://github.com/microsoft/autogen/issues/1339
- [ ] https://github.com/microsoft/autogen/issues/2032
- [ ] https://github.com/microsoft/autogen/issues/2048
- [ ] Align on docstring style and lint with ruff
- [ ] Enable testing of more notebooks
- [ ] Better categorization of notebooks page

Discord channel for discussion around documentation

[jackgerrits]

@davorrunje are you interested in working on any of the content around tool use?

[rickyloynd-microsoft]

Thanks Jack. I can cover documentation for Capabilities and Teachability.

Ricky

[davorrunje]

@davorrunje are you interested in working on any of the content around tool use?

@jackgerrits yes, I am. One thing: I have a fiver and will be offline for a few days. Some kindergarten virus is in the house 🤷‍♂️

[jackgerrits]

@davorrunje are you interested in working on any of the content around tool use?

@jackgerrits yes, I am. One thing: I have a fiver and will be offline for a few days. Some kindergarten virus is in the house 🤷‍♂️

No worries at all! I hope you feel better soon

[davorrunje]

@davorrunje are you interested in working on any of the content around tool use?

@jackgerrits yes, I am. One thing: I have a fiver and will be offline for a few days. Some kindergarten virus is in the house 🤷‍♂️

No worries at all! I hope you feel better soon

I am back. What's the plan? How to start with this?

[jackgerrits]

The idea is to create "topic docs", so the purpose is to explain more than to provide an example is as the case with notebooks. You can see an example of the style here.

For tool use one idea is to have a general page that outlines the concept of tool use and enumerates the different possible places in autogen that this is relevant (function map, web surfer agent, code execution etc). I am open to ideas about what you think is best for how to present this info

[gagb]

@jackgerrits @ekzhu should we putting logging on the agenda?

[jackgerrits]

Yeah definitely, we should add topics when we think of them. Please feel free to add logging where it makes sense

[nitya]

Hi folks - had created this markmap to help me navigate Autogen in a more cohesive way - and was encouraged to share feedback here so wanted to weigh in on the thread.

This was how I saw the docs being organized in my head, from the perspective of a developer journey where they need to go from core concepts to a quickstart to understanding tools for productivity before getting recipes for doing various specific tasks.

Would love to contribute feedback and/or content to shape the docs if you find it helpful.

I've also found this a useful way to identify gaps in the journey and to find out areas that developers are likely not aware of because the relevant documentation is buried elswwhere (e.g., in a blog post or in the github subfolder readme) - this helped me frame the big picture before diving in.

[rysweet]

@gagb @jackgerrits @ekzhu - how much of this is still needed?

[jackgerrits]

I think this can be closed as it is either stale or captured in new issues.