0% found this document useful (0 votes)
18 views3 pages

67e80b0cde01f CodeForge Prototype Submission Guidelines

The Code Forge Hackathon provides detailed guidelines for prototype submissions, emphasizing the importance of understanding the challenge, clear communication, and originality. Participants must create a public GitHub repository with a comprehensive README file that includes project details, dependencies, and setup instructions, and submit their projects between March 30th and March 31st, 2025. Additional tips highlight the value of video demos, concise descriptions, and early submissions to enhance the chances of success.

Uploaded by

mygames8520
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views3 pages

67e80b0cde01f CodeForge Prototype Submission Guidelines

The Code Forge Hackathon provides detailed guidelines for prototype submissions, emphasizing the importance of understanding the challenge, clear communication, and originality. Participants must create a public GitHub repository with a comprehensive README file that includes project details, dependencies, and setup instructions, and submit their projects between March 30th and March 31st, 2025. Additional tips highlight the value of video demos, concise descriptions, and early submissions to enhance the chances of success.

Uploaded by

mygames8520
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Code Forge Hackathon: Prototype Submission Guidelines

General Guidelines:

●​ Understand the Challenge: Before diving in, make sure you fully understand the
hackathon's theme, objectives, and judging criteria. Tailor your project to align with
these.
●​ Early and Often: Don't wait until the last minute. Start early, build incrementally, and
test frequently. This will help you avoid last-minute crises.
●​ Clear Communication: If you have any questions or need clarification, don't hesitate
to reach out to the organizers.
●​ Original Work: Ensure that the code you submit is primarily your own. If you use
external libraries or resources, properly credit them. Plagiarism will result in
disqualification.
●​ Focus on Functionality: While a polished UI is nice, prioritize a functional prototype
that demonstrates your core idea.
●​ Code Quality: Even though it's a hackathon, try to write clean, readable, and
well-commented code. This makes it easier for judges (and yourself) to understand.

Specific Prototype Submission Guidelines:

1. GitHub Repository & README File

●​ Repository Link: Your project submission must include a link to your GitHub
repository. Ensure the repository is public or accessible to the judges.
●​ README File Requirements: The README file is critical. It should include the
following:

○​ Project Overview:
■​ A concise and compelling description of your project's purpose and
functionality.
■​ Explain the problem your project solves.
■​ Highlight the key features and benefits.
○​ Dependencies:
■​ A comprehensive list of all software libraries, packages, frameworks,
or tools required to run your prototype.
■​ Specify the version numbers of each dependency (e.g., Python 3.9,
requests==2.28.1). This avoids compatibility issues.

○​ Setup Instructions:
■​ Detailed, step-by-step instructions on how to install, configure, and run
your project.
■​ Include commands to install dependencies (e.g., pip install -r
requirements.txt).
■​ Provide any necessary configuration steps (e.g., setting environment
variables, creating configuration files).
■​ Include instructions on how to start the application.
■​ If applicable, show how to use the basic features of your project.
■​ Example commands or screenshots can be very helpful.

○​ Additional README Suggestions


■​ Team Member Information: If you're part of a team, list the names
and roles of each member.
■​ License: Specify the license under which your code is released (e.g.,
MIT License, Apache 2.0).
■​ Contribution Guidelines: If you want others to contribute, add
information on how to contribute to the project.
■​ Future Plans: Briefly mention any planned future development or
improvements for the project.

2. Important Dates

●​ Prototype Round: Actively refine and improve your prototype during the active
Prototype Round on Unstop.
●​ Final Submission Window: Submit your project to DoraHacks between March
30th, 2025, and March 31st, 2025.
●​ Late Submissions: Submissions received after the deadline will not be accepted.
Plan accordingly.

3. How to Submit on DoraHacks (Here is the reference video - Link)

●​ DoraHacks Account: Ensure you have a registered account on the DoraHacks


platform. If you are on a team, make sure all team members are registered on
DoraHacks.
●​ Find the Hackathon: Locate the "Code Forge Hackathon" on the DoraHacks
platform (Link). Often, there's a dedicated page for the specific hackathon.
●​ Submission Form: Find the "Submit BUIDL" on the hackathon page. This will lead
you to the submission form.
●​ Form Fields: Carefully fill out all required fields in the submission form. This typically
includes:
○​ Project Name: The name of your project.
○​ Team Name: (If applicable)
○​ GitHub Repository Link: This is crucial! Double-check that the link is correct
and accessible.
○​ Project Description: A brief summary of your project (you can often copy
this from your README).
○​ Demo Video Link (if required/recommended): Consider creating a short
(1-2 minute) video demonstrating your project. Upload it to YouTube (unlisted
is fine) or another video hosting service and include the link in the
submission. This is often highly recommended.
○​ Other Information: There may be other fields specific to the hackathon (e.g.,
technologies used, target audience, impact). Answer them accurately and
thoughtfully.
●​ Submission Confirmation: After submitting the form, you should receive a
confirmation message or email. Save this confirmation for your records.

DoraHacks Submission Tips (from the video, generally):

●​ Video Demo: A short video goes a long way. Judges often review many projects,
and a well-made video can quickly showcase your project's key features and
benefits. Show, don't just tell.
●​ Clear and Concise: Be clear and concise in your descriptions. Judges appreciate
brevity.
●​ High-Quality Screenshots: Include relevant screenshots of your project in action,
especially in your README.
●​ Test Your Submission: Before submitting, double-check all links and information to
ensure everything works correctly.
●​ Submit Early: Don't wait until the last minute to submit. This gives you time to fix any
issues that may arise.

By following these guidelines, you'll significantly increase your chances of a successful


submission and a positive experience at the Code Forge Hackathon! Good luck!

You might also like