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

AI Project Management Tools

Francis Kojo Buabeng•50
@Francis-Kojo-Buabeng
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 really proud of how the project turned out, especially the clean and responsive design that works well on all devices. Using CSS variables was a smart choice because it makes future updates easier. The layout is straightforward, and the use of semantic HTML helps with accessibility.

That said, there are a few things I’d do differently next time. I’d focus more on accessibility by adding aria-labels and improving color contrast for better visibility. I’d also make font sizes more flexible on mobile to improve readability. Optimizing images for faster loading and adding some interactive elements, like hover effects or animations, would make the site feel more engaging. Lastly, making sure the icons are consistent in style would give the design a more polished look. These changes would enhance the overall user experience.

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

During this project, I faced challenges with responsiveness, alignment, and mobile optimization. The grid layout in the main section worked well on larger screens but became cramped on smaller ones. I used media queries to switch to a single-column layout on smaller screens, improving readability.

Aligning the text and images within each .box also posed a challenge. I resolved this by using flexbox in the .containerof2, ensuring consistent spacing and alignment, particularly on mobile devices.

Mobile optimization was another issue, with cramped text and elements. I adjusted font sizes and padding in the media queries to make the design more readable on smaller screens.

Finally, I adjusted the box shadows in the .box class, keeping them subtle to maintain a clean, light design. Through these solutions, I was able to create a responsive and user-friendly layout.

What specific areas of your project would you like help with?

In this project, I’d appreciate help in several areas. First, improving accessibility by ensuring better screen reader compatibility and optimizing keyboard navigation. I’d also like guidance on performance optimization, specifically using techniques like srcset for responsive images and cleaning up unnecessary CSS to improve load times.

The box shadows used in the .box elements might be too intense on larger screens, so I’d like advice on creating a more balanced effect. Additionally, I’m interested in organizing the CSS more efficiently, perhaps by leveraging CSS variables or reusable classes for better maintainability.

Lastly, while the site is responsive, I’d like to refine its design for mobile devices, particularly regarding font sizes, spacing, and usability. Overall, I’m looking for ways to enhance accessibility, performance, and mobile responsiveness.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jaca1x•120
    @Jaca7x
    Posted 8 months ago

    good!

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