Add an ember-basscss wrapper?

[johno]

Again, thanks for an awesome project, @jxnblk.

I've noticed that recently you've begun wrapping basscss for other frameworks (ng, handlebars). I'm curious if there's interest in an Ember wrapper, namely one that integrates with the ember-cli.

Thanks to the modularity of this project it'd be possible to add each as a single module to an Ember project:

• ember-basscss-buttons
• ember-basscss-typography
• ember-basscss-forms
• etc.

Only requiring ember install:addon ember-basscss-buttons to inject basscss components and CSS into the app. With an all-encompassing ember install:addon ember-basscss which basically introduces dependencies for all the other modules.

I'd be happy to create all the wrappers for integrating basscss CSS and components (as a whole and as separate modules) into ember-cli projects. However, I don't know if you'd like those to be under your own repo umbrella, @jxnblk, or if I should just start creating them under mine. Thoughts?

[jxnblk]

I've only dabbled with Ember a little bit, so correct me if I misunderstand anything.

Generally, love this idea, and if you want to be the owner for these, feel free to do so. From my side of things, I would like to provide modularized UI components for different libraries that rely on their web-component-like aspects. It also seems like not too much work to provide options for simpler templating engines like Rails ERB and Handlebars, but those components would essentially just be helpers.

Ideally, it would be nice to have library-agnostic HTML templates for each component that could be versioned and converted to their relevant library-specific syntax – that's why I started digging into Handlebars, and am definitely interested in Ember's fast boot HTMLbars work. That said something like lodash templates is also something I want to look into for creating source templates.

Angular directives are probably first on my list, because of my familiarity and the popularity of the library. Polymer is also on the radar because of the similarities to spec-based web components. And, of course, React because of its component-based approach.

I think it'd be rad if you wanted to create an ember-basscss repo, and I could definitely link to it from this site. I'm currently pulling in README files for all the modules docs and plan on using the same approach for the handlebars-basscss repo, once its in better shape, with a larger section of the docs for Components. I don't know much about the ember-cli side of things, but it seems like a good idea.

[johno]

Similarly to React/Angular/Polymer, Ember has support for web components that are attempting to adhere to the W3C as closely as possible [documentation]. The latest iterations are beginning to make these component first class citizens within the framework (an approach adopted from React). So, this would fit in nicely with your intentions. I definitely agree with you wholeheartedly, modularized UI components are the way to go, especially if they're library/framework agnostic.

I'd be happy to take ownership of the ember-basscss lib. Though, I'm first going to do a bit of digging and see if there's a method to expose web components to a wide array of front end frameworks, as that'd be ideal to attempting to manage multiple "wrappers" of Basscss. If something like Polymer is the lowest common denominator to create modular components to share among apps built in multiple frameworks (Ember/React/Ng/etc), perhaps that's the way to go. Whether that's achievable at this point, I have no idea. But, I'll do some digging and see.

Thanks for your time.

[johno]

After a bit of digging, it appears that Ember 2.0 will support Polymer components (with intentions of supporting the full W3C spec in the future). So, it appears, at least for the Ember case, Polymer components is the place to start.

As such, I will close this issue and open a new one regarding Polymer components.