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

HTML, CSS, TailwindCSS

tailwind-css
Colin McArthur•140
@ColinMcArthur85
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Im feeling pretty confident now that Ive built out a few of these card components so this time, based on the advice of someone in the Slack channel, I decided to implement TailwindCSS into the project. I implemented using the CDN just to take it for a 'test drive' and after a little while was surprised at how effective (and simple) using it was. By the end, I sort of felt like I was cheating.

Aside from a few media queries (which Im sure I can use Tailwind for) I didn't use any of my own CSS which allowed me to get this project done in a timely manner and, well, it just worked! Barely any troubleshooting is needed.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 3 years ago

    Hi

    As well as the styling issues I raised on slack with the Screenshots, I notice problems with the html here

    You have some text in divs and spans alone, not meaningful elements.

    You also have what should be an interactive element as a div for cancel I think (?)

    It's really important to choose the right elements and not neglect that. Right down to when you're using buttons vs anchor tags. Eg on this why is change an anchor link and proceed a button? What would you expect to happen if someone clicked each of these? That determines which element has to be used in each case

    Make sure you don't remove the gitignore files from these challenges too. You get one in the starter files and need to keep that in your repo

    Good luck with it

    Marked as helpful
  • Ivan•2,610
    @isprutfromua
    Posted over 3 years ago

    Hi there. You did a good job 😎

    keep improving your programming skills

    your solution looks great, however, if you want to improve it, you can follow these steps:

    ✅ place the Google import code such that it loads first directly after the html HEAD tag, EVEN before loading the CSS file. This ensures the fonts load before the CSS so there isn't any unexpected "jumping" of when the font finally loads.

    @import url("https://fonts.googleapis.com/css2?family=Red+Hat+Display:wght@500;700;900&display=swap");
    
    to
    
    <link rel="preconnect" href="https://fonts.googleapis.com">
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
    <link href="https://fonts.googleapis.com/css2?family=Red+Hat+Display:wght@500;700;900&display=swap" rel="stylesheet">
    

    ✅ no reason to use universal selector twice

    * {
      margin: 0;
      padding: 0;
    }
    
    *,
    *::before,
    *::after {
      box-sizing: border-box;
    }
    
    

    ✅ you have an separated tailwind config, but placed configuration into the html file.

    tailwind.config = {
            theme: {
              extend: {
                colors: {
                  "pale-blue": "hsl(225, 100%, 94%)",
                  "bright-blue": "hsl(245, 75%, 52%)",
                  "very-pale-blue": "hsl(225, 100%, 98%)",
                  "desaturated-blue": "hsl(224, 23%, 55%)",
                  "dark-blue": "hsl(223, 47%, 23%)",
                },
              },
            },
          };
    

    ✅ remove an empty style.css file

    ✅ there is no reason to have separated css file at all. You can simply add this properties with tailwind.

    I hope my feedback will be helpful. You can mark it as useful if so 👍

    Good luck and fun coding 🤝⌨️

    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 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