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

Profile Card Using HTML and SCSS

sass/scss
Achmad Riyadi•70
@AchmadRiyadi
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any suggestion to place the footer at the bottom?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted over 3 years ago

    Hello @AchmadRiyadi ,

    I have some suggestions regarding your solution:

    • Those 2 blobs images could be used as background value. This way, you won't have to create those 2 div.

    • Footer goes outside of main, not within it . So on this page, you would have a markup that looks something like this:

    <main>
    <footer>
    
    
    • In class="card__footer">, those stats need to be an unordered list<ul> with 3 list items. The number and word have to be read together to make sense so need to be in the same meaningful element(list item ). so only a span or maybestrongtag needs to wrap the numbers.

    • For <img src="./images/bg-pattern-card.svg" alt=""> decorative image, img tag should has empty alt="" and aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images. (even though it doesn't need to be in html ).

    • img src="./images/image-victor.jpg" alt=""the alternative text shouldn't be empty as it's an informative image. you can use the the avatar's name (Victor Crest). I would suggest to read more about alt text for informative and decorative images.

    • It's never a good practice to have font size in px.

    • You should use em and rem units .Both em and rem are flexible, scalable units . Using px won't allow the user to control the font size based on their needs.

    Hopefully this feedback helps

  • Abdellah el aajjouri•190
    @abdellahelaajjouri
    Posted over 3 years ago

    Hey men Good job working this challenge. You solutions looking very good to place the footer you can just use the margine property or give him positions absolut then change the placement where you want. Keep up with the good work

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