sebworks/atomiccomponent

Framework for building Atomic Components

atomiccomponent's Issues

CF integration

@sebworks I'm thinking we should keep this repo separate from CF. It's exceptionally well abstracted and stands fine on its own. CF can just inherit from it. I imagine you had this in mind when you wrote it. I propose we:

1. Move this repo to cfpb/atomic-component.
2. Publish it to npm as atomic-component.
3. Have CF organisms, molecules and atoms inherit from atomic-component.

For example, the code in table.js would be moved into cf-tables.js and instead of importing

var closest = require( '../../utilities/dom-closest' ).closest;
var config = require( '../../utilities/config' );
var Organism = require( './Organism' );

at the top of the file, it'd be

var closest = require( 'atomic-component/utils/dom-closest' ).closest;
var config = require( 'atomic-component/utils/config' );
var Organism = require( 'atomic-component/organism' );

Here's the complete example. I updated my cf sandbox to use it:

git clone [email protected]:contolini/capital-framework-sandbox.git
cd capital-framework-sandbox
npm i && npm start

Open http://localhost:3000/components/cf-tables/ and the table at the bottom should properly sort.

Let's chat later today!

cc @KimberlyMunoz @jimmynotjim @virginiacc @mistergone @cfarm