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

Workit responsive landing page ft. 11ty, CUBE CSS, and Tailwind

accessibility, cube-css, eleventy, tailwind-css, nunjucks
Josh Javier•930
@joshjavier
A solution to the Workit landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Yes, I finally tried Tailwind! I used it quite conservatively in conjunction with CUBE CSS, which means I still wrote component-based classes instead of taking a utility-first approach. But I definitely see the benefit of using Tailwind, especially for rapid UI development during the early phases of a project. I especially like how it can process design tokens and convert them into CSS custom properties that I can use in my code.

The source code of Build Excellent Websites is my primary inspiration for this project. I tried my best to practice the principles in that site, which is why I only used 2 media queries for this solution (not counting the ones in resets and config files). The rest of the layout are handled by utility classes, such as the Switcher a.k.a. the Flexbox Holy Albatross by Heydon Pickering.

I think I also gained more confidence working with SVG:

  • For the logos, I used inline SVG in the header and footer instead of <img> tags.
  • I combined the social media icons into an icon sprite embedded in the page, which avoids extra HTTP requests.

I still have to add those oval/spring patterns, but other than that, it's almost done.

Please let me know what you think! Do you think I could've used Tailwind more effectively for this project? Any feedback on code structure/organization?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mandriva 19•330
    @mandriva19
    Posted almost 2 years ago

    very impressed with this solution. it's clean and responsiveness is on point. the way project is structured is peaceful @ ~

    thanks for providing helpful resources!

    also the hardest part of completing FEM challenges for me, is positioning background images on the responsive layout. seems like you have nailed that with calc function, I usually write 40 lines of css and it's still breaks xD

    .... Just opened the page if Firefox (latest) and it renders content quite weirdly. https://i.imgur.com/WzRsT8k.jpg

    Good luck!


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

Oops! 😬

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

Log in with GitHub