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

Blog preview card using HTML and CSS

waru-guru•60
@waru-guru
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My code is not being built and deployed in github and therefore my live site url doesn't show the design I made. Can I get help with that?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Parves Hossain Rabby•560
    @Iamparves
    Posted over 1 year ago

    There is a minor error when adding CSS files to HTML. When you put '/' at the beginning of the path, it looks for that path directly from the main domain or root, which in your case is just after https://waru-guru.github.io, resulting in the final CSS file path https://waru-guru.github.io/static/assets/css/styles.css.

    However, your CSS file is stored at https://waru-guru.github.io/blog-preview-card/static/assets/css/styles.css. So instead, use a relative path. Simply add a dot (.) in front of the path, and it should work.

    Correct this: <link rel="stylesheet" href="/static/assets/css/styles.css

    To this: <link rel="stylesheet" href="./static/assets/css/styles.css">

    Edit: I noticed you also did same mistake for the avatar image. Fix that too.

    Marked as helpful
  • Don•380
    @eldon6219
    Posted over 1 year ago

    hello @waru-guru after you create the repositry in Github go to the repositry's setting and find the code and automation aside to the left

    find the pages and change the branch from none to main (/root) it will generate and live url for your work and you can show your work perfectly ! hope u find this helpful and happy to help anytime ! happy coding

    Marked as helpful
  • Saleiux•230
    @Saleiux
    Posted over 1 year ago

    Hi! it's normal that you didn't built your website with github! Normally developers use an editor to build the code (like vs code). It's easier. After you create your code in an editor you just need to create a new repo on github and follow the guidelines (there are also many videos on youtube about that, but it is a very simple process) and after for put online your website you can use a platform like netflify that will use your code on github to deploy the site. I hope I explain in a easy way myself and you understood! good luck!

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

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