Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Mobile First, HTML Tailwind CSS

William Anthony•240
@wpittman06
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Mobile design DOES works and am pretty proud of it. Desktop design is absolutely broken as you can see in the preview (sigh), and I have no idea where to start. I used Tailwind CSS for this project and its my first full foray into it and wanted to practice it. My breaks work until you enlarge the screen and my design breaks I followed some other devs and I went with the assumption we all shared screen size and everything was working UNTIL i went full screen. How does one figure out media query breaks? Any insight into my design is VERY much appreciated.

Also whenever i put folders in the Github repository it never sees my work and i have to drag and drop the actual files for Git to see my actual stuff. If you look at my other projects that say "files not found" you can actually click on the projects and will be taken to them but they aren't shown for some reason. Anyone have a fix or suggestion as to how i might do better uploading my files?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chris•740
    @chrisbailey85
    Posted about 4 years ago

    I have not used tailwind before myself but you seem to be on the right track for mending the desktop. On your .showcase div if you add a grid template rows to it so you've got two rows instead of one, and then hopefully it should just be a case of placing everything in the correct rows and columns. Good job on the mobile size's it looks good.

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    yes in your code you are saying your images are in a images folder but they are not on the web-server. remove the "/images" in your image links and they will load

  • Radoje Jezdic•70
    @Jezda1337
    Posted about 4 years ago

    src for star images are not good, you have to check the path, and name of the SVG image. And check tailwind docs for more info about responsiveness :) gl

  • Take a Look•170
    @hukhwan
    Posted about 4 years ago

    god....

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

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

Oops! 😬

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

Log in with GitHub