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

Responsive landing page using display flex

pauleenann•240
@pauleenann
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What can I do to improve? Is there anything I need to change?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Outstanding work on completing the 3-column preview card component challenge! 🌟 Tackling a project that requires responsive design and attention to detail in styling is a commendable effort. Your project displays a good understanding of layout, design principles, and responsiveness. Here are some best practices and suggestions to enhance your project:

    • HTML Best Practices:

      1. Semantic HTML: Consider using more semantic HTML elements to improve accessibility and SEO. Elements like <section> for each card, <header> for titles, and <footer> for buttons could provide better structure.
      2. Alt Text for Images: Include descriptive alt text for all images to improve accessibility for screen readers.
      3. HTML Structure: Maintain the well-organized structure of your HTML, which aids in readability and maintainability.
    • CSS Best Practices:

      1. Responsive Design: Ensure that your design is fully responsive and looks good on all device sizes. Test on various devices to ensure consistency.
      2. Hover States: Implement noticeable hover states for interactive elements like buttons to enhance user experience.
      3. Consistent Styling: Keep a consistent approach to styling, particularly with fonts, colors, and spacing.
    • Accessibility Considerations:

      1. Keyboard Navigation: Make sure that all interactive elements are easily navigable using a keyboard.
      2. Color Contrast: Ensure sufficient color contrast between text and background for readability, especially for users with visual impairments.
    • General Suggestions:

      1. Performance Optimization: Optimize your images and assets for faster loading times, especially for mobile users.
      2. Cross-Browser Testing: Test your page across different browsers to ensure compatibility and a consistent user experience.
      3. Code Validation: Use tools like the W3C Validator to check your HTML and CSS for errors and standards compliance.

    You've shown excellent skill and attention to detail in this project. Keep up the great work, and continue to challenge yourself with new projects to further enhance your skills! 💪

    Marked as helpful
  • mcorusa•210
    @mcorusa
    Posted over 1 year ago

    Hello @pauleenann,

    your project looks great!

    I have a small suggestion that you can consider regarding the visuals of your project. You can update paths of two car icons (SUV and Luxury).

    Love your 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

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