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

Profile Card Component using custom css properties.

accessibility
Akshita 👩‍💻•340
@Shanvie
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Yeah everyone.. Good Afternoon .. Here is my third project and any suggestion for this project you want to tell is welcome ..Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • HutHut•310
    @j-hutchison
    Posted about 3 years ago

    Hi Akshita,

    Great job on this component!

    I'm still on my journey to improve my front-end development skills, but a couple of things that have helped me with structuring my CSS and HTML better are:

    • Give all html elements a class name, this will help simplify your css instead of nesting element selectors --> To help with this you can look into a naming methodology called 'BEM' (Block Element Modifier) - sometimes it can look a little unsightly but i think it is worth it on larger projects and also if you work with SCSS in the future

    Above all great work and keep it up 👍

    Marked as helpful
  • Akshita 👩‍💻•340
    @Shanvie
    Posted about 3 years ago

    Thank you ...It will help me a lot for my next projects And I also say best of luck for your next project or challenge in this platform :D

  • Ahmed Bayoumi•6,680
    @Bayoumi-dev
    Posted about 3 years ago

    It looks good Akshita! I suggest you put the status of the profile card into the list item to add more semantics to your project, Div's don't do much for semantics but a list is much more meaningful..:

    <ul class="stats">
       <li><span class="stats-num">80K</span>Followers</li>
       <li><span class="stats-num">803K</span>Likes</li>
       <li><span class="stats-num"> 1.4K</span>Photos</li>
    </ul>
    

    I hope this is useful to you... Keep 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
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