Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

Used HTML5, CSS3 (Flexbox, gradients, media queries), and SVG for mode

Sudharshan Murugan•50
@SudharMurugan
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

What I’m most proud of: I take pride in my implementation of a fully responsive layout utilizing CSS Grid and Flexbox, guaranteeing an aesthetically pleasing design across diverse screen sizes. I am also confident in optimizing SVGs for enhanced visuals and reduced load times.

What I’d do differently next time: In the future, I would prioritize enhancing accessibility through the implementation of ARIA roles and improved keyboard navigation. I would also consider utilizing a CSS preprocessor such as SASS to enhance style organization and improve codebase maintainability.

What challenges did you encounter, and how did you overcome them?

Challenges I encountered: A primary difficulty was maintaining layout consistency across various screen sizes and browsers. Another challenge involved managing the design particulars, like the precise alignment of SVG icons and the conformity of spacing with the design criteria.

How I overcame them: To resolve the layout problems, I employed CSS Grid and Flexbox to establish a versatile structure and conducted comprehensive testing across various devices and browsers. To ensure design precision, I utilized browser developer tools and applications like as Figma to accurately measure spacing and alignment. In the event of issues, I consulted MDN documentation and community forums for resolutions.

What specific areas of your project would you like help with?

I would like feedback on the following areas of my project:

Responsive Design: Are there any improvements I can make to ensure better responsiveness across devices, especially for smaller screens?

Accessibility: Did I miss any important aspects of accessibility, such as proper ARIA attributes or color contrast?

Code Structure: Are there ways to make my CSS and HTML code more organized or reusable? Any suggestions for improving my file structure?

Performance Optimization: Are there areas where I could optimize the performance, such as reducing redundant CSS or optimizing images further?

Best Practices: Am I following current best practices in front-end development, or are there any modern tools or techniques I should consider?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Sudharshan Murugan's solution.

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.