Alternatives to Tailwind CSS logo

Alternatives to Tailwind CSS

Bootstrap, tachyons, Bulma, Material-UI, and Sass are the most popular alternatives and competitors to Tailwind CSS.
767
1.2K
+ 1
171

What is Tailwind CSS and what are its top alternatives?

Tailwind is different from frameworks like Bootstrap, Foundation, or Bulma in that it's not a UI kit. It doesn't have a default theme, and there are no build-in UI components. It comes with a menu of predesigned widgets to build your site with, but doesn't impose design decisions that are difficult to undo.
Tailwind CSS is a tool in the Front-End Frameworks category of a tech stack.
Tailwind CSS is an open source tool with 42.6K GitHub stars and 1.9K GitHub forks. Here鈥檚 a link to Tailwind CSS's open source repository on GitHub

Top Alternatives to Tailwind CSS

  • Bootstrap

    Bootstrap

    Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...

  • tachyons

    tachyons

    Create fast loading, highly readable, and 100% responsive interfaces with as little CSS as possible. ...

  • Bulma

    Bulma

    Bulma is a CSS framework based on Flexbox and built with Sass

  • Material-UI

    Material-UI

    It is a comprehensive guide for visual, motion, and interaction design across platforms and devices. ...

  • Sass

    Sass

    Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin. ...

  • Vuetify

    Vuetify

    Vuetify is a component framework for Vue.js 2. It aims to provide clean, semantic and reusable components that make building your application a breeze. Vuetify utilizes Google's Material Design design pattern, taking cues from other popular frameworks such as Materialize.css, Material Design Lite, Semantic UI and Bootstrap 4. ...

  • styled-components

    styled-components

    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 馃拝 ...

  • BEM

    BEM

    This methodology was developed at Yandex with the goals in mind that Fast development and long-lasting results for standard projects,A project involves many people,Scalable teams,Code reuse. ...

Tailwind CSS alternatives & related posts

Bootstrap logo

Bootstrap

52.2K
11.4K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
52.2K
11.4K
+ 1
7.6K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 943
    Consistent
  • 777
    Great docs
  • 677
    Flexible
  • 466
    HTML, CSS, and JS framework
  • 410
    Open source
  • 375
    Widely used
  • 368
    Customizable
  • 241
    HTML framework
  • 76
    Popular
  • 75
    Mobile first
  • 75
    Easy setup
  • 56
    Great grid system
  • 49
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 27
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 13
    Grids
  • 8
    Clean
  • 7
    Good for a person who hates CSS
  • 4
    Rapid development
  • 4
    Easy to setup and learn
  • 4
    Love it
  • 2
    Clean and quick frontend development
  • 2
    Provide angular wrapper
  • 2
    Great and easy to use
  • 2
    Great and easy
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Community
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 2
    Easy to use
  • 1
    Painless front end development
  • 1
    Responsive design
  • 1
    Reactjs
  • 1
    Geo
  • 1
    Design Agnostic
  • 1
    So clean and simple
  • 1
    Numerous components
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Love the classes?
  • 1
    Material-ui
  • 1
    Pre-Defined components
  • 1
    Boostrap
  • 1
    It's fast
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 0
    Frefsd
CONS OF BOOTSTRAP
  • 25
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 14
    Too much heavy decoration in default look
  • 14
    Grid system break points aren't ideal
  • 8
    Verbose styles

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Module Lead | 18 upvotes 路 2.3M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Francisco Quintero
Tech Lead at Dev As Pros | 13 upvotes 路 694.7K views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
tachyons logo

tachyons

