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

Advice generator app

👾 Ekaterine Mitagvaria 👾•7,860
@catherineisonline
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, Frontend Mentor community! This is my solution to the Advice Generator app.

I have read all the feedback on this project and improved my code. Due to the fact that I published this project very long ago, I am no longer updating it and changing its status to Public Archive on my Github.

You are free to download or use the code for reference in your projects, but I no longer update it or accept any feedback.

Thank you

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vahe Abovyan•1,110
    @VaheAA
    Posted over 3 years ago

    Hi! I noticed the same issue with the API call response in Firefox as i experience by myselfe while was doing this challenge. After first call you always get the cached response and result doesn't change. To solve it you can add to your fetch option "fetch(apiUrl, {cache: "no-cache"})". For more information https://developer.mozilla.org/en-US/docs/Web/API/Request/cache.

    Besides that, nice work!

    Marked as helpful
  • Karol Binkowski•1,620
    @GrzywN
    Posted over 3 years ago

    Great job Catherine! Frontendmentor.io crew did something wrong and they didn't provide right color for the background in this challenge. I used the one from figma and it wasn't matching any of the colors in the style-guide.md file.

    My color variables look like this:

    $dark-blue: #202733;
    $dark-grayish-blue: #313a48;
    $grayish-blue: #4f5d74;
    $light-cyan: #cee3e9;
    $neon-green: #53ffaa;
    

    Hope this helps! Happy coding!

    Marked as helpful
  • Simon Davis•505
    @Skidragon
    Posted over 3 years ago

    It looks good though I keep getting a cached response when fetching for new advice. I believe it has to do with fetch since I used axios for mine, and you might have to do what this post suggested: https://stackoverflow.com/questions/29246444/fetch-how-do-you-make-a-non-cached-request

    Just noticed its doing it on mine too. I think it might be firefox dev edition browser.

    Marked as helpful
  • Abdul•8,560
    @Samadeen
    Posted over 3 years ago

    Hey Catherine!! Cheers 🥂 on completing this challenge.. . I think your dice could use a little margin-top and the color can use a little filter to make it darker.

    You Inspire me so much... Happy coding

    Marked as helpful
  • Danilo Blas•6,300
    @Sdann26
    Posted over 3 years ago

    Hi Catherine!

    You're right, I when I saw about the colors, they didn't fit the design. In my case I used the eyedropper to inspect the page to get the colors.

    Obviously if you can't use the eyedropper because you have the image and not the web page, you can use this tool to take the colors.

    https://imagecolorpicker.com/

  • Jose Arape•160
    @zent0821
    Posted about 3 years ago

    I like it, nice job.

  • Salman sajib•230
    @salmansajib
    Posted about 3 years ago

    The color is not ok but nice work.

  • Robert Macwan•160
    @Robert170304
    Posted about 3 years ago

    hey you did a really good job and thanks your solution help me a lot to build this project.

  • Account deletedPosted about 3 years ago

    Boa, vejo que você está indo muito bem nos desafios, parabéns...

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted over 3 years ago

    Hey catherineisonline, good job completing this challenge. Keep up the good work

    Your solution looks great however I think in comparison with the design that the dice requires some margin-top.

    I hope this helps

    Cheers Happy coding 👍

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

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

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

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

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

Oops! 😬

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

Log in with GitHub