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

Blog preview

P
Weyehn Reeves•190
@WeyehnR
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 am most proud of learning maintable using cursor AI, unlike the QR project where I had to do it by eye and I used it without AI, and only this time I am improving using the provided CSS style from Figma (except the dimension, we have CSS styling for that!) and AI. I just wanted to see what the difference is between with vs without AI.

I would do differently by relying a little less on the AI, as at some point, the AI can write a different solution from what I intended. This led to more rabbit hole research on the different CSS styling and CSS maintainability techniques. I learned a lot in that area and got the idea of learning CSS styling and maintainability techniques from an AI I had never dreamt of before.

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

I encountered challenges implementing a view slider and switching from desktop to mobile view, as I wanted to test different dimension sizes. I tried to deviate from the two HTML sheets, as I didn't want to copy and paste similar HTML. I got around it by adding a div class view switcher and some CSS styling on top of that. Then I kind of broke the pure HTML/CSS rule, but I just wanted to refresh a bit on my JavaScript, too!

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

I probably need help keeping the card dimensions consistent from the mobile to the desktop slider, as I could not get around the slight dimension change when changing it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • KKen007•570
    @KKen007
    Posted 3 months ago

    Bon travail.

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