Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

HTML CSS BEGINNER

Kate•30
@unic0rnKate
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please don't judge me hard, i am completely beginner, have some mercy ok? :) i found difficult to make a boarder-radius of my image and description div, because they will change their border-radius separately and not gonna look as one box with rounded corners.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chris Andrews•170
    @ChrisAndrewsDev
    Posted almost 3 years ago

    Howdy @unic0rnKate!

    Don't worry, everyone seems very friendly on here (I am new too!) and usually give really good feedback.

    I did notice that your styles don't seem to be applying to your solution, and it looks to me that your relative linking is slightly incorrect:

    <link rel="stylesheet" href="css/styles.css">

    Should be changed to

    <link rel="stylesheet" href="styles.css">

    Typically the "/" denotes a parent folder - "parentFolder/itemInsideFolder" and since you don't have a "css" folder, you shouldn't need to use that!

    Once you've fixed that small issue we can have a look at the design implementation! Good luck :)

  • Alabi Olalekan Emmanuel•280
    @Lekanjoy
    Posted almost 3 years ago

    We are all here to help each other Kate. I can't seem to view either your live site or the code. Make sure you check again and update the right links.

    As Chris said, it might be that your relative linking is wrong. If you have your styles in a different folder in your workspace is when you use

    <link rel="stylesheet" href="yourCssFolderName/styles.css">

    but if your style file is not in any folder you just omit the folder name.

    Concerning the border-radius, it works in a clockwise direction, meaning border-radius: top, right, bottom, left. You can also specify each value distinctively.

    Hope this helps..

  • Alieu•190
    @alieuk61
    Posted almost 3 years ago

    It's ok, we're all trying to get better, your css isn't showing as Chris said however when you fix it I can come back and try to give some 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

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