Alternatives to Pattern Lab logo

Alternatives to Pattern Lab

Storybook, Bootstrap, Animate.css , Material Design for Angular, and Gatsby are the most popular alternatives and competitors to Pattern Lab.
14
40
+ 1
0

What is Pattern Lab and what are its top alternatives?

It helps you and your team build thoughtful, pattern-driven user interfaces using atomic design principles.
Pattern Lab is a tool in the Static Site Generators category of a tech stack.

Top Alternatives to Pattern Lab

  • Storybook

    Storybook

    It is an open source tool for developing UI components in isolation for React, Vue, and Angular. It makes building stunning UIs organized and efficient. ...

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

  • Gatsby

    Gatsby

    Gatsby lets you build blazing fast sites with your data, whatever the source. Liberate your sites from legacy CMSs and fly into the future. ...

  • Material-UI

    Material-UI

    MUI (formerly Material-UI) is the React UI library you always wanted. Follow your own design system, or start with Material Design. ...

  • Jekyll

    Jekyll

    Think of Jekyll as a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind GitHub Pages, which you can use to host sites right from your GitHub repositories. ...

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

Pattern Lab alternatives & related posts

Storybook logo

Storybook

748
368
0
Build bulletproof UI components faster
748
368
+ 1
0
PROS OF STORYBOOK
    Be the first to leave a pro
    CONS OF STORYBOOK
      Be the first to leave a con

      related Storybook posts

      Robert Zuber

      We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

      See more
      Bootstrap logo

      Bootstrap

      53K
      11.9K
      7.6K
      Simple and flexible HTML, CSS, and JS for popular UI components and interactions
      53K
      11.9K
      + 1
      7.6K
      PROS OF BOOTSTRAP
      • 1.6K
        Responsiveness
      • 1.2K
        UI components
      • 943
        Consistent
      • 778
        Great docs
      • 677
        Flexible
      • 466
        HTML, CSS, and JS framework
      • 411
        Open source
      • 375
        Widely used
      • 368
        Customizable
      • 241
        HTML framework
      • 76
        Popular
      • 76
        Easy setup
      • 75
        Mobile first
      • 56
        Great grid system
      • 50
        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
      • 8
        Clean
      • 7
        Good for a person who hates CSS
      • 4
        Easy to setup and learn
      • 4
        Rapid development
      • 4
        Love it
      • 3
        Great and easy to use
      • 2
        Great and easy
      • 2
        Provide angular wrapper
      • 2
        Community
      • 2
        Powerful grid system, Rapid development, Customization
      • 2
        Popularity
      • 2
        Great customer support
      • 2
        Clean and quick frontend development
      • 2
        Easy to use
      • 2
        Great and easy to make a responsive website
      • 2
        Sprzedam opla
      • 1
        Material-ui
      • 1
        Geo
      • 1
        It's fast
      • 1
        Boostrap
      • 1
        Pre-Defined components
      • 1
        Not tied to jQuery
      • 1
        Responsive design
      • 1
        Design Agnostic
      • 1
        Recognizable
      • 1
        Intuitive
      • 1
        Love the classes?
      • 1
        Reactjs
      • 1
        Felxible, comfortable, user-friendly
      • 1
        The fame
      • 1
        Easy setup2
      • 1
        Painless front end development
      • 1
        So clean and simple
      • 1
        Numerous components
      • 0
        Frefsd
      CONS OF BOOTSTRAP
      • 25
        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 | Module Lead · | 19 upvotes · 2.5M 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 · 790.2K 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

      9.2K
      1.5K
      0
      A library of CSS animations
      9.2K
      1.5K
      + 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

          8.3K
          6.6K
          520
          Material Design for AngularJS Apps
          8.3K
          6.6K
          + 1
          520
          PROS OF MATERIAL DESIGN FOR ANGULAR
          • 119
            Ui components
          • 62
            Backed by google
          • 51
            Backed by angular
          • 51
            Free
          • 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

          Gatsby logo

          Gatsby

          2.5K
          2K
          96
          Free, open source framework for building blazing fast websites and apps with React
          2.5K
          2K
          + 1
          96
          PROS OF GATSBY
          • 21
            Generated websites are super fast
          • 14
            Fast
          • 12
            GraphQL
          • 8
            Progressive Web Apps generation
          • 7
            Easy to connect with lots of CMS via official plugins
          • 7
            Reusable components (React)
          • 6
            Allows to use markdown files as articles
          • 4
            Static-sites
          • 4
            Images
          • 3
            Easy to connect with Drupal via official plugin
          • 3
            All the benefits of a static website + React+GraphQL
          • 3
            List of starters as base for new project
          • 2
            Open source
          • 1
            Gitlab pages integration
          • 1
            Incremental Build
          CONS OF GATSBY
          • 6
            No ssr
          • 3
            Very slow builds
          • 3
            Documentation isn't complete.
          • 2
            Slow builds
          • 2
            Flash of unstyled content issues
          • 2
            For-profit
          • 1
            Too many dependencies
          • 1
            Difficult debugging
          • 1
            Problematic between develop and build commands
          • 1
            Plugin driven development
          • 1
            Difficult maintenance

          related Gatsby posts

          Johnny Bell

          I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

          I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

          I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

          Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

          Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

          With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

          If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

          See more
          Ronan Levesque
          Software engineer at Algolia · | 18 upvotes · 240.9K views

          A few months ago we decided to move our whole static website (www.algolia.com) to a new stack. At the time we were using a website generator called Middleman, written in Ruby. As a team of only front-end developers we didn't feel very comfortable with the language itself, and the time it took to build was not satisfying. We decided to move to Gatsby to take advantage of its use of React , as well as its incredibly high performances in terms of build and page rendering.

          See more
          Material-UI logo

          Material-UI

          1.5K
          2.8K
          373
          The React UI library you always wanted.
          1.5K
          2.8K
          + 1
          373
          PROS OF MATERIAL-UI
          • 115
            React
          • 76
            Material Design
          • 49
            Ui components
          • 25
            CSS framework
          • 20
            Component
          • 12
            Looks great
          • 10
            Responsive
          • 10
            Good documentation
          • 9
            LESS
          • 7
            Open source
          • 6
            Code examples
          • 5
            Ui component
          • 5
            Flexible
          • 4
            JSS
          • 3
            Very accessible
          • 3
            Angular
          • 3
            Supports old browsers out of the box
          • 2
            Designed for Server Side Rendering
          • 2
            Interface
          • 2
            Fun
          • 2
            LADO
          • 1
            Easy to work with
          • 1
            Barev Arman
          • 1
            Asdasd
          • 0
            555
          CONS OF MATERIAL-UI
          • 27
            Hard to learn. Bad documentation
          • 22
            Hard to customize
          • 18
            Hard to understand Docs
          • 6
            Bad performance
          • 5
            Extra library needed for date/time pickers
          • 5
            For editable table component need to use material-table
          • 5
            Long Code

          related Material-UI posts

          Adebayo Akinlaja
          Engineering Manager at Andela · | 26 upvotes · 794.8K 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
          Jekyll logo

          Jekyll

          1.4K
          1.2K
          226
          Blog-aware, static site generator in Ruby
          1.4K
          1.2K
          + 1
          226
          PROS OF JEKYLL
          • 75
            Github pages integration
          • 53
            Open source
          • 37
            It's slick, customisable and hackerish
          • 23
            Easy to deploy
          • 22
            Straightforward cms for the hacker mindset
          • 6
            Gitlab pages integration
          • 4
            Best for blogging
          • 2
            Easy to integrate localization
          • 2
            Low maintenance
          • 1
            Huge plugins ecosystem
          • 1
            Authoring freedom and simplicity
          CONS OF JEKYLL
          • 4
            Build time increases exponentially as site grows
          • 2
            Lack of developments lately
          • 1
            Og doesn't work with postings dynamically

          related Jekyll posts

          Dale Ross
          Independent Contractor at Self Employed · | 22 upvotes · 996K views

          I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.

          I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.

          Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map

          See more
          Josh Dzielak
          Co-Founder & CTO at Orbit · | 5 upvotes · 262.8K views
          Shared insights
          on
          JekyllJekyllHugoHugo

          Earlier this year, I migrated my personal website (dzello.com) from Jekyll to Hugo. My goal with the migration was to make the development environment as pleasant as possible and to make it really easy to add new types of content. For example, I knew I wanted to add a consulting page and some portfolio-style pages to show off talks I had given and projects I had worked on.

          I had heard about how fast Hugo was, so I tried it out with my content after using a simple migration tool. The results were impressive - the startup and rebuild times were in milliseconds, making the process of iterating on content or design less cumbersome. Then I started to see how I could use Hugo to create new page types and was very impressed by the flexibility of the content model. It took me a few days to really understand where content should go with Hugo, but then I felt very confident that I could create many different types of pages - even multiple blogs if I wanted - using a consistent syntax and with full control of the layouts and the URLs.

          After about 6 months, I've been very happy with the results of the migration. The dev environment is light and fast and I feel at ease adding new pages and sections to the site.

          See more
          Nuxt.js logo

          Nuxt.js

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

          related Nuxt.js posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 816.7K 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 · | 8 upvotes · 83.8K 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