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

Blog preview

Jordan•20
@jordan1166
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?

Turning a design into a real website

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

Getting website to be just like the design

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

none

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Albert Celestino•20
    @1lbert
    Posted about 1 year ago

    Hi Jordan, as a fellow newbie, here's the following I saw in your layout.

    Border - the layout must have a border of black, Class - although it's not necessary, it must be better that our elements must have a certain class name as a distinction, this may also help as we style this in our CSS file. Responsiveness - the layout is not responsive on the Small screen, especially on a 320px device. instead of giving a fixed width to your "main" element, try to replace it with a min-width at wider devices and a maximum width at smaller devices. Height - one thing I learned from our colleague here is that avoid a height of 100vh, instead use min-height: 100vh to avoid overlapping when the smaller device is in the landscape. also, avoid giving fixed px quantity in height and width, it may affect your responsiveness in other devices CSS Reset - add CSS reset when designing in CSS. you can search for it and apply it to your code.

    That's it, I hope I can help you on your journey.

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 1 year ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have a suggestion regarding your code that I believe will be of great interest to you.

    ADDING HOVER STATE 🪄:

    • Looks like the component hover state with box-shadow has not been set yet. Your solution would be perfectly finished if you add this as a finishing touch!

    • Just add the following css rules
    main {
      transition: box-shadow .3s;
    }
    
    main:hover {
      box-shadow: 12px 13px 0px 1px rgba(0,0,0,0.93);
    }
    

    • Now your component's hover shadows has been set properly

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub