Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

"Responsive Web Projects with HTML & CSS,Flexbox & Grid for layout

accessibility
Yousef•40
@YOUSEF-ysfxjo
A solution to the Four card feature section 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’m most proud of successfully completing two web development projects, where I applied responsive design principles using HTML, CSS, and Tailwind CSS. I’m also proud of how I shared my progress on social media, receiving positive feedback that motivated me to keep pushing forward. Additionally, completing a KAUST course module this week shows that I am staying consistent with my learning goals, balancing both practical and theoretical aspects of my growth.

What would you do differently next time? Next time, I would focus more on refining the code after completing a project. I might spend additional time optimizing the performance of the website, such as:

Reducing load times Improving accessibility I also want to experiment more with JavaScript or other interactive elements to enhance the user experience. Lastly, I would allocate more time for in-depth exploration of advanced features in web development, like:

Animations Advanced grid layouts

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • why-not-phoenix•330
    @why-not-phoenix
    Posted 7 months ago

    Hi, Yousef, I just went through your site and it tested ok for responsiveness. I think you should be proud of yourself Going through your code I noticed there were some repetition e.g:

    body{
        margin: 0;
        padding:0;
        background-color: hsl(30, 38%, 92%);
    }
    

    Is that just a mistake or did you do that on purpose?

    I also personally think your @media (min-width: 1440px) could start at a lower min-width e.g for iPads etc with medium screen width.

    Thanks for sharing and goodluck

    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