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

Advice Generator App with React-Typescript

fetch, node, react, typescript, vite
Arinze Owoh•150
@ArinzeGit
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?

I am most proud of consuming APIs for the first time. Next time I will add animations to make the app more lively.

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

Initially, I couldn't get the "Advice #117" part to space out like the design. I learned that letter-spacing in CSS can be used to set the space between letters in a text. Before now, I thought it was fixed and dependent on the font-family.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Rupali•890
    @rupali317
    Posted about 1 year ago

    Hello @ArinzeGit

    Good job on completing the challenge!

    I have the following feedback for your code:

    • You may consider using rem instead of px for the button's width and height. Because if you change your browse's font size to "very small", you will notice that the proportion of the button is very big as compared to the rest of the UI elements

    • To enhance the code readability and maintainability, avoid using inline styles like <p style="font-family: Manrope; font-weight: 800; font-size: 1.71rem; color: rgb(206, 227, 233); >". Define them in the CSS itself like:

    p {
      font-family: Manrope; 
      font-weight: 800;  /*and so on*/
    }
    

    Also instead of color: rgb(206, 227, 233);, define rgb(206, 227, 233) as a custom variable. In fact, define colors, typography, spacing as custom variables. You can refer to my CSS file on how I create custom variables. Creating custom variables is ideal for maintainability.

    • I would not consider making the "Advice #" as a h1 because it does not look like a h1. It is a ribbon text. A <p> is more appropriate. In fact, the quotes can use <q> tag. Using the correct HTML tag can improve the accessibility.

    • Consider using <picture> element for displaying the divider based on the form factors. It is better for performance.

    Let me know if the suggestions work!

    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