-
Notifications
You must be signed in to change notification settings - Fork 17
Home
Tiago Rosa edited this page Aug 9, 2019
·
13 revisions
The expected outcome: To have 2 pilot-teams (one LMF one ADEO) being able to install and use, as a POC
, the Design System.
the goal here is not to have a bulletproof cross browser testing or even very stable elements,
but more to be able to test our assumptions about:
how things will be consumed by BUssyntax, modularity and architectural choicesthings are able to play well with various technical stacksthings play well with existing CSS code base
we want to be able to test :
our contributing guidelines and docscss guidelinesCI and CDissue and PR management
we want to be able to test that :
the project is easy to installthe doc is clear and thoroughit seamlessly integrate into your workflowthe linters are well configuredyou can apply some configuration
we want to be able to test that :
the information is well structuredyou can find code, assets and how to easilyit is easy for design system developers to implement
/!\ at this point, the design system is still considered as highly unstable !
The expected outcome: 2 pilot-teams being able to optimize their cycle-time, design and front end development, by leveraging components straight from the design system
testing and improving all the previous pointsredefining new objectivesadding the base list of componentsmake the styleguide looking greatrely heavily on international collaboration to test, review, implement the design system with uscross browser testing
The expected outcome: World-wide teams being use to optimize their time by leveraging this first stable version
the V1 should be the first stable system.
- testing and improving all the previous points
- locking as many point as we can regarding syntaxe, workflow, components etc…
- redefining new objectives