Frontend Mentor - Notifications page solution

This file is still Work-In-Progress.

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
  • Screenshot
  • Links
• My process
  • Built with
  • What I learned
  • Continued development
  • Useful resources
• Author
• Acknowledgments

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

Links

• Solution URL: Github
• Live Site URL: Netlify

My process

I first started out be studying the screenshots provided in the challenge and mapping out the best, clean and efficient way of structuring and writing the HTML code. After that step, i went ahead to start writing code while paying close attention to correctly add a link tag to elements that are links, adding Classes and IDs to elements that will need then when i begin styling later on. I also made sure i wrote code that another developer would be able to easily interprete.

After coding the HTML, i went ahead to add custom styling using CSS. I added styles to the page as specified in the screenshot. Making sure to be as concise and direct with the styling as much as possible to avoid using 5 lines of code for a style that can be done in one.

When i finished coding the HTML & CSS, then came Javascript. As part of the challenge requires that the site should be able to update whenever a viewer click/tries to view a notification by reducing the number of notification count.

Built with

• Semantic HTML5 markup
• CSS custom properties
• Flexbox
• JS

What I learned

Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.

To see how you can add code snippets, see below:

<h1>Some HTML code I'm proud of</h1>

.proud-of-this-css {
  color: papayawhip;
}

const proudOfThisFunc = () => {
  console.log('🎉')
}

If you want more help with writing markdown, we'd recommend checking out The Markdown Guide to learn more.

Note: Delete this note and the content within this section and replace with your own learnings.

Continued development

Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.

Note: Delete this note and the content within this section and replace with your own plans for continued development.

Useful resources

• Example resource 1 - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
• Example resource 2 - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.

Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.

Author

• Website - Add your name here
• Frontend Mentor - @yourusername
• Twitter - @yourusername

Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.

Acknowledgments

This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.

Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.