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

Flex, transition css-property

accessibility
Vitaly•60
@V0000DY
A solution to the Blog preview card 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 achieving a clean and semantically correct HTML structure. Successfully using semantic elements like <main>, <article>, <time>, and <span> significantly improved the document's organization and accessibility.

Next time, I would focus more on the initial planning phase. By sketching out the design and structure beforehand, I could minimize the amount of refactoring needed later on, leading to a more efficient development process. Specifically, better initial planning of CSS classes would help avoid unnecessary class names and styling conflicts.

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

One significant challenge was getting the layout to be perfectly responsive across different screen sizes. Initially, the card looked great on desktop but needed adjustments for mobile devices.

I overcame this by adopting a mobile-first approach and using CSS media queries. I started by styling the card for smaller screens and then progressively enhanced the styles for larger screens. This approach ensured a consistent and pleasing user experience, regardless of the device. I also spent extra time testing the layout on various devices and browsers to identify and fix any inconsistencies.

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

I would appreciate feedback on my CSS architecture and naming conventions. While I successfully refactored the CSS to reduce redundancy, I'm always looking for ways to improve the organization and maintainability of my stylesheets. Specifically, I'm interested in best practices for structuring CSS files in larger projects and effective naming strategies for CSS classes to ensure they are both descriptive and scalable. Any insights on these aspects would be highly valuable.

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 Vitaly'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

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner
  • Use cases

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