All Projects → 24ways → Frontend

24ways / Frontend

Licence: mit
Front-end component library for 24 ways. (2013-2019)

Projects that are alternatives of or similar to Frontend

Fast
The adaptive interface system for modern web experiences.
Stars: ✭ 6,532 (+2355.64%)
Mutual labels:  design-systems, component-library
Ft Origami
The Old Origami Website, do not use
Stars: ✭ 80 (-69.92%)
Mutual labels:  design-systems, component-library
Primitives
An open-source UI component library for building high-quality, accessible design systems and web apps. Maintained by @modulz.
Stars: ✭ 644 (+142.11%)
Mutual labels:  design-systems, component-library
Neumorphic Ui
📚 A library of components based on the concept of neumorphism
Stars: ✭ 82 (-69.17%)
Mutual labels:  design-systems, component-library
Vue Design System
An open source tool for building UI Design Systems with Vue.js
Stars: ✭ 2,077 (+680.83%)
Mutual labels:  design-systems, component-library
fyndiq-ui
Library of reusable web frontend components for Fyndiq
Stars: ✭ 39 (-85.34%)
Mutual labels:  design-systems, component-library
Baseweb
A React Component library implementing the Base design language
Stars: ✭ 7,213 (+2611.65%)
Mutual labels:  design-systems, component-library
Nostyle
Design System
Stars: ✭ 101 (-62.03%)
Mutual labels:  design-systems, component-library
Evergreen
🌲 Evergreen React UI Framework by Segment
Stars: ✭ 11,340 (+4163.16%)
Mutual labels:  design-systems, component-library
design-systems
A list of famous design systems, design languages and guidelines
Stars: ✭ 403 (+51.5%)
Mutual labels:  design-systems, component-library
fast-blazor
Blazor component library for FluentUI. Microsoft's official lightweight wrapper around the FluentUI Web Components for use with .NET 6.0 Blazor applications
Stars: ✭ 928 (+248.87%)
Mutual labels:  design-systems, component-library
nuxt-styleguide
Increase the quality and efficiency of product design and development workflows
Stars: ✭ 15 (-94.36%)
Mutual labels:  component-library
laravel-datatables-fractal
Laravel DataTables Fractal Plugin.
Stars: ✭ 94 (-64.66%)
Mutual labels:  fractal
NIM iOS UIKit
网易云信 iOS UI 组件,提供聊天界面,文本消息,图片消息,语音消息,视频消息,地理位置消息,自定义消息(阅后即焚)等消息示例。#推荐客户得比特币/京东卡,现在推荐使用网易云信,最低得0.02BTC或3000元京东卡/单,点击参与:https://yunxin.163.com/promotion/recommend
Stars: ✭ 1,371 (+415.41%)
Mutual labels:  component-library
carbon-components-vue
⛰️Carvue.js -- Carbon design for VueJS
Stars: ✭ 104 (-60.9%)
Mutual labels:  component-library
comento-ui
Vue UI components used in Comento
Stars: ✭ 25 (-90.6%)
Mutual labels:  component-library
marble
Marble is the design system used by The Metropolitan Museum of Art 🏛
Stars: ✭ 14 (-94.74%)
Mutual labels:  component-library
mayflower
Mayflower Mono Repo (react and pattern lab and documentation)
Stars: ✭ 17 (-93.61%)
Mutual labels:  component-library
clockface
UI Kit for building Chronograf
Stars: ✭ 33 (-87.59%)
Mutual labels:  component-library
foundational-design-system-proto
A prototype for a foundational design system at Shopify
Stars: ✭ 82 (-69.17%)
Mutual labels:  design-systems

Bits, the front-end component library for 24 ways

Requirements

Bits is built upon Fractal, a tool that enables the rapid development of components, templates and pages. Fractal uses a number of ES6 features, so this project requires Node.js v4.0+ to be installed locally. A global install of Gulp is also recommended.

Installation

To get the project up and running, and view components in the browser, complete the following steps:

  1. Download and install Node: https://nodejs.org/
  2. Clone this repo: git clone [email protected]:24ways/frontend.git (SSH) or git clone https://github.com/24ways/frontend.git (HTTPS)
  3. [Optional] Install Gulp globally: npm install gulp -g
  4. [Optional] Install Fractal globally: npm install fractal -g
  5. Install project dependancies: npm install
  6. Start the development environment: npm start
  7. Open your browser and visit http://localhost:3000

Development

When developing components, you may want assets automatically compiled and the browser to refresh automatically. To do this, run the following task:

  • npm run dev

Creating a static build

To create a static instance of this project, run the following task:

  • npm run build

This will create a folder called www, into which the required files will be created.

Deployment

To make this project publicly accessible, you can deploy a static instance by running the following task:

  • npm run publish

This will publish the contents of public to your gh-pages branch.

Repo structure

Sometimes it’s helpful to know what all these different files are for…

/
├─ src/
│  ├─ assets/        # Assets
│  │  ├─ icons/      # Favicon and home screen icons
│  │  ├─ images/     # Raster images (used in component examples)
│  │  ├─ scripts/    # JavaScript files
│  │  ├─ styles/     # CSS files
│  │  └─ vectors/    # SVG images, icons and logos
│  │
│  ├─ components/    # Components
│  │  ├─ _partials/  # …that render component previews
│  │  ├─ common/     # …that may appear anywhere
│  │  ├─ global/     # …that appear on every page
│  │  ├─ layouts/    # …that govern macro layout
│  │  ├─ scopes/     # …that style undecorated markup
│  │  ├─ templates/  # …that combine components to render page types
│  │  └─ utilities/  # …that have a single purpose/role
│  │
│  ├─ docs/          # Documentation
│  │  ├─ _partials/  # Partials for rendering documentation
│  │  └─ …           # Documentation files
│  │
│  └─ tokens/        # Design tokens
│
├─ tmp/              # Files required for dynamic builds (ignored by Git)
├─ www/              # Public build (ignored by Git)
│
├─ .editorconfig     # Code style definitions
├─ .gitignore        # List of files and folders not tracked by Git
├─ .eslintrc         # Linting preferences for JavasScript
├─ fractal.configjs  # Configuration for Fractal
├─ gulpfile.js       # Configuration for Gulp tasks
├─ LICENSE           # License information for this project
├─ package.json      # Project manifest
└─ README.md         # This file
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].