Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Reponsive advice generator app with React and Sass

react, sass/scss
Daniela Darnea•180
@mdanieladla
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there! Just finished this project, if you have any recommendations or feedback please let me know :) Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Luciano Lima•1,270
    @LucianoDLima
    Posted almost 3 years ago

    Gratz on finishing the project!

    As a piece of advice you could wrap it around a <main> tag instead of `<div id="root">' so your structure is more semantic.

    Also maybe add cursor:pointer to your button instead of the img since if you click on the button it still activates but there's no pointer indicating that unless you hover over the img itself

    I would avoid using position: absolute to position your divs, as if you do that in a actual page, it will be hard to make it responsive, so to center you could instead fo something like

    #root {
    height: 100vh;
    }
    
    .outside-card {
    display: grid;
    place-item: center;
    }
    

    Happy coding!

    Marked as helpful
  • Devmor•470
    @devmor-j
    Posted almost 3 years ago

    Great this is almost identical well done 🎉

    One important tip:

    Right now this app might not fetch new advice on Firefox browsers because they rely on cache and we have to enforce the browser to call API service on each user request.

    This can be easily done by adding {cache: 'no-store'} option to our fetch service like so:

    inside ==> advice-generator/src/services/api.js

    const callToApi = () => {
      return fetch('https://api.adviceslip.com/advice', { cache: 'no-store' })
        .then((response) => response.json())
         .........
    

    Hope this is helpful and have a nice time coding 🤩

    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
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