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

Quote App Using HTML,CSS,JS used API

Adeel Atta•130
@AdeelAtta
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jens Kristian Espevik•80
    @jkriesp
    Posted over 1 year ago

    Hello AdeelAtta,

    First off, I'd like to commend you on the responsive design of your project. It's clear that you've put considerable effort into ensuring the layout adapts well across various devices, which greatly enhances user experience. Moreover, your decision to centralize most of the CSS styling in an external stylesheet is a great practice, contributing to the maintainability and scalability of your code.

    However, there are a few areas where I believe your solution could be enhanced. While the use of semantic HTML might seem less critical in a project focused on a single quote, integrating elements like <blockquote> for the quote or <figure> for any associated imagery can further improve accessibility and the semantic structure of your document. Speaking of accessibility, adding alt attributes to images, including those used as buttons, is crucial for users who rely on screen readers. This small addition can make a big difference in making your project more inclusive.

    Additionally, while the responsive design is commendable, you might want to address the issue where the main content tends to shift off-center on larger screens. Employing a more flexible or centered layout, possibly through the use of CSS Grid or Flexbox, could help maintain the aesthetic balance across all screen sizes. Consider utilizing both provided dividers to enhance the visual appeal, though this is more of a stylistic choice and what you have currently still looks polished.

    Lastly, it's great to see most of your styling consolidated in an external CSS file. To further improve, I'd recommend reviewing any inline styles you have in your HTML to ensure all styling is centralized, making future updates and maintenance smoother and more efficient.

    In conclusion, your project demonstrates a solid foundation in responsive design and CSS management. With a few adjustments to enhance semantic HTML usage and accessibility, along with some layout tweaks for larger screens, your project will not only be more robust but also more user-friendly. Keep up the excellent work, and I look forward to seeing your future projects!

    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

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