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

blog preview

kieranichiban•30
@kieranichiban
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?

pretty straight forward. looking to make sure my css isnt over engineered

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

keep code to a minimum so its easier to read

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

same as above. would like feedback on css mainly

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Oscar Echenique D.•80
    @OscarE2D
    Posted about 2 months ago

    ✅ Positive Aspects

    • Semantic HTML Structure: Your use of semantic HTML elements enhances accessibility and provides a clear structure to the content.

    • Responsive Design: Implementing a responsive layout ensures that the blog preview card adapts well to various screen sizes, improving the user experience across devices.

    • Interactive Elements: Incorporating pseudo-classes like :hover and :focus adds interactivity, making the UI more engaging.

    • Use of Modern CSS Techniques: Utilizing Flexbox and CSS Grid demonstrates a good grasp of modern layout methods, allowing for flexible and efficient design implementations.


    🛠 Suggestions for Improvement

    • README Enhancement: Consider expanding your README to include sections like "What I Learned" and "Continued Development." This not only showcases your learning journey but also provides context for others reviewing your code.

    • Code Organization: Organizing your CSS using methodologies like BEM (Block Element Modifier) or adopting a modular structure can improve maintainability and scalability.

    • Accessibility Considerations: Ensuring that interactive elements are accessible via keyboard navigation and providing appropriate ARIA labels can enhance the inclusivity of your project.

    • Consistent Styling: Maintaining consistent spacing, font sizes, and color schemes throughout the project can lead to a more cohesive and professional appearance.

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