Skip to content
Ankit-aiml-2026

Ankit-aiml-2026/frontend-learning-journey

This repository contains my beginner frontend projects created while learning HTML and CSS.

My frontend development learning journey using HTML and CSS

0 0HTMLPush 19d agoListed 11d agoNo license on GitHub

No GitHub topics on this repo.

  • HTML57.4%
  • CSS41.8%
  • JavaScript0.8%
View on GitHub

Report a problem

1 Review

This is a solid early learning repository because it shows real hands-on practice instead of only notes: there are multiple static projects, screenshots, and enough HTML/CSS volume to show that you are working through layout, navigation, forms, and responsive behavior. The Lighten project is the strongest part because it attempts a full multi-page site with separate About, Product, Blog, and Contact pages, not just a single landing screen. The responsive form work also shows good beginner instincts: labels are connected to inputs, there is a viewport meta tag, and the login validation script handles empty fields plus basic username/password length checks.

The biggest improvement would be presentation and reliability. The top README is short and clear, but each project would be much easier to evaluate if it included a live demo link, a screenshot preview, and a short “what I learned” note. Right now the screenshots are stored separately, but they are not surfaced in the README. I also noticed rough project hygiene: Conctact.html is misspelled, some Lighten asset references appear to use inconsistent folder casing/path styles, and the repo has many duplicate or large image assets. Those details matter because a page that works locally on Windows can break on GitHub Pages or Vercel when file names are case-sensitive.

For the next pass, I would focus less on adding more clones and more on polishing these into portfolio-quality examples. Add an index.html launcher at the repo root, deploy it with GitHub Pages, clean unused assets, add alt text where images carry meaning, group shared CSS instead of repeating full styles per page, and include a license. The repo is new, with no stars/forks/issues yet, so the best way to build trust is to make it easy for someone to open, run, and understand each project in one minute.