Alternatives to Bulma logo

Alternatives to Bulma

Bootstrap, Material Design, Material, UIkIt, and Vuetify are the most popular alternatives and competitors to Bulma.
750
855
+ 1
38

What is Bulma and what are its top alternatives?

Bulma is a popular open-source CSS framework that is based on Flexbox. It offers a clean and modular design to quickly build responsive websites. Key features include a grid system, versatile components, and a mobile-first approach. However, some limitations of Bulma include limited browser support, lack of customization options, and a relatively smaller community compared to other CSS frameworks.

  1. Bootstrap: Bootstrap is one of the most widely used CSS frameworks that provides a robust grid system, extensive components, and responsive designs. Pros include great documentation and a large community, while cons include a larger file size compared to Bulma.
  2. Tailwind CSS: Tailwind CSS is a utility-first CSS framework that allows for rapid UI development with pre-built utility classes. Key features include customizable designs and reduced reliance on custom CSS, but some may find the learning curve steep compared to Bulma.
  3. Foundation: Foundation is a responsive front-end framework that offers a grid system, templates, and components for building websites. Pros include a modular codebase and customization options, while cons include a potentially steeper learning curve for beginners.
  4. Materialize: Materialize is a modern responsive CSS framework based on Google's Material Design. It offers components, animations, and a grid system. Pros include a user-friendly design language, while cons may include a larger file size compared to Bulma.
  5. Semantic UI: Semantic UI is a responsive front-end framework that uses human-friendly HTML for faster development. Key features include theming capabilities and a variety of UI components. Pros include a sleek design language, but cons may include a more complex syntax compared to Bulma.
  6. UIKit: UIKit is a lightweight and modular front-end framework that offers a variety of components, animations, and responsive designs. Pros include a customizable and modular structure, while cons may include a smaller community compared to Bulma.
  7. Spectre.css: Spectre.css is a lightweight and responsive CSS framework that focuses on modern and simple designs. Key features include a flexbox grid system and versatile components. Pros include minimalistic design aesthetics, while cons may include a potentially limited range of components compared to Bulma.
  8. Chota: Chota is a lightweight and responsive CSS framework that offers a minimalistic design language and a small file size. Pros include simplicity and fast load times, but cons may include a potentially smaller feature set compared to Bulma.
  9. Milligram: Milligram is a minimalist CSS framework with a small file size that focuses on providing a clean and simple design. Pros include lightweight and minimalistic design, while cons may include a potentially limited range of components compared to Bulma.
  10. Bloomer: Bloomer is a flexible and lightweight CSS framework based on Bulma that offers additional utilities and components. Pros include compatibility with Bulma, while cons may include a smaller community and potentially fewer updates compared to the original Bulma framework.

Top Alternatives to Bulma

  • Bootstrap
    Bootstrap

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

  • Material Design
    Material Design

    Material Design is a unified system that combines theory, resources, and tools for crafting digital experiences. ...

  • Material
    Material

    Express your creativity with Material, an animation and graphics framework for Google's Material Design and Apple's Flat UI in Swift. ...

  • UIkIt
    UIkIt

    UIkit gives you a comprehensive collection of HTML, CSS, and JS components which is simple to use, easy to customize and extendable. ...

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

  • Semantic UI
    Semantic UI

    Semantic empowers designers and developers by creating a shared vocabulary for UI. ...

  • Material-UI
    Material-UI

    Material UI is a library of React UI components that implements Google's Material Design. ...

  • Foundation
    Foundation

    Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices. ...

Bulma alternatives & related posts

Bootstrap logo

Bootstrap

