Alternatives to windiCSS logo

Alternatives to windiCSS

Bootstrap, Animate.css , Material Design for Angular, Material-UI, and Foundation are the most popular alternatives and competitors to windiCSS.
0
0
+ 1
0

What is windiCSS and what are its top alternatives?

It is a next-generation utility-first CSS framework. If you are already familiar with Tailwind CSS, think about it as an on-demanded alternative to Tailwind, which provides faster load times, fully compatible with Tailwind v2.0 and with a bunch of additional cool features.
windiCSS is a tool in the Front-End Frameworks category of a tech stack.
windiCSS is an open source tool with GitHub stars and GitHub forks. Here’s a link to windiCSS's open source repository on GitHub

Top Alternatives to windiCSS

  • Bootstrap

    Bootstrap

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

  • Animate.css

    Animate.css

    It is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness. ...

  • Material Design for Angular

    Material Design for Angular

    Material Design is a specification for a unified system of visual, motion, and interaction design that adapts across different devices. Our goal is to deliver a lean, lightweight set of AngularJS-native UI elements that implement the material design system for use in Angular SPAs. ...

  • Material-UI

    Material-UI

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

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

  • Nuxt.js

    Nuxt.js

    Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more. ...

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

windiCSS alternatives & related posts

Bootstrap logo

Bootstrap

52K
11.5K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
52K
11.5K
+ 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
  • 411
    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
    Love it
  • 4
    Easy to setup and learn
  • 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
    Easy setup2
  • 1
    Reactjs
  • 1
    Responsive design
  • 1
    Geo
  • 1
    Not tied to jQuery
  • 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
    Painless front end development
  • 1
    It's fast
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 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
  • 1
    Super heavy

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 · 719.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
Animate.css  logo

Animate.css

8.9K
1.2K
0
A library of CSS animations
8.9K
1.2K
+ 1
0
PROS OF ANIMATE.CSS
    Be the first to leave a pro
    CONS OF ANIMATE.CSS
      Be the first to leave a con

      related Animate.css posts

      Material Design for Angular logo

      Material Design for Angular

      7.9K
      6.2K
      517
      Material Design for AngularJS Apps
      7.9K
      6.2K
      + 1
      517
      PROS OF MATERIAL DESIGN FOR ANGULAR
      • 117
        Ui components
      • 62
        Backed by google
      • 51
        Free
      • 50
        Backed by angular
      • 48
        Javascript
      • 34
        Open source
      • 32
        Responsiveness
      • 31
        Easy to learn
      • 28
        Quick to develop
      • 20
        Customizable
      • 8
        Easy to start
      • 8
        Powerful
      • 6
        Themes
      • 6
        Flexible
      • 4
        Flexbox Layouts
      • 3
        Great community
      • 3
        I like its design
      • 2
        Great extensions
      • 1
        CDK
      • 1
        Consistents
      • 1
        It's the best looking out of the box
      • 1
        Seamless integration with AngularJS but lack of docs
      • 0
        Progressive Web Apps - to learn
      CONS OF MATERIAL DESIGN FOR ANGULAR
      • 4
        No practical examples

      related Material Design for Angular posts

      Material-UI logo

      Material-UI

      1.3K
      2.5K
      344
      React components for faster and easier web development
      1.3K
      2.5K
      + 1
      344
      PROS OF MATERIAL-UI
      • 110
        React
      • 72
        Material Design
      • 45
        Ui components
      • 23
        CSS framework
      • 17
        Component
      • 10
        Looks great
      • 9
        LESS
      • 9
        Responsive
      • 6
        Good documentation
      • 6
        Open source
      • 5
        Code examples
      • 5
        Flexible
      • 5
        Ui component
      • 4
        JSS
      • 3
        Very accessible
      • 3
        Angular
      • 2
        Designed for Server Side Rendering
      • 2
        Interface
      • 2
        Supports old browsers out of the box
      • 2
        Fun
      • 2
        LADO
      • 1
        Easy to work with
      • 1
        Asdasd
      • 0
        555
      CONS OF MATERIAL-UI
      • 25
        Hard to learn. Bad documentation
      • 22
        Hard to customize
      • 17
        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 · 657.7K 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

      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
      Foundation logo

      Foundation

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

      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
      Bootstrap
      Foundation

      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
      Nuxt.js logo

      Nuxt.js

      1.2K
      1K
      246
      The Vue.js Framework
      1.2K
      1K
      + 1
      246
      PROS OF NUXT.JS
      • 38
        SSR
      • 34
        Automatic routes
      • 22
        Middleware
      • 20
        Hot code reloading
      • 16
        Easy setup, easy to use, great community, FRENCH TOUCH
      • 16
        Static Websites
      • 16
        SPA
      • 14
        Plugins
      • 12
        Code splitting for every page
      • 11
        Custom layouts
      • 10
        Automatic transpilation and bundling (with webpack and
      • 8
        Modules ecosystem
      • 7
        Easy setup
      • 6
        Vibrant and helpful community
      • 6
        Pages directory
      • 6
        Amazing Developer Experience
      • 3
        Not React
      • 1
        Its Great for Team Development
      CONS OF NUXT.JS
      • 1
        Still vue 2

      related Nuxt.js posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 19 upvotes · 617.4K 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
      Giordanna De Gregoriis
      Jr Fullstack Developer at Stefanini Inspiring · | 7 upvotes · 34.4K 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
      Vuetify logo

      Vuetify

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

      related Vuetify posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 19 upvotes · 617.4K 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 · 681K 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
      Semantic UI logo

      Semantic UI

      821
      1.3K
      671
      A UI Component library implemented using a set of specifications designed around natural language
      821
      1.3K
      + 1
      671
      PROS OF SEMANTIC UI
      • 156
        Easy to use and looks elegant
      • 92
        Variety of components
      • 64
        Themes
      • 61
        Has out-of-the-box widgets i would actually use
      • 56
        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
        UI components
      • 7
        Clean and consistent markup model
      • 6
        Responsiveness
      • 4
        Elegant. clean. readable. maintainable
      • 4
        Because it is semantic :-D
      • 4
        Good-Looking
      • 2
        Great docs
      • 2
        Consistent
      • 2
        Is big and look really great, nothing like this
      • 2
        Modular and scalable
      • 1
        Jquery
      • 1
        Easy to use
      • 1
        Blends with reactjs
      CONS OF SEMANTIC UI
      • 5
        Outdated build tool (gulp 3))
      • 3
        HTML is not semantic (see list component)
      • 2
        Javascript is tied to jquery
      • 2
        Poor accessibility support

      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