Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Community single page grid

Yusuf K. Muhammad•570
@kyusufm
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


using flex grid,

Please give suggestion on improving the css-code or html tag.

Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your Single Price Grid Component project, Yusuf! 🌟 Your dedication and hard work are evident in the code you've written. Here are some best practices and recommendations to further refine your project:

    1. HTML Best Practices:

      • Semantic HTML: Great use of semantic elements like <main>, <section>, and <footer>. Continue this practice for better SEO and accessibility.
      • Image Alt Text: Ensure all images have descriptive alt text for accessibility.
    2. CSS Styling:

      • CSS Variables: Excellent use of CSS variables for colors. This makes it easier to maintain and update your styles.
      • Responsive Design: Good job on making the design responsive. Consider testing on various devices to ensure compatibility.
    3. Code Efficiency:

      • DRY Principle: Avoid repeating styles. Group common styles together and use classes to apply them.
      • Media Queries: Consolidate your media queries for better readability and maintenance.
    4. Accessibility:

      • Keyboard Navigation: Ensure that all interactive elements are accessible via keyboard navigation.
      • Contrast Ratios: Verify that text and background colors have sufficient contrast for readability.
    5. Performance:

      • Minimize CSS and JavaScript: Minify your CSS and JavaScript files for faster loading times.
    6. Code Organization:

      • External Stylesheets: Keep your CSS in external stylesheets instead of inline for better organization.
      • Commenting: Use comments to describe sections of your code for easier navigation and maintenance.
    7. Further Learning:

      • Flexbox and Grid: Continue exploring CSS Flexbox and Grid for more complex layouts.
      • CSS Frameworks: Experiment with CSS frameworks like Bootstrap or Tailwind CSS for rapid development.
      • Learning Resources: Explore MDN Web Docs for detailed guides and documentation.

    You've done a fantastic job on this project. Keep challenging yourself with new projects and technologies. Your progress is impressive, and I'm excited to see what you'll create next. Keep up the great work, and happy 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

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