Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

Submitted

Blog preview card component

@Micahtron

Desktop design screenshot for the Blog preview card coding challenge

This is a solution for...

  • HTML
  • CSS
1newbie
View challenge

Design comparison


SolutionDesign

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm mostly proud of how I was able to figure out more "recent" CSS stylings such as drop shadows, transformations, etc. on my own. I also wanted to get as close as I could to the design from eyeballing the visual image only, not extracting the numerical values from the Figma file.

I'm also pleased at how much faster I was able to complete this compared to previous micro projects / components.

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

The question was whether to nest the anchor tags inside their relative DOM elements, or place the DOM elements inside anchor tags. I decided to go with the latter because if this were a full-site design system or theme, there could easily be a case where h3 elements are NOT meant to also be hyperlinks and I didn't want the stylings to be tag-nesting dependent.

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

I used a fixed size since this is a card component. When it comes to responsive designs I'm good with full site and section layouts, but any micro changes to smaller in-page components are not as intuitive to me for some reason.

I would like to know if there's a way to make this (especially the text) slightly responsive without using a hard break point for elements other than the card body itself

Community feedback

Tayler 50

@AbraKadabraPuf

Posted

An interesting option for executing all the code in HTML. Personally, I find it more convenient to divide the code into: html, css, js

0

@Micahtron

Posted

Usually I keep things separate too, however since this is a component piece which will likely be used in other systems I figured it'd be more convenient to keep everything in one file since it's small. That way including it in another theme/build or design system is simply a matter of including the single file and taking only the necessary code.

1

Please log in to post a comment

Log in with GitHub
Discord logo

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