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

Blog Preview Card by HTML and CSS (Sass)

sass/scss, accessibility
Kairung Vangmanaw•260
@VangmanawKairung
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 how I successfully applied semantic HTML5 markup, Sass for better CSS structure, and responsive design techniques to make the project look great on various screen sizes. Using mixins to streamline styling in Sass was a key highlight for me, and I also feel accomplished in balancing the layout with Flexbox, ensuring a clean and functional design. Next time, I would focus more on optimizing my workflow by planning ahead for potential improvements in interactivity—maybe by integrating some JavaScript for dynamic content. I would also consider experimenting with CSS Grid for more complex layouts, to continue expanding my skill set.

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

One of the biggest challenges I encountered was making sure each element's size matched the design precisely. At first, it was tricky to get everything aligned and scaled correctly, especially when balancing padding, margins, and responsive adjustments. To overcome this, I carefully analyzed the design requirements and experimented with different unit types, ultimately settling on rem for consistency. I also relied heavily on Chrome's developer tools to inspect and adjust each element in real-time, ensuring they met the design specs. This process taught me the importance of precision and patience when working with design measurements.

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

I would love to get more insights on improving accessibility in my projects, especially when it comes to ARIA labeling. Although I’ve used basic alt text and role attributes, I want to ensure that my components are as accessible as possible for all users, including those who rely on screen readers. Additionally, I’d appreciate guidance on writing more advanced @mixin rules in Sass, as I see a lot of potential in using them for cleaner, more reusable code. Learning best practices for both accessibility and Sass techniques would really help me level up my development skills.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mayen•440
    @Mayen007
    Posted 7 months ago

    Great design implementation!

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