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

Order summary component with Tailwind

tailwind-css
Limbert Lino Mattos•40
@linomattos
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I learned a lot from this challenge! I have a question, when I configure the background images in tailwind, they only work for me in development. These images disappear when I open the index.html file, the reason I find is because of the absolute paths with which I call them. I don't know how to put them when I have the configuration file outside the folder that has my final code.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muhammad Waleed Ahmed•270
    @WDWaleed
    Posted almost 2 years ago

    Hi there. For images, you should directly specify them in the src attribute of the img tag but for background images you can configure the tailwind config file by extending the theme:

    theme: {
          extend: {
              backgroundImage: {
                    TheImg: "url('/images/the-img.png')"
              }
          }
    }
    

    After this, you can use it in your classes like this:

    class="bg-TheImg"
    

    I hope this helps, but if not then let me know and I'll look for a different approach.

    If you like, here is a real-world example from one of my projects but I use ReactJS so it has a different setup. Just note the extended theme in the tailwind config:

    /** @type {import('tailwindcss').Config} */
    export default {
      content: ["./index.html", "./src/**/*.{js,ts,jsx,tsx}"],
      theme: {
        extend: {
          screens: {
            custom: "750px",
          },
          colors: {
            Cyan: "hsl(176, 68%, 64%)",
            Blue: "hsl(198, 60%, 50%)",
            LightRed: "hsl(0, 100%, 63%)",
            IntroBack: "hsl(217, 28%, 15%)",
            MainBack: "hsl(218, 28%, 13%)",
            Footer: "hsl(216, 53%, 9%)",
            TestimonialsBack: "hsl(219, 30%, 18%)",
          },
          backgroundImage: {
            Intro: "url('/images/illustration-intro.png')",
            CurvyDesktop: "url('/images/bg-curvy-desktop.svg')",
            CurvyMobile: "url('/images/bg-curvy-mobile.svg')",
            ProductiveIllustration:
              "url('/images/illustration-stay-productive.png')",
            Arrow: "url('/images/icon-arrow.svg')",
            Quotes: "url('/images/bg-quotes.png')",
          },
          fontFamily: {
            Raleway: ["Raleway", "sans-serif"],
            OpenSans: ["'Open Sans'", "sans-serif"],
          },
        },
      },
      plugins: [],
    };
    
    

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.

Oops! 😬

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

Log in with GitHub