GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - ember-elements/ember-elements: a UI toolkit in Ember ♾️ storybook link(WIP) https://64f3486d17c24063fe86105d-zslyevuhcj.chromatic.com/

BranchesTags
Open more actions menu

Latest commit

 

History

448 Commits
448 Commits

Folders and files

NameName
Last commit message
Last commit date
.github
.github
 
 
.husky
.husky
 
 
.vscode
.vscode
 
 
packages
packages
 
 
.DS_Store
.DS_Store
 
 
.gitignore
.gitignore
 
 
.sonarcloud.properties
.sonarcloud.properties
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
commitlint.config.js
commitlint.config.js
 
 
lerna.json
lerna.json
 
 
package.json
package.json
 
 
yarn.lock
yarn.lock
 
 

Repository files navigation

Logo

Ember Elements is a UI toolkit built with Typescript and made available as an Ember addon. It is based on the awesome Blueprint design system.

Build Status minified minified + gzip license release

The Whys

Why Ember?

We chose EmberJS framework for the productivity and stability it brings to our projects. With this project, we strive to further reduce the time, effort and resources needed to build a web application.

Why Blueprint?

  1. We just loved the design 😍. Moreover, it has been designed with accessibility in mind.
  2. The project is mature and had been in production use for quite some time.
  3. It is optimized for building complex, data-dense web interfaces for desktop applications. This means, it is not a mobile-first UI toolkit. It reinforces our belief that design system should be contextual.
  4. Known for its quality in the React ecosystem.
  5. Lacked an Ember equivalent.

We strive to attain parity with BlueprintJS in terms of components and quality. We also strive to ensure that there is minimal effort in switching between react and ember elements.

PS: Still confused about the need? Watch Frédéric Soumaré talk @ EmberConf, 2019

Why Typescript?

  1. Well who doesnt love it.
  2. Increased adoption in Ember ecosystem.
  3. Moreover, BlueprintJS(React) is also written in Typescript.

Community

To request a new component, raise a request

For any other enhancements, raise an issue here

To file a bug, report it here

For any other contributions, read CONTRIBUTING.md

Join our Slack group to talk to us


About

a UI toolkit in Ember ♾️ storybook link(WIP) https://64f3486d17c24063fe86105d-zslyevuhcj.chromatic.com/

ember-elements.github.io/ember-elements/

Topics

designdesign-systememberember-addonemberjssasstypescriptuiui-components

Resources

Readme
Apache-2.0 license

Contributing

Contributing
Activity
Custom properties

Stars

55 stars

Watchers

5 watching

Forks

8 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.