Web Development Guide 15 Practical Projects
Web Development Project Ideas
for Beginners
Choose · Build · Test · Progress
15 projects from HTML websites to full-stack applications, with step-by-step coding examples, test checks and a clear learning pathway.
The learning route
One project at a time. Real skills. Real progress.Quick answer
Which web development project should a beginner build first?
If you are new to web development, begin with a personal webpage or school-club website using HTML and CSS. Next, build something interactive, such as a mathematics quiz, using JavaScript. When you are comfortable working with forms, data and browser events, progress to a project that uses a backend and database, such as a small-shop inventory system. The best project is not necessarily the biggest: it is one you can finish, test, explain and improve.
- Start small
- Write code
- Test results
- Advance gradually
Choose your next project at a glance
Not sure where to begin? Use the Proof it works column as your finish line. You do not need to build all 15 projects. Pick one that matches a skill you are ready to practise, complete its simplest version, and test it before adding new features.
Level (L): 1 = HTML/CSS basics; 2 = JavaScript projects; 3 = full-stack systems. Swipe the table on a phone to see every success test.
| Project | L | Main skills | Proof it works |
|---|---|---|---|
| 1. Personal introduction webpage | 1 | HTML | Your headings, goals and working link appear |
| 2. School-club website | 1 | HTML, CSS | The Meetings link opens the correct section |
| 3. Local business landing page | 1 | HTML, CSS | Services and hours remain readable on a phone |
| 4. Restaurant menu website | 1 | HTML, CSS | Categories and sample prices are easy to find |
| 5. Portfolio website | 1 | HTML, CSS, responsive design | Two completed projects have working links |
| 6. Student grade calculator | 2 | JavaScript, forms | Marks 78, 81, 87 produce an average of 82 |
| 7. Mathematics revision quiz | 2 | JavaScript, DOM, arrays | Correct and incorrect answers produce the right score |
| 8. Personal expense tracker | 2 | JavaScript, browser storage | The total is correct and returns after refresh |
| 9. Searchable library catalogue | 2 | JavaScript, filtering | Searching science shows relevant books only |
| 10. Weather information page | 2 | APIs, Fetch, error handling | A failed request produces a helpful message |
| 11. Small-shop stock system | 3 | Backend, database, validation | Five sold from 20 leaves 15; overselling fails |
| 12. Appointment booking system | 3 | Forms, APIs, database | Two customers cannot reserve the same slot |
| 13. Learning-resource portal | 3 | Authentication, permissions | A learner cannot edit teacher-only material |
| 14. Online shop prototype | 3 | Cart, orders, backend | The simulated order total matches product prices |
| 15. Course-registration application | 3 | Full stack, database, roles | An applicant submits; an authorised staff user reviews |
On a phone, swipe horizontally to view all columns.
The difficulty reflects the features described here. A static page needs fewer moving parts than shared data, accounts or real payments. The intermediate projects assume you have already practised HTML and CSS.
Which project should you choose first?
If you are completely new, build #1 before #2. If you can already write and style a webpage, try #6 to practise JavaScript input and calculations, then #7 to handle multiple questions. After you understand events, arrays and the DOM, build #9 or #10. Attempt #11–15 after you can explain the difference between the browser, an API and a database. Do not skip a level merely because a project name sounds impressive.
Before you start: what do you actually need?
Start with a computer, a web browser and a plain-text code editor. Make a new folder for each project, give your files meaningful names and keep a copy of each working version. You do not need to purchase web hosting to practise the first examples.
Three technologies will carry you through the first ten projects:
- HTML describes the content: headings, paragraphs, navigation, links, images and forms.
- CSS controls the layout and appearance, including how a page adapts to smaller screens.
- JavaScript provides behaviour: responding to buttons, checking answers and changing information on the page.
These are the core foundations used in the [MDN beginner website curriculum][1] and [MDN core learning modules][2]. If those terms are new, read NIT’s guide to HTML, CSS and JavaScript before attempting the interactive projects.
Level 1: Five simple website projects
These projects are good for school learners because they begin with information you already understand. You are creating useful pages, not managing passwords, payments or complicated databases.
Personal introduction webpage
Create a page introducing yourself, your favourite subjects and one skill you would like to learn. Start with a heading, two short paragraphs, an ordered list of goals and a link to a useful learning resource. Add a photo only if you have permission to publish it. Next challenge: add a second page and navigation links between the two.
School-club website
Imagine your science club needs a simple online noticeboard. Build a website showing its activities, meeting place and meeting time. Use this as your first complete practice project; the step-by-step code is below. Next challenge: add a gallery using images that your school has permission to share.
Local business landing page
A tailor, barber or stationery shop in Migori might want customers to see opening hours, services and contact details. Create a fictional business and design a page with those sections. Use sample details, not somebody else’s real phone number. Next challenge: make the services appear in a responsive grid and add a clearly labelled enquiry link.
Restaurant menu website
Build a menu for a fictional café with categories such as breakfast, drinks and snacks. Show each item’s name, description and a sample price in Kenyan shillings. Next challenge: add a print-friendly layout and make the menu readable on a narrow phone screen.
Personal project portfolio
Collect your best two or three projects into one website. For each project, explain what problem it solves, what tools you used, and one difficulty you overcame. Next challenge: link each project to a working public demonstration and its source files. If you can share the finished projects, let visitors open them and read a short note describing what you learned.
Walkthrough 1: Build the school-club website
The problem
Students keep asking when the club meets and what activities it offers.
Version 1 must
show the club name, two activities, a meeting time and links that jump to the correct sections. It should also remain readable on a phone.
- Step 1 — Create a file. Make a folder called
school-club. Inside it, createindex.html. - Step 2 — Add the following complete starter code. You can paste it into
index.htmland open the file in a browser.
- Step 3 — Understand what you wrote. The
headercontains the introduction and navigation.maincontains the information visitors came to read. CSS Grid arranges the two activity cards and changes their layout according to the available width. Thehref="#meetings"link jumps to the section withid="meetings". - Step 4 — Test it. Open the page. Select Meetings: your browser should move to the meeting section. Make the browser window narrower. The cards should stack when there is not enough room for them to sit side by side. Check that the text remains readable and the links work with a keyboard.
- Step 5 — Make it yours. Change the club name, activities and meeting details. If you are publishing the site, first confirm the information and obtain permission for any names or photos you use.
Common mistake: If a navigation link does nothing, compare the word after # in the link with the target section’s id. They must match exactly.
Finished when: another student can find the club activities and meeting details without assistance.
Level 2: Five interactive web projects
Now the website must do something when a person uses it. JavaScript can read values from forms, respond to button clicks and update the browser page without requiring a whole new page load.
Set up your testing environment: The quiz below works with the two files in one folder. For later exercises involving browser storage or network requests, serve your project from localhost rather than relying on a file:// address, whose behaviour can vary by browser. A code editor’s local-preview feature can do this; if Python 3 is already installed, open a terminal in the project folder, run python3 -m http.server 8000 (or py -3 -m http.server 8000 on Windows), and visit http://localhost:8000. [10]
Student grade calculator
Ask the learner to enter three marks and calculate the average. Begin with marks between 0 and 100; reject empty fields and values outside that range. Next challenge: let the user change the weighting for different assessments. Do not label the result an official school grade unless it follows a clearly stated grading policy.
Mathematics revision quiz
Show one question at a time, offer multiple-choice answers and calculate a final score. This teaches arrays, objects, conditional logic and browser events. A complete working example follows. Next challenge: explain why the chosen answer was correct or incorrect.
Personal expense tracker
Imagine a student wants to track transport, lunch and stationery spending. Let them add an expense with an amount and category, then calculate a running total. Add edit and delete functions after the first version works. Browser localStorage can keep small personal practice data between ordinary sessions, but it is specific to the browser and site and should not be treated as secure, shared or guaranteed storage. [4] Next challenge: group spending by category.
Searchable library catalogue
Create an array of fictional books with title, author and subject. Show the list and let the reader filter it by typing into a search field. Next challenge: add a subject selector and a message for searches with no matches. This version is a searchable catalogue, not a complete library borrowing system.
Weather information page
Start with sample weather data so you can finish the page layout. Later, use a weather data provider’s documented API to request information for a selected place. A browser API request made with JavaScript’s fetch() must handle loading, errors and unsuccessful HTTP responses; fetch() does not automatically reject every HTTP error response. [5] Next challenge: show when the information was last updated and explain unavailable data clearly.
Walkthrough 2: Build a mathematics revision quiz
The problem
A learner wants to practise a few mathematics questions and see a score immediately.
Version 1 must
display four questions, accept one answer for each, calculate the score and allow a fresh attempt. No account or database is needed for this exercise.
- Step 1 — Create two files. In a folder named
maths-quiz, createindex.htmlandquiz.js. - Step 2 — Build the interface in
index.html.
The id values let JavaScript find the right places on the page. The result element provides a place where the completed score can be announced to assistive technology, and the answer group is labelled by the current question. The question heading receives programmatic focus when the question changes, keeping keyboard users oriented. Clear text labels and meaningful controls are important accessibility foundations. [3]
- Step 3 — Add the logic in
quiz.js.
- Step 4 — Trace the logic. Each question stores the answer as a number:
0means the first choice,1the second and2the third. When you click a choice, the program checks its index, updates the score if correct, advances to the next question and displays the next set of answer buttons. When all four have been answered, the final score appears. - Step 5 — Test three attempts and keyboard use. Choose the second, first, third and second answers in that order; the result should be
4 out of 4. Select Try again and choose the first, second, first and first answers; the result should be0 out of 4. Restart once more and choose the second, second, third and first answers; the result should be2 out of 4. Use the Tab key and Enter or Space to choose answers; after a choice, keyboard focus should move to the new question heading so you can hear or read the new question before pressing Tab to reach its answer buttons. After the last question, focus should move to Try again. This follows W3C guidance on preserving logical focus when content changes. [13] - Step 6 — Extend the project. Add more questions, show feedback after each response, and style the page with CSS. Use a different subject, such as science or geography, once you understand the logic.
Common mistake: If buttons never appear, confirm that the JavaScript file is named quiz.js, is in the same folder as index.html, and that the browser’s developer console shows no error. Also check the id values against the JavaScript selectors.
Finished when: the learner can complete the quiz, receive the correct score and restart without refreshing the page.
Walkthrough 3: Build a searchable school library catalogue
The problem
A pupil wants to find books for science revision without reading a long, unorganised list. This exercise uses made-up titles and authors so no real pupil records are involved.
Version 1 must
list four sample books, filter by title, author or subject as someone types, ignore differences between uppercase and lowercase letters, and show a clear message when nothing matches.
- Step 1 — Make a folder called
library-search. Createindex.htmlandlibrary.jsin that folder. - Step 2 — Write
index.html. The label tells the learner what to type, and the list will hold results.
- Step 3 — Write
library.js. A JavaScript array stores four example books. Thefilter()method finds matches, andtextContentplaces book information on the page as text rather than interpreting it as HTML.
- Step 4 — Try these four searches. On first opening the page, four books should appear. Type
science: only Simple Machines and Plants Around Us should remain. TypeSCIENCE: you should get the same two books. Typenjeri: one book should remain. Typefootball: the list should be empty and the message should explain that no books were found. - Step 5 — Check your understanding. Add a fifth book to
catalogueand search for it. Try searching for only part of a title. Theinputevent runs the filter whenever the search field changes; you do not need a Search button.
Common mistake: If the list is empty when the page opens, check the filename library.js, the script path and the exact id values. Open the browser console if you see an error.
Finished when: another learner can find a book by title, author or subject, or understand that the search has no match. Next challenge: add a subject dropdown or a reset button. This is a local catalogue exercise, not a borrowing system with shared school records.
Level 3: Five intermediate-to-advanced full-stack projects
A frontend is the part people interact with in their browser. A backend runs application logic on a server. A database stores and organises records. An API is a defined way for the frontend to request information or actions from the backend. Review NIT’s API explanation and database guide if these ideas are new.
For the following projects, first draw the screens and plan the records. Add logins, shared data and server-side processing only when your first useful workflow is clear.
Small-shop stock system
A stationery shop needs to know what products it has and whether stock is running low. Build a product list with quantities, then add stock-in and stock-out actions. When you introduce a database, protect updates against invalid values and simultaneous stock changes. The walkthrough below shows a useful design. Next challenge: include stock movement history so a mistake can be traced.
Appointment booking system
Build a booking page for a fictional salon. Customers select a service, date and available time slot; the system stores a reservation. Begin with one staff member and one appointment duration. Next challenge: prevent two people booking the same slot through a server-enforced uniqueness rule. Use fictitious customer information during development.
Learning-resource portal
Imagine teachers need to publish revision notes while learners need to browse them. Create separate teacher and learner roles; teachers manage resources while learners can read published material. Next challenge: add subject filters and record updates with timestamps. Enforce permissions on the server, not only by hiding a button in the browser.
Online shop prototype
Create a catalogue, cart and simulated checkout. Begin without collecting card details or connecting real payments. Record a test order, calculate its total from the product data on the server and show confirmation. Next challenge: introduce stock reservations and order states. A production payment integration requires further security and operational work.
Course-registration application
Build a fictional course catalogue and a form that submits a learner’s application. Give a staff user permission to review applications and update their status. Next challenge: add an audit record for each status change. Test using fictional details; real educational records need appropriate access control and privacy safeguards.
Walkthrough 4: Design a stock system for a small shop
The problem
A shopkeeper records how many books and pens are in stock. When products are sold, the balance should reduce correctly.
Example starting records: Exercise book — 20 units; blue pen — 35 units; ruler — 12 units. These are fictional practice quantities.
- Step 1 — Define the first workflow. The shopkeeper sees products and quantities, records new stock received, and records a sale. A sale of five exercise books should change the quantity from 20 to 15. A sale of 21 should be rejected because the shop has only 20.
- Step 2 — Plan the database. A simple starting table in PostgreSQL could be:
The CHECK constraints prevent negative quantities and blank product names being stored through this table. They are safeguards, not a substitute for validating requests and controlling who can change stock. PostgreSQL documents how check constraints work. [11]
- Step 3 — Sketch the API. These are example application endpoints, not a claim that a server is already running:
GET /api/products— show available products and quantities.POST /api/stock-in— record a valid stock increase.POST /api/sales— validate a sale and reduce available stock.
- Step 4 — Protect stock reductions. The server should reject invalid quantities, check that the staff member has permission, and make the change safely in the database. An example parameterised PostgreSQL statement for reducing stock is:
Here $1 is the validated positive whole-number quantity to sell, and $2 is the product ID. The server must check whether a row was returned. If none was returned, the product may not exist or sufficient stock may not be available. The PostgreSQL RETURNING clause provides the new value of a modified row. [12] In a complete sales system, recording the sale and updating stock belong in the same database transaction, with idempotency or duplicate-request protection as needed.
- Step 5 — Test the important cases. Sell five exercise books and confirm the quantity becomes 15. Try selling 21 from the original 20 and confirm the request fails without changing stock. Try a quantity of zero, a negative value, and a value such as
2.5; all should be rejected before the SQL statement executes. Finally, simulate two staff members attempting to sell the last units at nearly the same time and verify the system never makes the quantity negative. - Step 6 — Improve the design. Add a
stock_movementstable showing the product, the quantity changed, why it changed, who authorised it and when. This creates a useful history instead of leaving the shopkeeper with unexplained numbers.
This is a system-design walkthrough, not complete deployable backend code. To implement the whole system, a learner must still create the server, authentication, endpoints, database transactions and tests. Server-side access control, input handling and secure configuration are especially important for shared applications; see the [OWASP Top 10:2025][7].
How to choose between two project ideas
Use these four questions instead of choosing the biggest-sounding project:
- Can I describe the problem in one sentence? “Students need to see club meeting details” is clearer than “I want to build a huge platform.”
- Can I name the first working version? For a quiz, it could be four questions and one correct final score.
- Will it teach me one skill I do not yet know? A project is useful when it advances your ability without introducing too many unfamiliar technologies at once.
- Can somebody else test it? Define an observable success result before adding extra features.
If you know HTML but not JavaScript, the club site strengthens layout skills; the grade calculator introduces input handling; and the quiz adds events, arrays and application state. Choose the smallest step that teaches something new.
Show someone what your project can do
After finishing a project, ask a classmate to try the feature without you explaining every click. Share a short note describing the problem, the feature you completed and how to run it. A screenshot alone cannot demonstrate that buttons and forms actually work.
Before sharing, check the following:
- The project opens without missing files or broken links.
- Buttons and forms work using both a mouse and keyboard.
- Headings and controls describe their purpose clearly.
- Content remains readable at narrow phone widths.
- Bad input produces a useful message instead of a broken result.
- No real passwords, personal records or API secrets are included in published files.
- A reviewer can see what you built and what you would improve next.
For a static HTML/CSS/JavaScript site, [GitHub Pages][6] is one documented option. It publishes static site files; it is not a place to run your own PostgreSQL-backed server. Never place secrets in a public project repository, and remember that even a Pages site built from a private repository may be publicly visible. [6]
This guide is about learning web development through increasingly capable projects. If your goal is to select projects specifically to demonstrate employability across ICT jobs, see NIT’s 12 ICT Portfolio Projects for Jobs in Kenya. That separate guide focuses on career-targeted evidence, not beginner coding lessons.
If you want one deeper end-to-end beginner tutorial, NIT’s How to Build Your First Web Application Step by Step walks through a different project: a Student Assignment Tracker. The present article is for choosing and progressively improving projects, rather than repeating that build.
Questions beginners often ask
Which web development project is easiest for a complete beginner?
A personal introduction webpage is one of the simplest starting points. It needs headings, paragraphs, links and perhaps an image. When that works, add CSS to improve its layout and make it responsive.
Can I build useful projects with only HTML, CSS and JavaScript?
Yes. You can build responsive websites, calculators, quizzes, searchable lists and many browser-based tools without a backend. Add a server and database when records must be centrally managed or shared between users.
How do I know that a beginner project is finished?
Write one or two conditions that a classmate can check without reading your code. For a quiz, it should calculate the score and restart correctly. For a search page, it should find matching books and explain an unsuccessful search. Once the simplest version passes its tests, you can add features.
Do beginners need to know React before building these projects?
No. The first ten examples can be approached using HTML, CSS and standard JavaScript. Learn the underlying browser fundamentals first; a framework can become useful as your applications grow. [2]
Your next project starts with one small working feature
Pick the project you can begin today. Write down what the first version must do, finish that version, test it and improve it. Then move to the next level. The skill you build is not just writing code; it is being able to turn an ordinary problem into working software.
To continue beyond beginner projects, NIT’s published Full-Stack Software Development programme lists eight months of institutional training and at least three months of industrial attachment. See the programme description [8] and admissions information [9] for course and application details.
From a beginner project to real full-stack skills
Register for Full-Stack Software Development at Newton Institute of Technology
Develop practical skills in frontend interfaces, JavaScript, backend development, APIs, databases, testing and deployment. Explore the course and register using the official links below.
References and learning resources
- [1] MDN Web Docs — Your first website. Beginner HTML, CSS, JavaScript and publishing sequence.
- [2] MDN Web Docs — Core learning modules. Web development foundations and accessible application practice.
- [3] W3C Web Accessibility Initiative — Labeling controls. Accessible form controls and labels.
- [4] MDN Web Docs — Web Storage API. Browser storage behaviour and limitations.
- [5] MDN Web Docs — Window.fetch(). JavaScript requests and HTTP response handling.
- [6] GitHub Documentation — Creating a GitHub Pages site. Publishing static projects and security considerations.
- [7] OWASP Foundation — OWASP Top 10:2025. Major web application security risks.
- [8] Newton Institute of Technology — Full-Stack Software Development Course. Programme duration, training scope and attachment.
- [9] Newton Institute of Technology — Admissions and Intakes. Application process and contact details.
- [10] MDN — Setting up a local testing server. Running localhost for beginner exercises.
- [11] PostgreSQL — Constraints. Database check constraints.
- [12] PostgreSQL — Returning Data from Modified Rows. Getting updated row values.
- [13] W3C WAI — Developing a Keyboard Interface. Maintaining predictable keyboard focus when an interface changes.
Technical references and examples checked 7 November 2026. All student, book, shop and school scenarios in this article are illustrative. Editorial responsibility: Newton Institute of Technology Editorial Team.