Ai & Web Programming Challenge

Participants may enter individually or as a team.

•  A team may have no more than four participants, including the Team Leader.

•  Each participant may be registered as a member of only one team in the challenge.

•  One participant must be designated as the Team Leader and will serve as the official contact for the team.

•  Changes to the registered team after the submission deadline require written approval from the organizing committee.

The official competition challenges will be published on the website on 15 October. Teams must review the published descriptions and select one challenge in the Project Submission Form. The submitted project must address the selected challenge directly and comply with any specific technical or content requirements stated in that challenge.

•  A team may submit one project unless the organizing committee gives written permission otherwise.

•  A project must remain within the scope of the selected challenge.

•  The selected challenge cannot be changed after the project-submission deadline without written approval.

Challenge 1: 

Interactive Museum

A modern museum wants an interactive website where visitors can virtually explore different sections of the museum and discover exhibits.

The goal is for the site to be more than just an introductory page; it should create an experience similar to a digital museum for the user.

Main Challenge Goal

Design and implement a fully frontend Digital Museum using HTML, CSS, and JavaScript, where user experience, animation, and interactions play the main role.

Participants’ Tasks

• 1. Design a homepage for the museum that introduces its different sections.

• 2. Create at least 4 different sections/galleries, for example:

• a – Ancient History

• b – Science

• c – Art

• d – Future

• 3. Each gallery should contain several exhibits.

• 4. Clicking on any exhibit should open an interactive page or Modal displaying information about that exhibit.

• 5. Add Filter and Search functionality for exhibits.

• 6. Design interactive Navigation so users can move between the different sections.

• 7. Use CSS Animation and Transition in a meaningful way.

• 8. The site must be fully Responsive, with an appropriate and distinct experience on mobile and Desktop.

Challenge 2:

Escape Room

Participants have entered a digital laboratory whose security system has been locked. To escape, they must solve a series of puzzles and logic codes in a Web Application.

Main Goal

Build a web-based Escape Room with different stages, puzzles, a Timer, scoring, and a progress system.

Participants’ Tasks

• 1. Build an interactive environment for the Escape Room.
• 2. Design at least 5 different stages.
• 3. Each stage must have a different type of Puzzle.
•  

Examples:

• – Decryption
• – Finding patterns
• – Sorting information
• – Finding relationships between data
• 4. The next stage should unlock only after the previous stage has been solved.
• 5. The system should include Hints.
• 6. Use JavaScript for Puzzle interactions.
• 7. The system must have a Timer.
•  

Scoring should be based on:

• – Time
• – Number of Hints
• – Number of Attempts

Challenge 3: 

Build Your Own Mini Wikipedia

A scientific community wants to collect its knowledge and articles in an online encyclopedia, but any user can modify articles, and some changes must be reviewed by other people.

The team must design a system that manages change history and collaboration between users.

Main Goal

Build a Knowledge Platform with simple Version Control, Review, and Collaboration.

Participants’ Tasks

• 1. Users should be able to create an article.
• 2.  Each Article should have:
• – Title
• – Content
• – Category
• – Author
• – Created Date
• – Updated Date
• 3. Users should be able to Edit an Article.
• 4. Each Edit must create a new Version.
•  

For example:

• – Version 1
• – Version 2
• – Version 3
• 5. Users should be able to view previous Versions.
• 6.  Users should be able to compare two Versions.
•  

For example: Version 2 vs Version 3

The system should display the parts that have changed.

• 7. Users should be able to leave a Comment.

• 8. Users should be able to Report an Article.

Challenge 4 : 

Auction Arena

An online auction platform is going to hold a live auction. Several people place bids on a product, and each bid can change the state of the competition.

The team must build a system that manages auction logic reliably.

Main Goal

Build an Auction system with bidding logic, timing, and bid management.

Participants’ Tasks

• 1. The Admin should be able to create an Auction.

• 2. The following should be specified for each
•  

Auction:

