> For the complete documentation index, see [llms.txt](https://handbook.openguild.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.openguild.wtf/hackathon-projects-and-events/hackathon/hackathon-general-information/project-qualification.md).

# Project Qualification

### Tips to make a good Web3 project

* Meet a <mark style="color:yellow;">**complete standard of the UI/UX quality and functionalities**</mark>
* Identify a <mark style="color:yellow;">**clear roadmap**</mark> of the projects&#x20;
* Good <mark style="color:yellow;">**README file**</mark> to demonstrate the application
* A <mark style="color:yellow;">**demo video**</mark> of the project
* Finding <mark style="color:yellow;">**mentors**</mark> from TheLowLevelers community [Elder](/general-information/membership/ranking-system/elder.md) and [Member](/general-information/membership/ranking-system/member.md)

## 📘 Hackathon Project Qualification Guide

### **Preliminary review 50%: (technical dimension)**

1. <mark style="color:purple;">Technical difficulty (20%):</mark> The problem solved has a certain technical threshold and there is a certain breakthrough at the technical level;
2. <mark style="color:purple;">Project completion (20%):</mark> The project is fully realized, not just the concept, and the Demo/POC display is complete;
3. <mark style="color:purple;">Standardization (10%):</mark> The project is submitted within the specified time and the content is standardized.

The preliminary review will mainly review the project's code submission, new features, test improvements, inheritance, deployment, etc. during the hackathon. Submitting a project with a clear history will help the reviewers understand the actual development work of the project.

### **Final 50%: (Business Dimension)**

1. <mark style="color:purple;">Commercial value (20%):</mark> Can solve problems and be used in industry scenarios you know;
2. <mark style="color:purple;">Innovation (20%):</mark> novel ideas, breakthroughs, breaking conventional thinking;
3. <mark style="color:purple;">User experience (10%):</mark> including how intuitive and understandable the submitted solution is to potential users.

The team participating in the demo is determined by the score of the technical preliminary review. After the demo is completed, the review can be adjusted based on the situation of the demo and the actual developed functions.