🦜️🔗 The LangChain Open Tutorial for Everyone
Last updated
Last updated
This tutorial delves into , starting from an overview then providing practical examples.
The LangChain community in Seoul is excited to announce the LangChain OpenTutorial, a brand-new resource designed for everyone. This tutorial builds upon the foundation of the existing tutorial available here: written in Korean.
Within this new repository, we offer the following enhancements to benefit users of all skill levels:
Addressing global use cases for international users,
Diving deep into cutting-edge features including the recent updates available at the latest version of LangChain and LangGraph release, and
Demonstrating additional goodies that showcase real-world uses and further applications.
At this base repository, it serves as a home for both beginners and seasoned LangChain users. The tutorial whould provide a roadmap for learning LangChain, while also offering a valuable refresher for those already familiar with its functionalities.
Open a Pull request (PR): Develop at least one existing or new content file (.ipynb). Optionally, add examples related to open LLMs. Then, Submit a PR with the developed content.
- Note: Self-Check Before PR Submission (Recommended)
License Compliance & Copyright Issues: Verify that all dataset and content comply with licensing requirements. Confirm that there are no copyright infringements.
Template Compliance: Follow the provided templates in or in
Execution Platform: Individual files should be executable on Google Colab.
Specifications Submission (if Required): If using open models or additional packages, specify the required environment to Infra Team.
Team Peer Reviews: Assign at least two team members as reviewers. Reviewers will evaluate the code and content quality and check tutorials are compatible with Mac, Windows, and Linux environments. Approve the Pull Request if there are no issues.
Merge Pull Request: Once the Pull Request has been approved by more than two reviewers, the original author can merge the PR into the 'main' branch.
Proofreading: During the following week, the proofreading team will review the submitted content for typos, template compliance, and proper citations. If the proofreading team requests any modifications, the original author must make the necessary corrections and resubmit the PR.
Minji Kang
Dowoung Kong
Dooil Kwak
Namyoung Kim
Musang Kim
Sunworl Kim
Sungchul Kim
Youngin Kim
Yongdam Kim (codingiscoffee)
Jaeho Kim
Jongcheol Kim
JungWook Kim
Junseong Kim
JoonHo Kim
Taylor (Jihyun) Kim
Taehwan Kim
Harheem Kim
Heeah Kim
Kyusik Moon
Bokyung Moon
HyeonJong Moon
Heesun Moon
Sunyoung Park (architectyou)
Erika Park
Yejin Park
JeongGi Park
Gimin Bae
Injin Bae (Ivy)
Pyoungwon Seo
Joonho Song
HoJun Song
HeeWung Song (Dan)
Aera Shin
Jeongho Shin
Haseom Shin
kkamDragon
Yoonji Oh
Jooyeong Oh
Byunggil Yoon
Kane
Donghakl
Chester (Sangyoon Lee)
Suhyun Lee
Sunhyoung Lee
Wonyoung Lee
YuChul Lee
Jongho Lee
Juni Lee
Chang-Jun Lee
Sohyeon Yim
Mark Lim
Yookyung Jeon
Joonha Jeon
Changwon Jeon
Gwangwon Jung (Pupba)
Wooseok Jeong
Ilgyun Jeong
Youngjun Cho
Jinu Cho
Hwayoung Cha
Ash-hun
Yeonhee Han
Sooyoung Her
Seongmin Hong (Solon)
Jaemin Hong
Chaeyoon Kim
✨ Want to join? Add your info and submit a PR!
📖
Unless stated otherwise, the codebase is released under the . This covers both the codebase and any sample code in the documentation.
