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

Blog Card Project using React-Vite-Tailwind

react, tailwind-css, vite
RappyProg•30
@RappyProg
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?

On this project i am quite proud of the better understanding of the tasks. I didn't quite see the readme or style-guide on the last project, but i have safely followed the guide this time.

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

Challenges came when i was messing around @media screen to see whether it's phone or pc size.

Thankfully i already made it responsive from the start, so it's not a huge problem.

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

I have little to no difficulty on this project. I would love some feedback instead.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • haquanq•1,675
    @haquanq
    Posted 12 months ago

    Hellooooo @RappyProg 👋👋👋

    Nice work on the challenge, it look similar to the design!!

    Here is some other things that can be improved:

    • Each page should have one main landmark which means wrap you most important content of the page inside it (there are other landmarks).
    • Using more semantic HTML markups and keep your HTML simple like article, section, time,.. . For example you can wrap entire card inside article or just it's content (except image).
    • figure is being misused here, figure is often used along with figcaption and wraps around contents to give it extra details/explanations (SEO and accessibility improvement ) - could think of it simply as a label/caption (not only for images, can be a list, a long paragraph,... ). Here you are using figure for an image with zero context and it is redundant, leave only the img alone is fine.
    • Consider add some transition to your hovering events:
    transition-property: properties name (color, background-color, outline, border,...)
    transition-duration: time of ms (micro-second)
    transition-timing-function: ease/ease-in/... (transition behaviors)
    
    /* shorthand it looks like this*/
    transition: color 200ms ease;
    

    There is a small detail that you may have missed, when you hover the title the black shadow will move!!! You can check out my solution to see (don't look at my code and try to build it yourself, it's interesting)

    Hope this help 🙀🙀

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