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

Profile-card

Adam.Codes•180
@AdamCodes42
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This Challenge looked very easy at the first but as a beginner when I started this challenge I came across the background elements which made it difficult to use flex box and also had to use negatives values. My code Need a review from some expert I may have messed up 😅.But learned new things too.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Faris P•2,810
    @FarisPalayi
    Posted about 4 years ago

    Good work on this one👍

    • About positioning the background image, using CSS background-image property could make things much easier, and also it is more flexible with the help of related properties like background-position and background-size. Or you could use a CSS pseudo-elements like ::before or ::after for this.
    • Also, those images are purely decorative, so set the alt tag to empty alt="", so that screen readers and other assistive devices can ignore them.
    • Victor's image's alt text shouldn't be "profile-img", it should be something descriptive like Victor's name or something like that.
    • Furthermore, try to clear the issues in the reports section if you can.

    I suggest you to take a look at these articles if you can:

    • HTML: A good basis for accessibility
    • Semantic HTML5 Elements Explained

    I'm not at all an expert in these things, so, do your own research and if there are mistakes on my part, let me know😀

    Have fun coding✨

    Marked as 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

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