-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AutoGen Tutorial #1702
AutoGen Tutorial #1702
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1702 +/- ##
=======================================
Coverage 37.09% 37.09%
=======================================
Files 64 64
Lines 6834 6836 +2
Branches 1502 1502
=======================================
+ Hits 2535 2536 +1
- Misses 4082 4083 +1
Partials 217 217
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@ekzhu We currently have two notebooks on teachability. Are they sufficient for the tutorial? https://github.com/microsoft/autogen/blob/main/notebook/agentchat_teachability.ipynb |
Do we duplicate notebooks in notebooks/ and Tutorials/ ? |
The proposed structure is a bit different to what we have on the roadmap - do you want to update the issue to reflect? #1597 |
Perhaps. I am not sure at this point. The goal is for the tutorial notebooks to be rendered as webpages. So it should be inside the “website” directory? Also, I think it won't be duplicate because the tutorial should have a coherent flow. |
Right. I was thinking about making the tutorial shorter but making the detailed topics more “flat”. I can update the issue page if you agree with the layout here. |
Thanks! I think I can take them and combine them into one notebook and add some context, so it blends into the tutorial as a whole. So the tutorial version of teachability notebook is going to be different from the notebooks version of the notebook. |
Rendering them as webpages doesn't require the original notebook to be under the website. The current notebooks are renderable as long as they follow the guide. |
I think the tutorials should be website pages first and foremost. Notebooks under notebook/ are just rendered on the website under a big list of notebooks. However, for the docs we are putting more effort into we want to make sure the left navbar makes sense and represents a logical progression of teaching. So I agree with these tutorials being added under website/ |
Organize tutorials under getting started section
Break down chapter 2
Edits for tutorial
Is there any info about |
* update intro * update intro * tutorial * update notebook * update notebooks * update * merge * add conversation patterns * rename; delete unused files. * Reorganize new guides * Improve intro, fix typos * add what is next * outline for code executor * initiate chats png * Improve language * Improve language of human in the loop tutorial * update * update * Update group chat * code executor * update convsersation patterns * update code executor section to use legacy code executor * update conversation pattern * redirect * update figures * update whats next * Break down chapter 2 into two chapters * udpate * fix website build * Minor corrections of typos and grammar. * remove broken links, update sidebar * code executor update * Suggest changes to the code executor section * update what is next * reorder * update getting started * title * update navbar * Delete website/docs/tutorial/what-is-next.ipynb * update conversable patterns * Improve language * Fix typo * minor fixes --------- Co-authored-by: Jack Gerrits <[email protected]> Co-authored-by: gagb <[email protected]> Co-authored-by: Joshua Kim <[email protected]> Co-authored-by: Jack Gerrits <[email protected]>
Why are these changes needed?
Create a tutorial that covers the basic concepts of AutoGen, and expand to detailed topics.
Tutorial structure:
Table of content (displayed on the sidebar)
Related issue number
#1597
Checks