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

Blog Preview Card using Semantic HTML5 and CSS

itunumide•80
@itunumide
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?

Proud of: Successfully implementing a clean and responsive design that adapts well to different screen sizes. Using Google Fonts (Figtree) to create a professional and visually appealing typography style. Applying CSS properties like box-shadow to give depth and modern UI styling. Ensuring accessibility through semantic HTML5 tags.

What I’d do differently:

Incorporate CSS Grid for areas where more complex layouts might simplify code structure. Add animations for hover effects on buttons and interactive elements to improve user experience. Include better responsive breakpoints to further enhance the mobile design experience.

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

Challenges:

Achieving Perfect Alignment: Aligning elements (e.g., buttons and avatars) required careful tweaking of padding and margin values.

Solution: Used Flexbox properties (justify-content and align-items) for precise alignment and inspected the design on different screen sizes for fine-tuning.

Responsive Design Issues: Ensuring the card layout worked well on both desktop and mobile devices.

Solution: Implemented a max-width on the card and media queries to adjust font sizes and padding for smaller screens.

Font Loading from Google Fonts: The imported font styles initially didn’t render correctly in some browsers.

Solution: Ensured the proper use of font-display: swap for better performance and caching.

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

Improved Responsiveness: Suggestions on better handling font sizes and spacing for ultra-small devices (like narrow mobile screens).

Code Refactoring: Feedback on how to optimize my CSS for reusability and maintainability, especially for similar components in future projects.

Hover States: Ideas for creative hover effects on buttons or card elements while maintaining a professional and clean UI.

Performance: Best practices for optimizing CSS animations and ensuring fast load times.

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

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.