• – Product
• – Starting Price
• – Minimum Bid Increase
• – Start Time
• – End Time
• 3. Users should be able to submit a Bid.
• 4. A Bid must be higher than the current highest bid.
• 5. Every new Bid must be saved.
• 6. The system must have a Bid History.
• 7. The remaining Auction time must be displayed.
• 8. When the time runs out, the system must determine the Winner.
• 9. Users should be able to view their previous Auctions.
• 10. Invalid Bids must not be entered into the Database.
• 11.  As much as possible, the system must prevent inconsistent states when bids are submitted simultaneously.
•  

Challenge 5:

Smart Marketplace

A local Marketplace wants to create a platform where sellers can sell their products and buyers can place orders.

However, the system must be able to manage inventory, orders, discounts, shipping status, and user behavior.

Main Challenge Goal

Build a multi-vendor Marketplace with a Backend and Database.

Participants’ Tasks

• 1. Authentication.

• 2. The following Roles:

• – Customer
• – Seller
• – Admin

• 3. The Seller should be able to:

• – Create a Product
• – Edit a Product
• – Set a price
• – Set inventory

• 4.  The Customer should be able to:

• – Search for Products
• – Filter Products
• – Add products to the Cart
• – Change product quantity

• 5. Inventory must be checked during Checkout.

• 6. After an order is placed, inventory must decrease.

• 7. Create an Order.

• 8. An Order must have a status:

• – Pending
• – Confirmed
• – Preparing
• – Shipped
• – Delivered
• – Cancelled
•  

Challenge 6: 

Smart Campus

A university has realized that students must constantly search across several different systems to find classes, events, facilities, and university services.

Your team must design an intelligent, integrated portal for managing and using university services.

Main Challenge Goal

Build a Web Application to manage university information and provide various services to students.

Participants’ Tasks

• 1. Create a user registration and login system.

• 2. Define different Roles, such as:

• – Student
• – Teacher
• – Admin

• 3. Build a dedicated dashboard for each user type.

• 4. Create a class management system with:

• – Course name
• – Instructor
• – Time
• – Room
• – Capacity

• 5. Students should be able to register for a class.

• 6. Prevent registrations from exceeding a class’s capacity.

• 7. Build a class Search and Filter system.

• 8. Build a page for university events.

• 9. Allow students to register for Events.

• 10. Build an Admin panel to manage users, classes, and Events.

•  11. Use an SQL Database to store all information.

• 12. Create a Responsive design using HTML/CSS.

• 13. Use JavaScript for interactions without Reloading parts of the website.

Challenge 7: 

The Last Will: Digital Inheritance

A wealthy individual has placed their assets and important documents in a digital system before death, but access to them is granted according to a set of specific rules and conditions.

Family members, lawyers, and the asset manager must be able to submit and review requests, but no one should be able to access the assets outside the defined rules.

Main Challenge Goal

Build a Full-Stack system for managing digital assets, inheritance, access requests, and the execution of asset-transfer rules.

The system must be able to determine who has access to what, and under which conditions.

Participants’ Tasks

• 1. Create a complete Authentication system.
•  

At least the following Roles:

• – Owner
• – Beneficiary
• – Lawyer
• – Administrator
•  

• 2.  The Owner should be able to register their assets.
•  

For example:

Asset: House

Value: €250,000

Owner: John

• 3.  The Owner should be able to assign one or more Beneficiaries to each Asset.
•  

For example:

House → Alice 60%

House → Bob 40%

• 4.  The system must check that the total shares do not exceed 100%.

• 5. The Owner should be able to define a Rule for transferring each Asset.

Beneficiary must approve

AND

Lawyer must verify

• 6. The Beneficiary should be able to submit a request to receive an Asset.

• 7. The request should enter a Workflow:

Pending

→ Under Review

→ Approved

→ Executed

Or:

Rejected

• 8. The Lawyer should be able to review requests and verify the required documents.

• 9. The system must have Permission controls.
• 
  

For example, a Beneficiary must not be able to:

• – Create an Asset
• – View another person’s Asset
• – Change another person’s share
• – Approve their own request
•  

• 10. All important operations must be stored in an Audit Log.