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

i used css styling nothing extra

bootstrap
SigneWinnie•20
@SigneWinnie
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 happy about the fact that i am improving on my css skills

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

what i encoutered was being able to separate the paragraphs and being able to align the image with the text

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

javascript and css

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tharun Raj•1,330
    @Code-Beaker
    Posted 10 months ago

    Hi there, congratulations on completing this challenge... 🎉 Unfortunately, it looks like you've submitted the solution for a different challenge. 😢

    Currently, the live site URL displays your README.md file. You have to move the index.html file to the root of your directory and publish the page again. Alternatively, you can use a tool like Vercel to publish your site where you will be able to edit the root directory of your website while deploying it.

    I want to share some of my suggestions regarding the source code you've shared.

    • Do not use % to define widths, heights, etc. It breaks the site's responsiveness and is harder to maintain on different screen sizes. Instead, use rem or em units. They're relative and are easier to define and manage.
    • Use CSS Custom properties/CSS Variables to make your CSS reusable and cleaner.
    • Use rem to create font-size. NEVER use px to define font-size. Read this article which explains why this is important.

    I hope you find it 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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub