Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

advice-generator-app

react, vite, tailwind-css
AbieroAlvin•160
@AbieroAlvin
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Insights on how to improve the code would be appreciated especially, how i can add quotation marks to the advice and the advice number for the title.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted almost 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    HEADINGS ⚠️:

    • This solution consists incorrect usage of <h1> so it can cause severe accessibility errors due to incorrect usage of level-one headings <h1>

    • Every site must want only one h1 element identifying and describing the main content of the page.

    • An h1 heading provides an important navigation point for users of assistive technologies, allowing them to easily find the main content of the page.

    • In this solution there's <h1> element which is this <h1>Advice</h1>, you can preferably use <h2> instead of <h1>. Remember <h1> provides an important navigation point for users of assistive technologies so we want to use it wisely

    • So we want to add a level-one heading to improve accessibility by reading aloud the heading by screen readers, you can achieve this by adding a sr-only class to hide it from visual users (it will be useful for visually impaired users)

    • Example: <h1 class="sr-only">Advice Generator</h1>

    • If you have any questions or need further clarification, you can always check out my submission for another challenge where i used this technique and feel free to reach out to me.

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

  • Boots 😺•1,610
    @adityaphasu
    Posted almost 2 years ago

    Hello again! @AbieroAlvin

    To answer your question, to add those quotation marks you can just add them like a text like this:

     <p className="py-4 md:text-3xl text-2xl text-[var(--LightCyan)]">
           "{advice}"
     </p>
    
    • Basically wrap the {advice} with " "
    • For the advice number, the API also returns an id for them so you would want to modify your code a bit like this:
    try {
          const response = await fetch(url);
          const data = await response.json();
          setAdvice(data.slip);   //here 
        } 
    

    In the try block instead of getting the advice from the slip object we just get the object as it is and then access the advice and id number from it using dot notation like this:

     <p className="py-4 md:text-3xl text-2xl text-[var(--LightCyan)]">
           "{advice.advice}"
     </p>
    

    and in your your h1 access the id for the advice like this:

      <h1 className="md:text-2xl text-xl text-[var(--NeonGreen)] uppercase">
            Advice  #{advice.id}
       </h1>
    

    This should work.

    • An alternative way for the above solution would be to make another state (say id and setId) and set the id like this in the try block:
    try {
          const response = await fetch(url);
          const data = await response.json();
          setAdvice(data.slip.advice);
          setId(data.slip.id);    // This line
        } 
    

    and then in h1 like this:

    <h1 className="md:text-2xl text-xl text-[var(--NeonGreen)] uppercase">
            Advice  #{id}
       </h1>
    

    This should also work but in my opinion, the 1st one is better since you do not have to manage 2 states and just use one to handle the whole object but 2nd is one is also fine as it's more readable I guess hahaha

    Good luck and happy coding!🙌🏻

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