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

Html CSS

P
Patrick•14,265
@palgramming
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


First Challenge I have posted here

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt Studdert•13,611
    @mattstuddert
    Posted almost 5 years ago

    Nice work, Patrick, and congrats on submitting your first solution! Here are a few pointers after taking a look at your code:

    • You're using heading elements when I'd say paragraphs would be better suited. For example, I'd say the "Gain access to our full library..." text is a paragraph, not a h3.
    • You're using HTML5 structural elements which is great. But I would say you could use the article and section elements better. An article is typically used to contain distinct content that could live independently from the rest of the content on the site/page. Good examples of this would be blog posts, articles, and forum posts. A section is typically used to wrap a larger grouping of themed content. For example, the whole Slack sign up area below these comments would be considered a section. For smaller groupings of content I'd then use div elements. So for this challenge, I'd say the whole thing is a section and the inner areas are just div elements.
    • I'd use a ul for the list of benefits/features as opposed to br tags.
    • The whole component could also have its width restricted so that it isn't quite so wide.

    I hope these tips help. Let me know if you have any questions! 👍

  • P
    Patrick•14,265
    @palgramming
    Posted almost 5 years ago

    Thanks for the feedback. I think on the designs that are to be fixed width maybe in design photo it should show that element inside another example layout it might help understand the usage for what is being designed . just like a wire frame image with the little block inside showing the wire frame grow and shrink and the different widths

    yes and not using UL for the list when I just got lazy and typed BR #Thanks

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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