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

Responsive advice quote generator using javascript,css,html

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

Solution retrospective


All observations noted and corrected

Any feedback will be appreciated

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Soe Wai Yan Aung•410
    @soewaiyanag
    Posted over 3 years ago

    Great job with functionality. But with design, I found that the dice button is not fully centered. When I check your code I found that you are using a fixed value for the right property which is right: 8rem. You can fix it by setting it's right to 50% and adding transform: translateX(-50%). It will center the dice no matter what size or width of the card. And give it border-radius 50% to get a full circle. And would be better if you fix your font size and font-weight. Other than that, well done with functionality, keep it up.

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

    Hey nice, job here!

    To make things faster or appear faster, I would 1) move the script to the head, and add the async attribute, 2) put some placeholder text in the HTML that way if things are slow or JS fails the user still has something to read 3) not include window.onload and just execute the function as its read (you may need to swap async to defer if that messes up interactivity).

    Also, I'd suggest having another look at your fonts - they don't seem to be showing up, and also adding some fallback text in your catch so that the user still sees something if JS fails for any reason.

    Hope this helps a little

    Cheers Dave

    Marked as helpful
  • Shashree Samuel•8,860
    @shashreesamuel
    Posted over 3 years ago

    Hey good job completing this challenge

    Keep up the good work

    Your solution looks great however I think the font family of the content does not match the one specified in the style-guide.md file.

    In terms of your accessibility issues simply wrap all your content between main tags

    I hope this helps

    Cheers 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

Oops! 😬

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

Log in with GitHub