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

Advice Generator App built with Tailwind, SASS and JavaScript

accessibility, fetch, sass/scss, tailwind-css, bem
P
Daniel 🛸•44,790
@danielmrz-dev
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


🛸 Hello Front-End Mentor Community! I'm Daniel and this is my solution for this challenge! 😊

🛠️ Built with:

  • HTML 🧾
  • SASS 🎨
  • Tailwind 👾
  • JavaScript 🤖
  • BEM Notation 🅱️
  • Third Party API 🆕
  • Mobile first workflow approach 📲

The design is simple, but this project gave me the opportunity to practice fetching data from an API, which is new for me. That's my second project working with API. Polishing up my Javascript every day 😊

Note: Advice is cached for 2 seconds. Any repeat-request within 2 seconds will return the same piece of advice.

👾 Custom features:

  • Added a little animation on the button when hovered over and clicked.

Thanks to the Front-End Mentor team that create challenges that make us learn a lot from doing them. 💟

If you have any suggestions on how I can improve this project, feel free to leave me a comment!

Feedback welcome 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Iggy19944•160
    @Iggy19944
    Posted over 1 year ago

    Hi Daniel, great looking design. I wanted to ask you a question and this seems to be the only place I can ask, I am sorry If it is not directly related to this challenge. How do you study JavaScript and combine it with doing challenges. If you already studied it before, What approach did you take, did you study to a certain level of competence and then start doing challenges or did you combine it. The reason I am asking is because I just started learning it and I would like to know about some good approached for balance and for it to be effective. Thank you.

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