// projects/

Web development projects I have built

Eight web projects I built as a student web developer in Bangladesh, from HTML, CSS and JavaScript apps to Next.js and TypeScript tools like a Gemini AI quiz generator. Every card links to public code, and the same kind of page can be made for a business.

// 01 · read

How to read a project card.

The title is the name of the repository’s project, not a brand. The summary is one honest paragraph. Technologies are the ones I actually used. Featured means I want that card near the top of this page. It does not mean the project is finished, funded, or professional.

GitHub opens the code. Live demo opens a page only when one is published. If GitHub Pages is off, the card says there is no demo instead of linking to a dead URL. A demo badge, if one appears later, means the card is placeholder layout, not work I finished.

1 published project

// 02 · planner

Student Planner is a task app.

Student Planner adds, edits, completes, and deletes tasks, with deadlines, priorities, categories, search, and filters. The theme and the task list stay in localStorage on that browser. There is no account system and no server in this version.

GitHub Pages is not turned on for that repository, so the live link is the code. The same idea — tasks, filters, a clear layout — is something I can build for a team or a business, including a version that saves to a server.

The card is Student Planner. The repository is mfaysal-dev/mahir-student-planner.

// student-planner
storage  localStorage
tasks    add edit filter
server   not in this repo
demo     code on GitHub
can build a hosted version

// 03 · nexora

Nexora is an early personal page.

Nexora is a static site: a task list, a calendar, a focus timer, and an analytics view. It is published with GitHub Pages, so the project card can include a real live demo. The address is on the project page, and it points at mfaysal-dev.github.io.

The words “Pro Member” in that interface are layout text in the demo, not a checkout. I can build a real members area, a dashboard, or a business page in that direction when the project needs it.

Both projects can be featured. Featuring is only sort order. Student Planner can sit beside Nexora even though one has a demo and one does not. The missing demo is information, not a failure I need to hide.

// 04 · upload

New work shows up the same way.

When a build is ready to show, I add it from the admin dashboard: title, summary, description, technologies, GitHub link, demo link when one is live, and a cover image. The public page renders that row with the same card as the projects already here.

Published means anyone can read the card. Client work can sit in this list the same way. If I cannot describe what the page does in a few sentences, it is not ready to go up.

// 05 · next

What I want the next project to teach.

The next build I want on this list is a page with a real brief behind it: a clearer planner with a server, a business site, or a dashboard that reads and writes MySQL. Phone layout included from the start.

If that brief is yours, use the contact page. The card, the GitHub link, and a straight description will follow once the page works.