Inspiration/Overview

[danalexilewis]

Atomic Dog is an exploration into a systematic approach and universal language for discovering, designing, developing & deploying software (react) products.

Initially we are focusing between the overlap between design and development. We are using React Storybook with React components co create the User Interface (UI) and User Experience (UX).

Atomic Dog takes its name from a combination of the awesome Atomic Design framework and the popular tools framework dogstack that we created at Root Systems.

As with dogstack we are using Dan Abramov's great Presentational and Container Components to create a clear separation of concerns within our react components.

We will also be using Json Schema to describe the expected data input of a container. This will allow us to fake this data to develop our UI (organisms) elements.

All of this will result in a system that looks something like

SRC:
 - (Functional React) Components
  - Atoms
   - optional collection folder (buttons)
    - atom folder
     - atom.js
     - story.js
  - Molecules
   - molecule folder
    - molecule.js
    - story.js
  - Organisms
   - organism folder
    - organism.js
    - story.js
 - Containers
  - container folder
   - index.js
   - schema.js - Json Schema & Json Schema Faker
 - Templates (series of organisms**)
  - domain folder

** WIP Library

Repos that were looked at to use or for inspiration:

react-atomic-design
Json Schema Faker
react-json-schema-proptypes
react-storybook official example

[michael-smith-nz]

❤️ this @agentlewis . I've been excited to use a design system on a project for a while now.

I'd love to hear what type of projects you think are suited to this model of working and where some of the limitations are?

[danalexilewis]

@NotThatSmith in a nutshell larger products.

If we build up the tooling and documentation for this significantly as well as the capabilities of our pm, designers and devs to work with it on smaller jobs.

The atomic design process is quite systematic and until designers and developers both chose and felt that it was there preferred manner of working AND that they were Effective and Efficient with it I don't see us using it on small projects.

A good existing example of this is TDD - if any one of us got it to the point that it was a skill that we were only exploiting rather than discovering we could use it on client jobs - until than its probably only an option of products where we can value the capability building aspect of it.