55.3K
13.1K
7.7K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
55.3K
13.1K
+ 1
7.7K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 943
    Consistent
  • 779
    Great docs
  • 677
    Flexible
  • 472
    HTML, CSS, and JS framework
  • 411
    Open source
  • 375
    Widely used
  • 368
    Customizable
  • 242
    HTML framework
  • 77
    Mobile first
  • 77
    Popular
  • 77
    Easy setup
  • 57
    Great grid system
  • 52
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 28
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 14
    Grids
  • 9
    Good for a person who hates CSS
  • 8
    Clean
  • 4
    Easy to setup and learn
  • 4
    Rapid development
  • 4
    Love it
  • 3
    Great and easy to use
  • 2
    Easy to use
  • 2
    Devin schumacher rules
  • 2
    Boostrap
  • 2
    Community
  • 2
    Provide angular wrapper
  • 2
    Great and easy
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Clean and quick frontend development
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 1
    Painless front end development
  • 1
    Love the classes?
  • 1
    Responsive design
  • 1
    Poop
  • 1
    So clean and simple
  • 1
    Design Agnostic
  • 1
    Numerous components
  • 1
    Material-ui
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Vue
  • 1
    Felxible, comfortable, user-friendly
  • 1
    Pre-Defined components
  • 1
    It's fast
  • 1
    Geo
  • 1
    Not tied to jQuery
  • 1
    The fame
  • 1
    Easy setup2
CONS OF BOOTSTRAP
  • 26
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 15
    Grid system break points aren't ideal
  • 14
    Too much heavy decoration in default look
  • 8
    Verbose styles
  • 1
    Super heavy

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Technical Lead · | 19 upvotes · 4.7M 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 · 1.6M 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
Material Design logo

Material Design

595
885
14
Google's Material Design
595
885
+ 1
14
PROS OF MATERIAL DESIGN
  • 5
    They really set a new bar in design
  • 4
    An intuitive design
  • 3
    Simply, And Beautiful
  • 2
    Many great libraries
  • 0
    Composants
CONS OF MATERIAL DESIGN
  • 2
    Sometimes, it can hang the browser

related Material Design posts

Giordanna De Gregoriis
Jr Fullstack Developer at Stefanini Inspiring · | 8 upvotes · 458.5K views

TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.

We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.

  • The cold start takes too much time
  • Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
  • Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)

I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.

I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.

What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

See more
Ashish Sharma
Sr. UI Associate at Daffodil Software · | 5 upvotes · 690K views

I am a bit confused when to choose Bootstrap vs Material Design or Tailwind CSS, and why? I mean, in which kind of projects we can work with bootstrap/Material/Tailwind CSS? If the design is made up on the grid, we prefer bootstrap, and if flat design, then material design. Similarly, when do we choose tailwind CSS?

Any suggestion would be appreciated?

See more
Material logo

Material

93
87
3
A Graphics Framework for Material Design in Swift
93
87
+ 1
3
PROS OF MATERIAL
  • 1
    Good Documentation
  • 1
    Samples included
  • 1
    IOS benefits
