Welcome to Devlynix Buildathon 1.0, an asynchronous, weekend-long mini-hackathon designed specifically to help you transition from watching tutorials to building practical, real-world projects. This hackathon focuses on the "Idea-to-MVP Sprint" model. We aren't looking for perfect code; we are looking for strong problem-solving, clean design, and a solid technical approach.

⚠️ IMPORTANT: MANDATORY STEP All official announcements, squad formations, and shortlisting results will be shared EXCLUSIVELY on our WhatsApp handles. Joining both is mandatory for participation. 👉 Join our WhatsApp Channel: https://whatsapp.com/channel/0029VbCzGzaJpe8chzjL0w1F 👉 Join our Community Group: https://chat.whatsapp.com/EJrdn43jObx00BKnp444Rj

​📅 Event Overview

Format: 48-Hour Asynchronous Online Hackathon Team Size: 1 to 4 Members per Squad Goal: Build a Minimum Viable Product (MVP) addressing specific community tech challenges.

🛠️ The Challenge: Choose Your Problem Statement

Squads must select one of the following real-world challenges to solve. Your goal is to build a functional MVP with a clean User Interface.

1. The Developer Proof-of-Work Platform 🚀 Many developers build great projects but lose them in scattered GitHub repositories. Build a centralized showcase directory where developers can host their deployed projects, tag their tech stack, and attach demo videos. Include filtering options (e.g., MERN, Web3, AI) for easy discovery.

2. The "Execution-First" Accountability Tracker 🔥 Students often get stuck in "tutorial hell." Build a web dashboard that tracks a user's daily or weekly "build streak" based on actual project execution. The app should prompt users with "What did you code today?", visualize their consistency, and reward them with milestones.

3. The Skill-Based Teammate Matchmaker 🤝 Finding the right teammates for hackathons or side projects is a major hurdle. Design a user-directory system where individuals can create profiles highlighting their specific skills (e.g., UI/UX, React, AI) and proficiency levels. Implement a search and filter mechanism to connect users.

4. The Crowdsourced Learning Vault 📚 The internet is flooded with scattered resources. Build an organized, community-driven resource hub where users can submit and categorize high-quality links, tools, and guides. Include an upvote/downvote system so the best resources naturally rise to the top.

5. The Micro-Event & Submission Portal 🎯 Small tech communities struggle to manage asynchronous events through chaotic group chats. Create a streamlined event dashboard displaying hackathon details, rules, and deadlines. It must feature a dedicated submission portal where teams can upload their final deliverables.

🎯 What You Need to Submit (The Deliverables)

To successfully complete the hackathon, your squad must submit the following three items:

1. The Website MVP (Minimum Viable Product)

Build What You Can: If you are a beginner, building just a clean, functional frontend MVP is completely fine. If you have the skills, you are highly encouraged to build the full-stack version (Frontend + Backend/Database)!

Note: Even if you only build the frontend, integrating a simple AI API or explaining how your backend would work in your PPT will earn you extra points.

2. The Presentation (PPT)

Create a short, simple presentation (Google Slides/Canva/PowerPoint). It must include:

The Problem: What specific issue are you solving? The Solution: How does your app fix it? Tech Stack: What technologies did you use (or plan to use)? Future Scope: How can this app grow in the future?

3. The Pitch Video (Max 10 Minutes)

This is your final presentation! Record your screen and your voice. How to do it: Walk us through your PPT first, and then give a live demo of your Website MVP. The Vibe: Be confident! Explain your thought process, why you designed the UI a certain way, and how the code logic works.

📅 Buildathon 1.0: Official Timeline

Phase 1: Registration & Concept Submission Date: 4th May Duration: 24 Hours Task: Register your team on Devfolio and submit your project idea/problem statement. Deadline: 4th May (11:59 PM) Note: Teams will be shortlisted tonight for the building phase.

Phase 2: The 48-Hour Build Sprint Date: 5th May – 6th May Duration: 48 Hours Task: Start coding your MVP (Minimum Viable Product). This is the main development phase where you build your frontend/full-stack solution. Submission: Keep your GitHub repository updated throughout these 48 hours.

Phase 3: Final Submission & Video Pitch Deadline: 6th May (Before 12:00 Midnight) Final Deliverables: 1. Complete GitHub Repository URL. 2. Presentation (PPT) Link. 3. Final Video Demo (Max 10 Minutes).

Important: The Devfolio submission portal will automatically close at 11:59 PM on 6th May.

📅 Important Instructions for Participants:

Single Dashboard: You will use the same Devfolio project dashboard to update your progress in each round.

Strict Deadlines: Submissions after the round deadline will lead to automatic disqualification.

Communication: All shortlisting announcements will be made via the official Devlynix WhatsApp group and Devfolio notifications.

📊 Evaluation Criteria

Judges will evaluate your submissions out of 100 Points based on these 4 pillars:

Problem-Solution Fit (25 Points): How practical and realistic is your solution? UI/UX & Design (25 Points): Is the layout user-friendly, clean, and adhering to the 'Silent Coder' aesthetic? Technical Logic (25 Points): How functional is the code, or how clearly is the technical architecture defined? The Final Pitch (25 Points): How well was the product explained and demonstrated in the video?

Get ready to build. Good luck, Squads! Let's build something awesome. 🛠️🔥