Key Dates (Save them on your calendars 📅):

1 December - 19 December 21 December (Extended): Register for the Coding Challenge and start hacking!

4 December: Submission opens at 1200 (GMT +8)

21 December: Submission closes - remember to submit your projects before or on 2359 (GMT +8)

23 December - 26 December: Judging period

27 December: Winners announcement. All winners will receive an email notifying them of their win.

Submission Requirements For Start Building Challenge Statement

One must submit at least a fully working prototype of their project and you will need to submit all of the following submission artefacts.

Submit the link to your GitHub repository. The repository should contain:

• README. A write-up with no more than 500 words explaining how this tool works and why users should adopt this tool. You must include a video demo showing how your completed product works in the README. It should also contain instructions on how to build, install and run the tool or application.
• Source Files. These files can be built locally and can be used by anyone.
• Your Discord and/or X handle, so that we may tag winners in an announcement.

⚠️ Any INCOMPLETE or PLAGIARISED submission will be DISQUALIFIED.

Submission Requirements For Write A Tutorial Challenge Statement

One must submit a full tutorial and you will need to submit the following submission artefact.

Submit the link to your tutorial. The submission can be:

• A Medium article. This is for users who prefer the feel of Word processors. Sign up if you don't have an account yet.
• A Dev.To article. This is for users who prefer to use Markdown. Sign up if you don't have an account yet.

Lastly, provide your Discord and/or X handle in your tutorial, so that we may tag winners in an announcement.

⚠️ Any INCOMPLETE or PLAGIARISED submission will be DISQUALIFIED.

Judging Criteria For Start Building Challenge Statement

#C1C1/Innovation and Creativity (20%)

• Originality: How unique is the submission? Does it introduce new concepts or approaches?
• Ingenuity: How effective does the project solve or address the problem?

#C1C2/Impact and Value (25%)

• Relevance: How related is the project towards the selected category?
• Value: Does the project provide value or benefits to its intended audience or industry?
• Positive impact: What kind of positive impact does this project have to its target industry?

#C1C3/Functionality and Usability (30%)

• MWE (minimal working example): Is the project functional? Are there any bugs or issues?
• User Experience: How intuitive and easy is it to use the project for its target audience or users?

#C1C4/Pitching (10%)

• Presentation and Clarity: How clear are the project goals in terms of finding solutions and creating an impact?
• Demonstration: How well was the project demonstrated using various mediums such as a README or a video presentation?

#C1C5/Extensibility and Potentiality (15%)

• Potential: Does the project have the potential to grow bigger and scale?
• Extensibility: How extensible is the project that it can be used outside from its target use cases?

#C1C6/Complexity and Simplicity (Bonus)

• Logic: How complex or how simple is the code logic of the project?
• Integrations: How integrated are the third-party functionalities does this project have to make it fully functional?
• Reasonable: Does the complexity or simplicity make sense for the project?

Judging Criteria For Write A Tutorial Challenge Statement

#C2C1/Clarity and Structure (25%)

• Introduction: Does the tutorial introduce the topic clearly and explain the objective to the reader?
• Logical Flow: Are the steps presented in a coherent, easy-to-follow manner? Is there a natural progression from one step to the next?
• Headings and Subheadings: Are headings used effectively to break down content into digestible sections?
• Conciseness: Is the tutorial clear without unnecessary detail? Does it avoid jargon or overly complex language, especially for beginners?

#C2C2/Technical Accuracy and Depth (25%)

• Correctness: Is the content technically sound and factually accurate? Are the explanations and instructions free from errors?
• Depth of Coverage: Does the tutorial address the topic in sufficient depth? Does it include not only the basics but also advanced or nuanced details when appropriate?
• Practicality: Are the instructions practical and actionable, guiding readers to a tangible outcome?

#C2C3/Engagement and Readability (20%)

• Engaging Style: Is the tutorial engaging and easy to read? Does the writing style captivate the reader without being too dry or too casual?
• Tone: Is the tone appropriate for the target audience? (e.g., formal vs. informal, instructional vs. conversational)
• Audience Awareness: Is the tutorial written with a clear understanding of the reader’s skill level? Are terms explained if they may be unfamiliar to beginners?

#C2C4/Visuals and Examples (15%)

• Use of Visual Aids: Are visual aids (images, screenshots, diagrams) included to enhance understanding? Are they clear and high-quality?
• Code Examples (if applicable): Are code snippets (if relevant) clearly formatted and explained? Do they work as intended, and are they relevant to the tutorial’s content?
• Illustrative Detail: Are the visuals and examples detailed enough to clarify complex concepts or steps? Are they well-captioned or annotated?

#C2C5/Creativity and Innovation (10%)

• Unique Approach: Does the tutorial present a unique or innovative approach to the subject matter?
• Creative Problem-Solving: Does the tutorial demonstrate creative ways to overcome challenges or explain difficult concepts?
• Engaging Learning Methods: Does the tutorial incorporate interactive or creative elements (e.g., quizzes, exercises, alternate approaches)?

#C2C6/Grammar and Language (5%)

• Grammar and Spelling: Is the tutorial free from grammatical errors, spelling mistakes, and awkward phrasing?
• Language Clarity: Is the language clear and accessible? Are instructions easy to follow without ambiguity?

#C2C7/Practicality and Usefulness (Bonus)

• Actionable Outcome: Does the tutorial provide a clear, actionable outcome or result that readers can apply immediately?
• Real-World Application: Is the tutorial's content applicable in real-world scenarios? Does it help the reader solve an actual problem or accomplish a meaningful task?

Prize Scheme for Start Building Challenge Statement

🌟 A total of USD$500 worth of prizes is up for grabs 🌟

To be rewarded with a prize, become one of the top 5 winners!

• 1st Place will get USD$120 reward.
• 2nd Place will get USD$110 reward.
• 3rd Place will get USD$100 reward.
• 4th Place will get USD$90 reward.
• 5th Place will get USD$80 reward.
• 5 Merit Prize winners will get USD$20.

Prize Scheme for Write A Tutorial Challenge Statement

🌟 A total of USD$200 worth of prizes is up for grabs 🌟

To be rewarded with a prize, become one of the top 5 winners!

• 1st Place will get USD$60 reward.
• 2nd Place will get USD$50 reward.
• 3rd Place will get USD$40 reward.
• 4th Place will get USD$30 reward.
• 5th Place will get USD$20 reward
• 5 Merit Prize winners will get USD$10.

ℹ️ Note: If you are submitting a project with a team, the prize reward will be split amongst all members (e.g. A team of 2 members will have each member receive USD$100 from a USD$200 reward).

Disclaimer: Winning projects or tutorials may be featured in future campaigns at StackUp.