Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Notifications Page

Bobby S•410
@bobbe86
A solution to the Notifications page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The javascript was challenging for me. Also some of the UI was challenging. I really need to work on the responsiveness too. I tried to use SASS but I could not install on my computer successfully. I know the responsiveness is off and the grid layout is not perfect. But I think it turned out ok. I tried using BEM naming conventions which made the class names really long so I stopped along the way. I may try BEM in the future again.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muhammad Al-Ameen Abdullahi•280
    @al-ameen36
    Posted over 2 years ago

    hello Bobby

    A few suggestions

    1. I usually use Grids to make complex layouts or when i know the sizes i want my columns to be, else i just use FlexBox to align items horizontally.
    2. I also try to give my HTML elements very meaningful and intuitive names like notification and notification__item.
    3. Designing mobile first makes responsive design easier.
    4. I use semantic HTML elements as much i can.
    <main class="container">
        <header class="notification__header">
            <h1>Notifications
                <span id="notification-count" class="badge">3</span>
            </h1>
            <button id="readAll-btn" class="btn">Mark all as read</button>
        </header>
        <section class="notification">
            <article class="notification__item unread">
                <picture class="user__image"><img src="images/avatar-mark-webber.webp" alt=""></picture>
                <div class="notification__content">
                    <h2 class="user__name"><a href="#">Mark Webber</a></h2>
                    <p class="notification__text">reacted to your recent post
                        <a href="#">My first tournament today!</a>
                    </p><span class="dot"></span>
                    <time>1m ago</time>
                </div>
            </article>
        </section>
    </main>
    

    w3shools.com is a great resource i use for learning, it provides you great examples and a try-it editor for practice. Here are some useful links i recommend

    • CSS Box Model
    • CSS Flexbox
    • CSS Grids

    I hope this is helpful, you can always ask for clarification. Good luck

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub