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

Advice slip api using HTML CSS JS

fetch
P
Jared Silver•500
@jsilver88
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any suggestions to improve are much appreciated. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Naveen Gumaste•10,420
    @NaveenGumaste
    Posted over 3 years ago

    Hello Jared Silver ! Congo 👏 on completing this challenge

    Let's look at some of your issues, shall we:

    • Just one suggestion Always use h1 first and then h2, h3 and so on

    happy Coding😀

    Marked as helpful
  • P
    Dave•5,295
    @dwhenson
    Posted over 3 years ago

    hey @jsilver88 well done on this challenge! Looking good 🙌 !

    Here's a few points to think about:

    • HTML: You will notice the validtor is complaining about you having a h4 element without any headings of a higher level above it. What this means is that you should use the <h1> headings as main headings of your web page, followed by the <h2> headings, then the less important <h3> headings, and so on, without skipping a level.

    This is really important as many people using assistive tech to access your pages will navigate the site based on the heading structure. We shouldn’t use headings to make text look BIG or bold. Use them only for setting out the heading of your document and to show the document structure. In this case using a h1 and adding the styles from the h4 to it should solve this issue.

    • CSS: My only suggestion here is to remove the height setting on your container as it causes elements to overlap depending on the length of the returned text. Generally if you are setting a height on something you should have a good look at what you are doing as it often causes issues. In this case you could remove it completely or just change it to max-height which will allow elements to grow if needed.

    • JS: I would suggest you add a check to ensure the API has responded correctly, and render an error message if not. This isn't too tricky, and I would just change your data variable to be:

      response.ok ? response.json() : throw new Error("API Failed")
    

    If you then add a catch at the end of of your fetchAdvice function you can render some fallback text in case things don't work for any reason. It's not a big deal, but thinking about how things can go wrong is a good habit to get into.

    Hope this helps!

    Keep up the good work!!! 👍

    Cheers 👋

    Dave

    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

Oops! 😬

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

Log in with GitHub