Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

Responsive meet page using tailwind CSS

tailwind-css
P
V.S Karthik Tirumalasetty•130
@VSKarthikT
A solution to the Meet 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've just started learning Tailwind CSS for this project and am excited to have implemented a responsive page! Responsiveness has always been a bit tricky for me, especially dealing with overlapping elements when using absolute positioning, but I feel like I've finally got it figured out

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

At first, I found Tailwind’s syntax a bit challenging, but the website’s documentation was super helpful, and now I’m much more comfortable with it. Positioning hero images was a bit tricky too—I wanted them to overflow the parent container and touch the viewport edges. I figured it out by using negative margins, and it’s looking just right now!

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

I’d like some guidance on effectively using mixins or reusable styles in Tailwind, similar to how CSS handles mixins. I’m curious if there’s an efficient way to apply repeated styling patterns across multiple components without adding redundant code.

Additionally, I’ve noticed my HTML tags are getting cluttered with a lot of classes, making them look a bit unwieldy. Are there any strategies or best practices in Tailwind for keeping my code cleaner, especially when it comes to managing lengthy class lists? Any tips on optimizing readability would be great!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Erik S. Carlsten•290
    @ecarlste
    Posted 3 months ago

    Nice job getting your responsive UI to work the way you wanted it to in tailwind.

    It looks like the paragraph text in the first two sections is expanding farther than the design. The top hero section text should be the same width as the heading above it. The second heading and that section's paragraph text are also expanding farther than the design looks to intend.

    The footer section looks to be laid out in a column rather than a row, so you might want to take a look at getting it to flex as a row rather than a column for large screens.

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