TEN-framework / TEN-framework/ten-framework

[2026NewYearChallenge 🏅] Improve TEN Documentation & Guides

Open
#1,970 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

2026-new-year-challenge-1-point
Dominant language
Python
Stars
11.1k
Forks
1.4k
Avg merge
2d 15m
Merged PRs (30d)
22

Description

This is an issue for the 2026 New Year Challenge – 5 Projects United Hackathon, co-hosted with memU, OpenAgents, Sealos, and Zeabur, with a $600 prize pool.

Full challenge website and rules: https://memu.pro/hackathon/rules/tenframework
Submission form:
👉 https://forms.gle/wtX8YWH1tcjenmM68
Period: Jan 8, 00:00 PT – Jan 18, 00:00 PT

💡 What to Contribute
Create or improve documentation, tutorials, and developer guides for TEN Framework to help developers get started faster and build better real-time voice agents.
Submissions can be new docs or improvements to existing documentation.
Suggested Documentation Directions (but not limited to):

  1. From-scratch tutorials
  2. Usecase Walkthrough
  3. Existing doc bug fix & improvments

📌 PR Requirements

  • Meaningful documentation improvements
  • Clear explanations of core concepts
  • Consistent and explicit repository references
  • Since English is our primary documentation language, your pull request should focus on updating the English docs.

🔍 Review Criteria

  • Usability

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's existing English documentation and the challenge directions in this issue. Choose a specific tutorial, use-case walkthrough, or documentation improvement, and consider the work complete when it provides clear explanations and consistent repository references in a submitted pull request.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.