Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Advice Generator App

tucecifci•150
@tucecifci
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Here are some potential improvements that could be made to the application:

Styling: Add CSS to improve the visual appearance of the app. Loading Indicator: Display a loading indicator while the advice is being fetched. Error Messages: Show user-friendly error messages on the UI instead of just logging them to the console.

What challenges did you encounter, and how did you overcome them?

Understanding the Fetch API: Challenge: As a beginner, understanding how to use the Fetch API to make network requests and handle responses was initially challenging.

Handling Asynchronous Operations: Challenge: Working with asynchronous operations in JavaScript can be tricky, especially when dealing with promises and asynchronous functions.

What specific areas of your project would you like help with?

While the basic functionality of the Advice Generator app is working well, there are several areas where I could use some assistance to improve and enhance the project: User-Friendly Error Messages: Help Needed: Currently, errors are logged to the console. I would like to implement user-friendly error messages that are displayed on the UI when something goes wrong (e.g., network issues). Details: Guidance on best practices for error handling in JavaScript and how to display error messages in a way that does not disrupt the user experience would be beneficial.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gautam Sarkar•850
    @gautam32b7
    Posted 11 months ago

    Hi there!

    I appreciate your effort in completing the challenge. However, I would suggest you study my solution.

    Github link: https://github.com/gautam3333/advice-generator

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