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

Results Summary Component

Sadeesha Jayaweera•240
@SadeeshaJayaweera
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Seeking Code Review and Suggestions for My Project**

Hi everyone,

I hope you're doing well. I'm reaching out today to request your valuable insights and suggestions regarding a project I've been working on. I've recently completed coding a project using only HTML and CSS, but I'm aware that it may not be matching the ideal solution. I'm particularly interested in making it responsive for different resolutions and improving the code to better align with the project's goals.

Before diving into the details, I'd like to ask a few questions for your feedback:

  1. Have you encountered similar projects before, and do you have experience in making web projects responsive?
  2. What are the key considerations for ensuring a project is responsive across various screen sizes and devices?
  3. Are there any best practices or CSS frameworks that you recommend for responsive web design?
  4. How can I optimize my HTML and CSS code to better meet the project's objectives?

Your insights, guidance, and suggestions are highly appreciated. I'm open to constructive feedback, and I believe your expertise can help me enhance the project's overall quality and user experience.

Thank you in advance for your assistance, and I look forward to hearing your thoughts.

Best regards,

Sadeesha

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Sadeesha Jayaweera'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.