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

Using Axios and React hooks to display random advice

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

Solution retrospective


My first API-related project. Made with HTML5, SASS, ReactJS (Axios, useState, useEffect).

What I've learned:

  • basics of SASS (using variables and nesting)
  • playing with media view for completely responsive design
  • basics of useState
  • basics of useEffect
  • basics of GIT (commit, push) and Github

My considerations

The project took me considerably less time than my very first project (the Rating component). The first one took over 8 hours, whereas this took about 4 hours, mostly spent on getting the Axios.get working, and minutiae CSS details.

CSS: Positioning the button was difficult, played around with negative margins which didn't seem like an elegant solution. Researched alternatives and used transform, instead.

React: Could have used fetch instead of the Axios package, had difficulties implementing the get function and reading data on it. Lots of Googling and reading docs.

Thank you for taking the time to check my work out. I'm very open to any and all comments and suggestions ❤️

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matthijs van der Plas•30
    @MatthijsvanderPlas
    Posted about 3 years ago

    Awesome App! Inspiring me to look forward to sass and react. Code looks really clean.

    I could only suggest changing the width to a more static display so it doesn’t change depending on the quote it displays. Only the height would adjust slightly.

    Some delay on mobile before you can get a new quote, no idea how.

    Keep it up!!

    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