31
67
0
Quickly build and design new UI without writing css
31
67
+ 1
0
PROS OF TACHYONS
    Be the first to leave a pro
    CONS OF TACHYONS
      Be the first to leave a con

      related tachyons posts

      Bulma logo

      Bulma

      536
      648
      33
      Free, open source, & modern CSS framework based on Flexbox
      536
      648
      + 1
      33
      PROS OF BULMA
      • 10
        Easy setup
      • 6
        Easy-to-customize the sass build
      • 6
        Community-created themes
      • 4
        Great docs
      • 4
        Responsive
      • 3
        Easy to learn and use
      CONS OF BULMA
      • 2
        Not yet supporting Vue 3

      related Bulma posts

      Daniel Hern谩ndez Alcojor
      Frontend Developer at atSistemas | 8 upvotes 路 301.3K views

      I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.

      But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.

      What do you think we should use? Maybe you have another suggestion?

      See more
      Material-UI logo

      Material-UI

      1.3K
      2.5K
      338
      React components for faster and easier web development
      1.3K
      2.5K
      + 1
      338
      PROS OF MATERIAL-UI
      • 107
        React
      • 70
        Material Design
      • 45
        Ui components
      • 23
        CSS framework
      • 17
        Component
      • 10
        Looks great
      • 9
        Responsive
      • 9
        LESS
      • 6
        Open source
      • 6
        Good documentation
      • 5
        Code examples
      • 5
        Flexible
      • 5
        Ui component
      • 4
        JSS
      • 3
        Angular
      • 3
        Very accessible
      • 2
        Fun
      • 2
        Designed for Server Side Rendering
      • 2
        Supports old browsers out of the box
      • 2
        LADO
      • 1
        Interface
      • 1
        Asdasd
      • 1
        Easy to work with
      • 0
        555
      CONS OF MATERIAL-UI
      • 24
        Hard to learn. Bad documentation
      • 21
        Hard to customize
      • 16
        Hard to understand Docs
      • 6
        Bad performance
      • 5
        Long Code
      • 4
        Extra library needed for date/time pickers
      • 4
        For editable table component need to use material-table

      related Material-UI posts

      Adebayo Akinlaja
      Engineering Manager at Andela | 22 upvotes 路 627.1K views

      I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen鈥攕ince I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

      A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

      In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

      If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

      See more

      My React website is a simple 5-pager that attaches to a database to store and display registrations and other data. The user (small user base) can change any form elements, but I don't need theme-ing, though that would be fun for the user. reactstrap/react-bootstrap built on Bootstrap 4 sounds dated. I am familiar with reactstrap, but a friend said to try Material-UI. The thought of learning it is interesting, but somehow I think it might be overkill. So... reactstrap, react-bootstrap, or Material UI, which should I use?

      See more
      Sass logo

      Sass

      27.3K
      19.3K
      3K
      Syntactically Awesome Style Sheets
      27.3K
      19.3K
      + 1
      3K
      PROS OF SASS
      • 604
        Variables
      • 587
        Mixins
      • 465
        Nested rules
      • 411
        Maintainable
      • 296
        Functions
      • 148
        Modular flexible code
      • 140
        Open source
      • 111
        Selector inheritance
      • 107
        Dynamic
      • 96
        Better than cs
      • 4
        Used by Bootstrap
      • 2
        If and for function
      • 1
        Custom functions
      • 1
        Better than less
      CONS OF SASS
        Be the first to leave a con

        related Sass posts

        Islam Diab
        Full-stack Developer at Freelancer | 9 upvotes 路 8.2K views

        Hi, I want to start freelancing, I have two years of experience in web development, and my skills in web development: HTML CSS JavaScript [basic, Object-Oriented Programming, Document object model, and browser object model] jQuery Bootstrap 3, 4 Pre-processor -> Sass Template Engine with Pug.js Task Runner with Gulp.js and Webpack Ajax JSON JavaScript Unit testing with jest framework Vue.js

        Node.js [Just basic]

        My Skills in Back end development Php [Basic, and Object-Oriented Programming] Database management system with MySql for database relationships and MongoDB for database non-relationships architecture pattern with MVC concept concept of SOLID Unit testing with PHPUnit Restful API

        Laravel Framework

        and version control with GitHub ultimately, I want to start working as a freelancer full time. Thanks.

        See more

        ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

        ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

        React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

        styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

        React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

        Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

        See more
        Vuetify logo

        Vuetify

        836
        1.4K
        134
        Material Component Framework for VueJS 2
        836
        1.4K
        + 1
        134
        PROS OF VUETIFY
        • 26
          Enables beauty for graphically challenged devs
        • 22
          Wide range of components and active development
        • 18
          Vue
        • 14
          New age components
        • 10
          Easy integration
        • 10
          Material Design
        • 8
          Nuxt.js
        • 8
          Open Source
        • 5
          Not tied to jQuery
        • 3
          Awesome Documentation
        • 3
          Internationalization
        • 3
          Awesome Component collection
        • 2
          Not tied to jQuery
        • 2
          Best use of vue slots you'll ever see
        CONS OF VUETIFY
        • 17
          It is heavy

        related Vuetify posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH | 19 upvotes 路 571.1K views

        Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

        • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
        • Vue Styleguidist as our style guide and pool of developed Vue.js components
        • Vuetify as Material Component Framework (for fast app development)
        • TypeScript as programming language
        • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
        • ESLint, TSLint and Prettier for coding style and code analyzes
        • Jest as testing framework
        • Google Fonts and Font Awesome for typography and icon toolkit
        • NativeScript-Vue for mobile development

        The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

        • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
        • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
        • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
        • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
        • Large scaling. Vue.js can help to develop pretty large reusable templates.
        • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
        See more
        Paul Whittemore
        Developer and Owner at Appurist Software | 15 upvotes 路 662.2K views

        I'm building most projects using: Server: either Fastify (all projects going forward) or ExpressJS on Node.js (existing, previously) on the server side, and Client app: either Vuetify (currently) or Quasar Framework (going forward) on Vue.js with vuex on Electron for the UI to deliver both web-based and desktop applications for multiple platforms.

        The direct support for Android and iOS in Quasar Framework will make it my go-to client UI platform for any new client-side or web work. On the server, I'll probably use Fastly for all my server work, unless I get into Go more in the future.

        Update: The mobile support in Quasar is not a sufficiently compelling reason to move me from Vuetify. I have decided to stick with Vuetify for a UI for Vue, as it is richer in components and enables a really great-looking professional result. For mobile platforms, I will just use Cordova to wrap the Vue+Vuetify app for mobile, and Electron to wrap it for desktop platforms.

        See more
        styled-components logo

        styled-components

        798
        422
        7
        Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
        798
        422
        + 1
        7
        PROS OF STYLED-COMPONENTS
        • 7
          Very easy to use and integrate
        CONS OF STYLED-COMPONENTS
          Be the first to leave a con

          related styled-components posts

          Johnny Bell
          Software Engineer at Weedmaps | 14 upvotes 路 470.1K views

          For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.

          Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.

          We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.

          Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.

          The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.

          If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.

          #StackDecisionsLaunch

          See more

          ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

          ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

          React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

          styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

          React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

          Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

          See more
          BEM logo

          BEM

          89
          70
          0
          It is a methodology, that helps you to achieve reusable components and code sharing in the front-end
          89
          70
          + 1
          0
          PROS OF BEM
            Be the first to leave a pro
            CONS OF BEM
              Be the first to leave a con

              related BEM posts