Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Product Preview Card Component Solution using Media query

bootstrap, tailwind-css
Ajiboye Caroline Adetomiwa•10
@dev-caroline
A solution to the Product preview card component 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 how clean and responsive the final layout turned out. It matches the design closely across different screen sizes, and I was able to apply Tailwind CSS effectively to speed up styling while keeping the codebase neat.

If I were to do this project again, I would focus more on improving accessibility—ensuring that the component works well for screen readers and keyboard users. I’d also like to implement the project using only one styling approach, either Tailwind or Bootstrap, to avoid unnecessary overlap.

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

One of the main challenges I faced was making the layout responsive on smaller screens. At first, the elements overlapped or didn't stack properly. I overcame this by reviewing how flexbox and media queries work, and then applied a mobile-first approach to fix the layout step by step.

Another challenge was deciding when to use utility classes from Tailwind versus writing custom styles. To keep things organized, I stuck mostly to Tailwind but used custom classes only when necessary for clarity and reuse.

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

I'd really appreciate feedback on the following:

  1. Responsiveness: Does the layout adjust well across different screen sizes? Are there any breakpoints or devices where it looks off?

  2. Code structure and readability: Is my HTML and CSS organized in a clean and maintainable way? Any tips on improving naming conventions or reducing repetition?

  3. Mixing frameworks: I used both Tailwind CSS and Bootstrap—was this a good decision, or should I stick to one? What’s the best way to manage or separate styles when combining frameworks?

  4. Accessibility: Are there any improvements I could make to ensure the component is more accessible (e.g., better focus states, semantic elements, or alt text usage)?

I’m open to any tips that can help me improve as a front-end developer, especially in real-world projects like this!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ajiboye Caroline Adetomiwa's solution.

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.