Why we choose Tailwind over Foundation for Elements

Elements
1

Hello again,

“Why Tailwind over any other CSS framework?” I hear you cry. Well, I’m glad you asked…

We just published a video that looks at why Foundation CSS is showing its age, and why so many companies, designers, and developers have moved over to Tailwind CSS, including us!

As you hopefully know, Elements is built on Tailwind CSS, the most popular utility-first framework on the web. But it’s important to note, Elements isn’t locked into Tailwind. To prove this, we produced a proof-of-concept demo of Foundation running in Elements :scream:

We chose Tailwind because it’s the best option right now. If something better comes along in the future, no problem, Elements is designed to evolve!

Note: This video is quite technical in places, but it gives a good overview of why you made the right choice in picking Elements (and Tailwind) over anything else :wink: Check the description on YouTube for chapter markers.

Elements x Tailwind

At the heart of Elements is Tailwind CSS, a modern, utility-first framework that gives you total design control without writing custom CSS.

Every component and layout in Elements is built using Tailwind’s powerful classes.

Because Tailwind is so flexible, we can offer built-in components like Forms, Galleries, and CMS integrations that are lightweight, responsive, and easy to style and extend via the Theme Studio, all without compromising on accessibility or performance.

Tailwind was first published in November 2017, and has seen a steady stream of updates and huge improvements.

Tailwind is the most popular CSS Framework

Tailwind is the most popular CSS Framework on the planet, it’s used and trusted by some of the biggest bluechip companies in the world, including: Netflix, NASA, OpenAI, Shopify, Microsoft, GitHub Next, Google I/O, and many more.

In recent years, Tailwind has exploded in popularity, it’s seen 20× growth in just four years, and it’s still accelerating.

Year Weekly Downloads
2021 859,312
2022 2,981,473
2023 6,419,291
2024 9,463,256
2025 19,349,210

Benefits of using Tailwind in Elements

We built Elements around Tailwind because it gives you the most flexibility, performance, and modern best practices. It’s:

  • Fast, lightweight, and SEO-friendly
  • Accessible by default
  • Customisable without limits
  • Actively maintained and rapidly evolving

Better for performance and SEO

Tailwind (and Elements) uses a just-in-time compiler that generates only the CSS you actually use. That means:

  • Smaller files (often under 10kB!)
  • Faster load times
  • Better scores for Google’s Core Web Vitals
  • Higher rankings in search

Accessibility, built-in.

Tailwind also helps you build accessible websites out of the box:

  • Great support for keyboard navigation and focus styles
  • Encourages semantic HTML and good colour contrast
  • No hidden accessibility nightmares.

By building Elements around Tailwind, we ensure that your websites are performant, future‑proof, and made with best‑in‑class front-end technology.

Tailwind powers some of the best websites on the internet, and now it powers yours too, with Elements!

Download Elements for Mac

We think Elements is the best visual Tailwind builder on the planet, download the demo today and see what all the hype is about!

Thanks,
Team Elements

6 Likes
2

Ouch. Dan 1, Joe 0.

It’s becoming more clear to me what the real complaint from the Foundation group really boils down to. Particularly since you’ve shown that the Foundation framework can work within the Elements app just as it can in the Rapidweaver app. Something tells me that the Foundation folk won’t bother to build out their framework for Elements as you started to do, because it just exposes the difference, and the only ones that would want to work that way are those that want to preserve their Foundation site as is (which they can do currently, anyway).

I’d also like to acknowledge that you did the right thing here by using real examples, real data, and real information, while Joe has only sniped and innuendo-ed. Thank you for taking the high road. And thank you for Elements. Ever since I saw the very first demo I’ve realized that it’s going to change how a lot of us do Web design. While I’ve yet to deploy any of my sites in Elements (still need that CMS, Ben), I’ve spent a lot of time prototyping ideas, and Elements is perfectly suited to that. Still haven’t made any final decisions yet, but I’m pretty sure my eventual sites will be everything I want them to be.

3 Likes
3

So it took 59 mins to make a 43 minute video, it took “about 1 hour” of prepping so two hours in total. It took me 43 minutes to watch video, so here’s my summary:

You can use foundation (Zorb version) in Elements, but you can not use Elements in Foundation 6 ( JW version). Foundation is not updated as frequently as Tailwind. There’s been loads more downloads of Tailwind than other CSS Software. You can do loads in Elements that easier than F6. However there are hundreds of stacks for themes and styling - not mentioned for F6 (JW Version). Now as a user of Elements in an ELements forum I appreciate the “Mac v Windows” videos but I would like CMS. From a user perspective it would have been more beneficial for you to spend two hours on CMS rather than this. Summary took 3mins and 46 seconds to type. Please lets have CMS to add to NON BET Elements 1.0. WELL DONE GUYS FOR YOUR ACHIEVEMENTS!! Next video POST CMS can we do how to use stacks (NOT Stacks) in Elements! That would be a killer!

1 Like
4

We’re absolutely still working on CMS. It’s a big feature, and we know how much people want it. That said, sometimes we have to spend time on other things (like marketing, videos, and onboarding improvements) to help attract new users to Elements.

The simple truth is, if we don’t grow the user base, we won’t be able to keep developing the product. So while the CMS is super important, so is making sure enough people actually discover and use Elements in the first place.

We’re doing our best to balance everything. CMS is coming, and we’re just as keen as you are to get it out the door.

2 Likes
5

Thanks for the nice feedback, it’s reassuring to know we’re on the right path :smiling_face_with_three_hearts:

The CMS is coming along very nicely :hugs: Here’s a sneak peek at a simple blog project I’ve been working on for inclusion in Elements…

CleanShot 2025-07-31 at 4 .28.57@2x
CleanShot 2025-07-31 at 4 .28.57@2x1920×2038 783 KB

6

I was only being mischievous! :slight_smile: As I said “WELL DONE!” I think we just all want to try CMS after teaser videos so therefore your marketing has worked! :slight_smile: too well in the CMS instance! :slight_smile: :slight_smile: :slight_smile:

1 Like
7

Having been in the situation where the customer insists they need ‘x’ now an I kept telling them it wasn’t ready, then being forced to deliver it early, I know that it just ends in bad news from customers who say it doesn’t work properly.
Don’t be forced to deliver the CMS early. Everything else is superb, don’t spoil it with a less than working delivery of CMS :slight_smile: Keep up the good work

1 Like
8

Okay, but “making sure enough people…” will actually be helped immensely by delivering the CMS. It answers more problems than just blog, but blog alone will get people’s attention. I know several people who right now are passing on Elements because it doesn’t have that feature.

Here’s my bet: the day you actually ship CMS Elements purchases will go up, and the more people hear about it, the faster the purchase ramp will be.

Your CMS, even without the standalone editor, will also be a bit of a thorn in Joe’s side. Frankly, his CMS may be pretty full featured, but it’s a mess to set up and style. At the moment, he seems to think his CMS is the thing that saves Stacks, and I just don’t see that.

Also, another complement: your videos are better, more to the point, don’t wander, and easier to take in than your competitor’s. Video (and streaming) is a way to lower the amount of information conveyed compared to writing, and when you then lower it some more by straying and repeating and pontificating, the information content per minute drops precipitously. You’re to be commended for keeping your videos high in content per minute, right up there with the best.

2 Likes
9

When people are choosing the tools they are going to use they often want to know what the future holds. This is easily the most powerful statement of the entire post for me. Why? For the reasons stated, not locked into an ecosystem. I know Elements is a ecosystem in itself, but if some strange thing that happened beyond RM control it would not upset the business.

The life blood of a business is sales. This is a powerful sales pitch for a developer concerned about the future of their tools.

1 Like
10

You didn’t read my second post. I was being flippant just adding another CMS when opportunity. As someone who runs a business and has his website done in RW/F6 and Cartloom currently and is looking to go/or not the new Elements or Stacks/F6 route I appreciate your view. However IMO if Elements can have a CMS this itself will be the wow factor that will make more people want to look at going over to the Elements route. If you want to a powerful statement for Elements then just watch JW Video of a few days ago Stacks v Elements :rofl:

1 Like
11

My 2 Cents: It is basic to have an online editor to give to clients. :star_struck:

12

Patience is a virtue Padwan! In my case “Patients” were a virtue as I worked in a hospital! :slight_smile: