Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Blog Preview Card - Animation and Custom CSS Variables

animation
SaruMakes•160
@SaruMakes
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 quite proud of how much I learned with this challenge. I took my time to research different concepts and topics, so that I felt that I knew what I was doing. I had to change and rewrite very few lines of code along the way.

I'm also proud of the work I put into the README file, which I filled out to the best of my ability (while also learning markdown/.md syntax). I'm very happy with how the hover transitions turned out as well as my custom CSS variables.

If you're curious to read more, there's a whole README in the Github repository with a lot more detail than I'm going to go into here.

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

Honestly, there weren't many super difficult parts. I made sure to prepare for each thing I was about to work on, and when I wasn't quite sure about something, I simply studied some more.

The main challenge was implementing new concepts that I had never worked with before, like transitions and hover/active states, but I overcame that through research.

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

I'd love some feedback on my HTML structure, as I'm not entirely sure I got it set up in the most logical way.

Also, if there's anything in my HTML or CSS code that stands out to you as odd or some part that I can improve on, I'd love to know!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Uche Ofatu•350
    @Macnelson9
    Posted about 1 year ago

    Your solution is super cool! Wow! I'd love to connect with you. I like your animation, I don't know how to animate yet, but I'm looking to move into that next. I would like to be able to get some tips and tricks from you especially with the semantics part and the readme notes, if that's okay by you. thanks!

    Marked as helpful

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