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

Single Price Grid Component đŸŽ¯ [ SEMANTIC MARKUP - CSS GRID - BEM ]

accessibility, bem
Abdul Khaliq 🚀â€ĸ72,380
@0xabdulkhaliq
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


👾 Hello, Frontend Mentor coding community,

This is my solution for the Single Price Grid Component.

  • Feel free to leave any feedback and help me to improve my solution (or) make the code clean!
  • Had a lots of fun building this challenge !
  • Got some experience in handling layout with css grid
  • Layout was built responsive via mobile first workflow approach

CUSTOM TWEAKS..🚀 :

  • Added button clicked effect by styling the transform property for :active pseudo-class

👨‍đŸ”Ŧ Follow me in my journey to finish all newbie challenges to explore solutions with custom features and tweaks

Ill be happy to hear any feedback and advice!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alperâ€ĸ1,090
    @adonmez04
    Posted over 2 years ago

    Hi, @0xAbdulKhalid. It's a good solution. Keep coding. I have some suggestions for you.

    1 - You don't need the CSS Grid for 1-direction flow. They match perfectly with the flexbox. Use flexbox 1-direction flow. In this project, you can just use the margin for whitespace. Keep it simple. CSS Grid is a good solution to 2-dimensions layout and complex components. CSS Grid usually uses a general page layout.

    2 - You can use ul > li for main__third-section area, . All ordered or undered list areas are natural ul items. Here is a nice sample of it. Use just ul > li.

    I hope these will help you to improve your perspective. Keep coding. All the best.

    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
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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! đŸ˜Ŧ

You need to be logged in before you can do that.

Log in with GitHub