Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive landing page using Tailwind CSS

P
Matt Pahuta•650
@MattPahuta
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm pretty happy with how the mobile/desktop navigation menu turned out. There are some finer styling details that can surely be improved, but it's probably one of the more semantically proper and accessible hamburger menus I've implemented here. This is largely thanks to Jessica Chan's excellent video tutorial (linked and acknowledged in my project Readme) on the topic.

What challenges did you encounter, and how did you overcome them?

I spent a fair amount of time wrestling with integrating the updated pure CSS for the mobile nav functionality (that I was comfortable with) with the Tailwind code I had originally put in place. Ultimately, I left most of the heavy lifting of the menu to the vanilla CSS and JS.

What specific areas of your project would you like help with?

I'm definitely still learning to become proficient with Tailwind, so there's certainly a lot of areas around class usage I can improve upon. Being new to the framework, it's difficult to gage if my html is overly polluted with classes, especially given the layout isn't the most complex. Of course, proficiency will come with time and practice but I'm happy to receive any and all feedback on my Tailwind implementation.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Matt Pahuta's solution.

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.