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

Advice Generator App with Async Function

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

Solution retrospective


This is my first project using JavaScript on FrontEnd Mentor, please review my project and send feedback to me, is welcome. Greetings

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your Advice Generator App project! 🎉 It's impressive to see you bring together different technologies to create a functional and visually appealing application. Here are some best practices and suggestions to enhance your project:

    • HTML and CSS Best Practices:

      • Great job on using semantic HTML tags! Keep this practice as it improves accessibility and SEO.
      • In your CSS, consider organizing properties in a consistent order, such as positioning, box model, typography, and visual styling. This makes your code more readable and easier to maintain.
    • Responsive Design:

      • You've implemented a responsive design using media queries. Test your app on various devices to ensure it adapts well to different screen sizes.
      • Check text sizes and button dimensions on mobile devices to ensure they are touch-friendly and easily readable.
    • JavaScript Best Practices:

      • Consider using const for variables that don't change and let for variables that do. This provides clarity on which variables are meant to be immutable.
      • In your fetchAdvice function, move the URL 'https://api.adviceslip.com/advice' to a constant at the top of your script. This makes it easier to manage and change if needed.
    • Accessibility and Usability:

      • Ensure that all interactive elements (like buttons) have appropriate focus and hover states to improve accessibility and usability.
      • Add aria-label to elements like buttons for screen reader users, especially when the button only contains an image.
    • Code Comments and Cleanup:

      • Remove any commented-out code that is not being used, such as the <div> with id creation. This helps keep your codebase clean and maintainable.
      • Add comments to your CSS and JavaScript files to explain what certain blocks of code are doing, which can be especially helpful for more complex sections.
    • Performance Optimization:

      • Optimize your images to reduce file size for faster page loading times. Tools like TinyPNG can compress images without losing quality.
    • Cross-Browser Compatibility:

      • Test your app in different browsers to ensure it works and looks consistent across them.

    References for Further Learning:

    • CSS and HTML Best Practices: MDN Web Docs
    • Responsive Web Design: A List Apart
    • JavaScript Best Practices: JavaScript.info
    • Accessibility: Web Accessibility Initiative (WAI)

    Keep pushing your limits and exploring new aspects of web development. Your progress is inspiring, and I'm excited to see what you'll create next! 💻🌟

    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