Scribd
Upload
3 views

Web Dev Rules

The Web Development Competition requires teams to create a web application based on a theme announced at the start, with a 24-hour duration for development and presentations. Teams must consist of 1 to 3 undergraduate participants, use their own machines, and adhere to specific rules regarding frameworks and originality. Evaluation will focus on ideation, functionality, design, technical implementation, and presentation quality, with strict penalties for non-compliance.

Uploaded by

harismasood012
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
3 views

Web Dev Rules

The Web Development Competition requires teams to create a web application based on a theme announced at the start, with a 24-hour duration for development and presentations. Teams must consist of 1 to 3 undergraduate participants, use their own machines, and adhere to specific rules regarding frameworks and originality. Evaluation will focus on ideation, functionality, design, technical implementation, and presentation quality, with strict penalties for non-compliance.

Uploaded by

harismasood012
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

WEB DEVELOPMENT

GUIDELINES
Web Development Competition
Competition Overview:

• Each team would be given a theme, and they would need to implement their ideas to
solve that problem with a web application
• The theme would be announced to all the participants when the competition starts.
• The duration of the competition is about 24 hours (including presentations)
• Teams must bring their own machines.
• The Internet/Extensions will be provided; however, participants are requested to bring
their own internet to avoid any sort of inconvenience.
• Day 1: The competition starts at 2:30 PM sharp. Teams must be present in the assigned
room (details will be shared). Teams may leave after 5:00 PM and continue working
from home.
• Day 2: Teams must report back by 10:00 AM at the venue. Code submission will be
followed by evaluations and presentations.
Competition Rules:

• Teams can use any frontend and backend frameworks of their choice. But,
o Using WordPress isn’t allowed.
o Firebase or any other Backend as a Service is allowed but custom backends
will be given more points.
• Both SQL and No SQL databases can be used depending on the design choice.
• Functionality will be tested in a 10–15-minute evaluation of the working website to the
judges.
• Participants are required to be there at the time of evaluation. Failure to appear before
the judge at the time of evaluation will automatically disqualify the project from the
competition.
• Teams should bring their own converters for the projectors so that their presentations
can go smoothly.
• The decision of the Judges will be final and cannot be challenged. If any team keeps
arguing with the host team on this matter, they will be disqualified.
• All work must be original and completed exclusively by the registered team members.
• Plagiarism of all kinds is strictly prohibited.
• No deadline extensions will be provided, regardless of technical issues.
Team Eligibility Criteria:

• Each team should consist of a minimum of 1 and a maximum of 3 participants.


• Participants must be enrolled in an undergraduate degree program.

Evaluation Criteria:

• Ideation & Innovation


o Originality & Creativity
o Purpose & Impact
• Functional Completeness
o Core Requirements: All mandatory features implemented and fully
functional.
o Edge Cases & Error Handling: Graceful handling of invalid inputs, errors, and
unexpected scenarios.
• Visual Design & User Experience
o Responsiveness: Mobile, tablet, and desktop screens.
o Consistency: Consistent (colors, fonts, spacing), adherence to design
systems.
o Visually Appealing
• Technical Implementation
o Frontend Code: Clean, modular code with proper separation of concerns
o Backend Architecture: Clean, modular code with proper separation of
concerns. Error logging and input validation.
• Best Practices
• Presentation & Documentation
o Documentation: README with setup instructions, code comments
o Demo Effectiveness: Structured pitch and Live demonstration of key
features.

You might also like