<FAQ/>

No. The WebForge is designed to be approachable for participants who are still learning. The preparation workshops introduce the development workflow and the tools used throughout the event.

No. You should be willing to learn, experiment, solve problems, and work with your team. AI is intentionally part of the development process.

University students who complete registration may participate. Final eligibility details are confirmed by the organizers before the event.

A laptop, charger, and access to the email and development accounts you plan to use. Install a modern browser, Visual Studio Code, Git, and Node.js in advance.

No. Participants without a team can use the team formation process to create or join one.

Yes. You may register alone, and the team-formation process can help you join or create a team.

A team may include the primary registrant and up to ten additional member email addresses. Only registered team members may collaborate on the competition solution.

Request team changes through the organizer contact form before competition day. Changes are valid only after organizers confirm the updated roster.

Yes. AI may generate part or all of your application. There is no requirement to manually write a specific percentage of the code.

Yes. Standard paid consumer AI plans such as ChatGPT Plus are allowed. The highest-tier or advanced premium plans, such as ChatGPT Pro, are not.

Participants are not restricted to one AI provider. The same access principle applies: free and standard paid consumer tiers are permitted, the highest-tier or advanced premium access is not. If unsure about a specific plan, ask an organizer.

Your team is responsible for the final application. If something breaks, you must be able to investigate the problem, direct your tools toward a solution, test the result, and verify that the application works.

Day 01 covers planning and the development workflow. Day 02 covers full-stack development and debugging. Day 03 covers deployment, domains, search discovery, and performance. Together they walk through the same workflow used on competition day.

Attendance is strongly recommended, because the competition assumes familiarity with the full workflow. Participants remain responsible for the published presentation material and the handout checklists before competition day.

All three workshop days are developed and taught by Shoug Alomran.

That is part of the challenge. Teams receive the official application brief when the challenge is released on competition day.

No. Teams may prepare and practice, but may not begin building a solution for the competition challenge before it is officially released.

Teams should be prepared to adapt during the competition.

No. Competing teams may not share challenge-specific code, prompts, solutions, debugging fixes, implementation details, or strategies during the competition.

Yes. The final application must be publicly accessible for judging, deployed and connected to a domain or subdomain.

No. The judged submission may not be modified after the official deadline unless organizers explicitly authorize it.

Out of 100 points across seven categories: functional completeness, technical implementation, problem solving and adaptability, UI/UX, system understanding, production readiness, and the final demonstration.