CONS OF MATERIAL
    Be the first to leave a con

    related Material posts

    UIkIt logo

    UIkIt

    787
    414
    262
    A lightweight and modular front-end framework for developing fast and powerful web interfaces
    787
    414
    + 1
    262
    PROS OF UIKIT
    • 39
      Complete GUI
    • 29
      Easy modify
    • 27
      Practical
    • 24
      Easy to learn
    • 24
      Functional
    • 22
      Intuitive
    • 21
      Free
    • 16
      Simple
    • 15
      Lightweight
    • 15
      Easy to use
    • 5
      Modular
    • 5
      Because I can create amazing things with little effort
    • 5
      Modern look
    • 4
      Responsiveness
    • 3
      Small but Active Community
    • 2
      Convenient JS Components
    • 2
      Based on Flexbox
    • 2
      No requires jquery
    • 2
      Responsive grid
    CONS OF UIKIT
      Be the first to leave a con

      related UIkIt posts

      Daniel Hernández Alcojor
      Frontend Developer at atSistemas · | 8 upvotes · 1M 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
      Vuetify logo

      Vuetify

      1.2K
      1.8K
      170
      Material Component Framework for VueJS 2
      1.2K
      1.8K
      + 1
      170
      PROS OF VUETIFY
      • 29
        Enables beauty for graphically challenged devs
      • 24
        Wide range of components and active development
      • 22
        Vue
      • 18
        New age components
      • 13
        Easy integration
      • 11
        Material Design
      • 10
        Nuxt.js
      • 10
        Open Source
      • 6
        Awesome Documentation
      • 5
        Awesome Component collection
      • 5
        Internationalization
      • 5
        Not tied to jQuery
      • 4
        Best use of vue slots you'll ever see
      • 2
        Not tied to jQuery
      • 2
        Treeshaking
      • 2
        Active Community
      • 2
        Responsiveness
      CONS OF VUETIFY
      • 19
        It is heavy
      • 3
        Not Vue 3 Ready (Alpha-Version)

      related Vuetify posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 4.8M 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
      Jeyabalaji Subramanian

      At FundsCorner, when we set out to pick up the front-end tech stack (around Dec 2017), we drove our decision based on the following considerations:

      (1) We were clear that we will NOT have a hybrid app. We will start with Responsive Web & once there is traction, we will rollout our Android App. However, we wanted to ensure that the users have a consistent experience on both the Web & the App. So, the front-end framework must also have a material design component library which we can choose from.

      (2) Before joining FundsCorner as a CTO, I had already worked with Angular. I enjoyed working with Angular, but I felt that I must choose something that will provide us with the fastest time from Concept to Reality.

      (3) I am strong proponent of segregating HTML & JavaScript. I.e. I was not for writing or generating HTML through JavaScript. Because, this will mean that the Front-end developers I have to hire will always be very strong on JavaScript alongside HTML5 & CSS. I was looking for a Framework that was on JavaScript but not HEAVY on JavaScript.

      (3) The first iteration of the web app was to be done by myself. But I was clear that when someone takes up the mantle, they will be able to come up the curve fast.

      In the end, Vue.js and Vuetify satisfied all the above criteria with aplomb! When I did our first POC on Vue.js I could not believe that front-end development could be this fast. The documentation was par excellence and all the required essentials that come along with the Framework (viz. Routing, Store, Validations) etc. were available from the same community! It was also a breeze to integrate with other JavaScript libraries (such as Amazon Cognito).

      By picking Vuetify, we were able to provide a consistent UI experience between our Web App and Native App, besides making the UI development ultra blazing fast!

      In the end, we were able to rollout our Web App in record 6 weeks (that included the end to end Loan Origination flow, Loans management system & Customer engagement module). www.jeyabalaji.com

      See more
      Semantic UI logo

      Semantic UI

      952
      1.5K
      673
      A UI Component library implemented using a set of specifications designed around natural language
      952
      1.5K
      + 1
      673
      PROS OF SEMANTIC UI
      • 157
        Easy to use and looks elegant
      • 92
        Variety of components
      • 64
        Themes
      • 61
        Has out-of-the-box widgets i would actually use
      • 57
        Semantic, duh
      • 44
        Its the future
      • 42
        Open source
      • 37
        Very active development
      • 31
        Far less complicated structure
      • 28
        Gulp
      • 9
        Already has more features than bootstrap
      • 8
        Just compare it to Bootstrap and you'll be hooked
      • 7
        Clean and consistent markup model
      • 7
        UI components
      • 6
        Responsiveness
      • 4
        Because it is semantic :-D
      • 4
        Elegant. clean. readable. maintainable
      • 4
        Good-Looking
      • 2
        Is big and look really great, nothing like this
      • 2
        Consistent
      • 2
        Great docs
      • 2
        Modular and scalable
      • 1
        Easy to use
      • 1
        Blends with reactjs
      • 1
        Jquery
      CONS OF SEMANTIC UI
      • 5
        Outdated build tool (gulp 3))
      • 3
        Poor accessibility support
      • 3
        HTML is not semantic (see list component)
      • 2
        Javascript is tied to jquery

      related Semantic UI posts

      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
      Hassan Mugabo
      Software Developer at Codeparl Digital Services · | 3 upvotes · 70.1K views

      Hi, I'm using Tailwind CSS for my project but I found Bootstrap and Semantic UI offering pre-built components like Model, Sidebars, and so forth. Is it possible to use Semantic UI or Bootstrap under Tailwind CSS?

      See more
      Material-UI logo

      Material-UI

      2.2K
      3.6K
      441
      Material UI is a library of React UI components that implements Google's Material Design.
      2.2K
      3.6K
      + 1
      441
      PROS OF MATERIAL-UI
      • 141
        React
      • 82
        Material Design
      • 60
        Ui components
      • 30
        CSS framework
      • 25
        Component
      • 14
        Looks great
      • 12
        Responsive
      • 12
        Good documentation
      • 9
        LESS
      • 8
        Ui component
      • 7
        Open source
      • 6
        Code examples
      • 6
        Flexible
      • 5
        JSS
      • 3
        Angular
      • 3
        Very accessible
      • 3
        Fun
      • 3
        Supports old browsers out of the box
      • 2
        Typescript support
      • 2
        # of components
      • 2
        Interface
      • 2
        Designed for Server Side Rendering
      • 1
        Support for multiple styling systems
      • 1
        Css
      • 1
        Easy to work with
      • 1
        Accessibility
      CONS OF MATERIAL-UI
      • 35
        Hard to learn. Bad documentation
      • 28
        Hard to customize
      • 21
        Hard to understand Docs
      • 8
        Bad performance
      • 7
        Extra library needed for date/time pickers
      • 7
        For editable table component need to use material-table
      • 2
        Typescript Support
      • 1
        # of components

      related Material-UI posts

      Adebayo Akinlaja
      Engineering Manager at Andela · | 30 upvotes · 3.3M 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—since 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

      I just finished tweaking styles details of my hobby project MovieGeeks (https://moviegeeks.co/): The minimalist Online Movie Catalog

      This time I want to share my thoughts on the Tech-Stack I decided to use on the Frontend: React, React Router, Material-UI and React-Apollo:

      1. React is by far the Front-End "framework" with the biggest community. Some of the newest features like Suspense and Hooks makes it even more awesome and gives you even more power to write clean UI's

      2. Material UI is a very solid and stable set of react components that not only look good, but also are easy to use and customize. This was my first time using this library and I am very happy with the result

      3. React-Apollo in my opinion is the best GraphQL client for a React application. Easy to use and understand and it gives you awesome features out of the box like cache. With libraries like react-apollo-hooks you can even use it with the hooks api which makes the code cleaner and easier to follow.

      Any feedback is much appreciated :)

      See more
      Foundation logo

      Foundation

      1.2K
      1.2K
      740
      The most advanced responsive front-end framework in the world
      1.2K
      1.2K
      + 1
      740
      PROS OF FOUNDATION
      • 160
        Responsive grid
      • 93
        Mobile first
      • 80
        Open source
      • 75
        Semantic
      • 72
        Customizable
      • 52
        Quick to prototype
      • 50
        Simple ui
      • 45
        Fast
      • 44
        Best practices
      • 39
        Easy setup
      • 6
        Neutral style
      • 6
        HTML, SCSS and JS
      • 5
        Accessibility support
      • 5
        Professional
      • 3
        Xy grid
      • 2
        Sass
      • 2
        Every new version is smaller, smarter & more efficient
      • 1
        Robust
      CONS OF FOUNDATION
      • 5
        Requires jQuery
      • 4
        Awful site

      related Foundation posts

      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
      Shared insights
      on
      BootstrapBootstrapFoundationFoundation

      Should I go with Foundation CSS instead of Bootstrap? Or, if any other popular responsive frameworks are out there, please suggest them to me. My site mainly targets mobile or tablet

      See more