Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

First time Javascript solution all by myself

NBD•240
@bdal90
A solution to the Notifications page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Dear All,

Here is my newest challenge which is a true milestone in my learning process. It was the very first time that I came up with the whole javascript solution all by myself (no extra help, no google, no cheating). It took me a long time to learn even how to use console.log and I finally managed to do that this time and I was simply following my instincts. Therefore, I would truly appreciate if someone could have a glimpse on my code and see if it is alright or total garbage. Really ANY kind of comment/advice is extremely helpful for me.

Thanks a lot in advance,

Cheers,

Dalma

P.S.: I've had issues with the colors, so they might not match the design perfectly, sorry about that... :/

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Paulo Xavier•100
    @paulo-xavier
    Posted over 1 year ago

    Hi @bdal90 👋

    Congratulations for completing the challenge!

    The solution is well-done and almost perfectly. Great job! 😁

    Suggestion for the next challenges 📌

    <img src="assets/images/avatar-rizky-hasanuddin.webp" alt="" class="avatar">

    Do not forget to include alternative text for your images; it makes the content more accessible, especially for users relying on screen readers or if the image does not load. 🌟

    You did a great job!

    Best regards,

    Paulo Xavier.

  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted over 1 year ago

    You did an excellent job on this one, Dalma! 😊

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
Frontend Mentor logo

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

Oops! 😬

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

Log in with GitHub