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

main-notifications-pages static using React

Ngouend raoul Gerard•680
@BeinRain06
A solution to the Notifications page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My Time

Long time ago I dream to be a like star in the sky m how beautiful it was that nightmare...huh that dream ! of course, but the time is so harsh that it's kind of fully horror surrounding me . But let us this pop harsh movie away life still need to enforce us to the goodness. That's why happy New Year to all members of the community..

Foods in the kettle This web static pages is not a one of this big design considered you know, but some kind of friendly view that i aim to offer to everyone . It's my first time with react and i got troubling time that issue :

digital envelope routines::unsupported

i finally find out that it has be one that has facing many users on react , angular with nodejs 17,

i have tried many solutions and advise but the one working at the end was to ** update** react-script --version in the root file package.json by running the Terminal command : npm install --save react-scripts@latest in vscode under the directory of my react app folder. It's has updated my react-script --version 2.0.4 to the version --5.0.1

that works well to establish a gh-pages branch on github repository and allow with that the website in github pages to be well viewed .

Hope you will enjoy it. Thanks Dude !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ngouend raoul Gerard•680
    @BeinRain06
    Posted over 2 years ago

    Rainy Weather Rain might be fall at any times, the clouds persists to be dark over the sky, the weather is the weather. What are going to happen will state before the end of the day.

    New Design I Improve the design of Notifications-maim-page to enhance some dynamic effect. It's the continuous version of our app trying to fix media queries as well as experience of UI when taking a break to looks at our app.

    Here are the new link of our work . Hope you will be delighted of our changes :

    • Solution URL: https://github.com/BeinRain06/notifications-page-main-dynamic.git

    • Live Site URL: https://beinrain06.github.io/notifications-page-main-dynamic/

    Thanks Dude! And a Bright Day to All ...

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub