Skip to content

Latest commit

 

History

History
83 lines (44 loc) · 3.34 KB

File metadata and controls

83 lines (44 loc) · 3.34 KB

Frontend Mentor - Notifications page solution

This is a solution to the Notifications page challenge on Frontend Mentor. Frontend Mentor challenges help you improve your coding skills by building realistic projects.

Table of contents

Overview

The challenge

Users should be able to:

  • Distinguish between "unread" and "read" notifications
  • Select "Mark all as read" to toggle the visual state of the unread notifications and set the number of unread messages to zero
  • View the optimal layout for the interface depending on their device's screen size
  • See hover and focus states for all interactive elements on the page

Screenshot

desktop

Links

My process

Built with

  • Semantic HTML5 markup
  • Mobile-first workflow
  • Vue - JS Framework
  • Sass - For CSS
  • Webpack - For bundling everything for the browser

What I learned

I have been using laravel-mix up until now for setting up the project. It would take care of vue, tailwind and whatever preprocessing I needed. And laravel-mix assures its utility by being ready for as many front-end resources as possible. I knew it is a wrapper around webpack itself. And I wanted to know how much less of a setup is needed if I do not use laravel-mix. So I decided to use webpack directly, without the help of laravel-mix. Of course, where needed, I have peeked into laravel-mix's source code as well. But now I believe I can set up a webpack project by myself.

Also as always suggested by frontendmentor, I decided to try sass for css. VSCode does not show the colour decorators (preview and picker) and out-of-the-box, so I fiddled with some plugins, but none was satisfactory. I later learned that VSCode supports colour decorators in scss! Maybe because sass itself doen't validate as css before compilation, there must be a lot more coding required to support colour decorators in a different language altogether. Will try scss next time.

Continued development

I wish to write a workflow for each of my frontend mentor projects and make it such that only that project's output is triggered by updates to that project's folder

Useful resources

Author