momentum-design / momentum-design Goto Github PK
View Code? Open in Web Editor NEWMono Repo for Momentum Design
Home Page: https://momentum-design.github.io/momentum-design/
License: MIT License
Mono Repo for Momentum Design
Home Page: https://momentum-design.github.io/momentum-design/
License: MIT License
As a Multi-Platform Applications Developer, I'd like to have a single source-of-truth for animations I can depend on.
Fonts currently exist within the @momentum-ui/animations package. Migrate these animations into this project as a new package: @momentum-design/animations
.
@momentum-design/animations
packageAfter the main branch has been merged to and the CD deployment script has run, we need to update the design-token-updates branch to have all the changes from main, to mitigate any future merge conflicts, and to keep it up to date for designers. The scope of this ticket is to
As an Internal Webex Developer, I'd like to have the newly automated tokens present within my existing project.
In order to alleviate adoption cost for one of our MVP stakeholders, our team should implement the consumption of the new automated tokens available within this project into the associated Material Design theme.
As a Multi-Platform Applications Developer, I'd like to have a single source-of-truth for illustrations I can depend on.
Illustrations currently exist within the @momentum-ui/illustrations package. Migrate these illustrations into this project as a new package: @momentum-design/illustrations
.
@momentum-design/illustrations
packageAs a Multi-Platform Applications Developer, I'd like to have a single source-of-truth for fonts I can depend on.
Fonts currently exist within the @momentum-ui/fonts package. Migrate these fonts into this project as a new package: @momentum-design/fonts
. Note that the font assets themselves may be abstracted within the @momentum-design/tokens
package.
@momentum-design/fonts
packageIn order to allow for easier automation via CD, dependency tree iteration should be implemented on the core project's package.json
file. This can be inclusive of additional scripts available in the ./scripts
folder if necessary. This will be used to determine if changes impact a specific package, and run automation accordingly.
cd:test
- Runs tests on impacted packagescd:analyze
- Runs static-analysis on impacted packagescd:build
- Builds impacted packagescd:deploy
- Deploys changed packages. Note: This should not deploy as a part of this scopeAs a Multi-Platform Applications Developer, I'd like to have a single source-of-truth for icons I can depend on.
Icons currently exist within the @momentum-ui/icons package. Migrate these icons into this project as a new package: @momentum-design/icons
.
@momentum-design/icons
packageWe need a doc site for the entire folder
Define the features
This ticket needs to be broken up
Scope of ticket
re: component and theme tokens format
As a Contributor and Consumer of this project, I'd like to have API documentation available in the form of JSON abstracted from inline documentation within the source files.
Implement a flow to convert from inline TSDoc to JSON metadata to be consumed locally. This will likely include using the following packages:
./docs/metadata
folder for each packageAs a Multi-Platform Applications Developer, I'd like a way to consume a designer's style definitions as css
, scss
, xml
, json
, and swift-classes
.
Generate a new package within this project titled @momentum-design/tokens
that is used to generate various, platform-specific, formats for consumption.
css/variables
scss/variables
android/colors
ios-swift/swift.class
web/json
As a developer, I'd like to consume the newly automated theme tokens from within the legacy tokens project.
Generate theme token transforms that convert the new theme token format provided by the newly automated tokens into the legacy theme token format available in @momentum-ui/tokens.
As a designer, i'd like to have 5 more illustrations
We need to add 5 more illustrations
In order to validate that the @momentum-design/token-builder
package can properly process input tokens, with a provided configuration, into output tokens. Generate a testing suite that can be used to accomplish this within one or more of the following flows:
This should use template/fixture data to accomplish the resolve.
At this time, there is not an easy way for the team to manage the current roadmap and engineer progress within the Momentum Design project. Using GitHub Projects, outline the roadmap as well as engineer flows needed to complete tasks within this project.
Momentum Design
In order to provide a truly modular option for other token generation flows without coupling the flow to the tokens themselves, an abstracted layer is needed. Implement the abstracted layer and separate all logic from the existing @momentum-design/tokens
package into the following packages:
@momentum-design/tokens
- input/output resources only for design tokens@momentum-design/token-builder
- Logical flows for translating input tokens into output tokensAs a developer, I'd like to consume the newly automated core tokens from within the legacy tokens project.
Generate core token transforms that convert the new format provided by the newly automated core tokens into the legacy format available in @momentum-ui/tokens.
We need to be able to measure the usage of momentum design and track the broadness of scope it touches. Generally we also need to be able to have an on demand calculation of how much time it saves === money vs what we have today. These numbers can be rough. Both of these should be published as continuously updating markdown documents
This project will require testing for pull requests on the various packages that reside within it. Implement a GitHub actions configuration that allows for pull request validation.
In order to properly release each package in a fully independent way, unique version control requirements must be met:
Note that this should not perform a MAJOR version bump unless its specifically triggered.
As a Multi-Platform Applications Developer I'd like to have the theme tokens available via my existing workflow fully automated.
Within the @momentum-ui/tokens project, create additional transforms to convert the momentum-abstract project theme tokens to convert them via the script tooling into the staged format.
As a Developer on this Project's Team and a Designer on this Project's Team, I'd like to have a place in which we can store all of our general decisions and workflows associated with this project.
Create a folder on the root of this project that can be used to store important executive decisions made by our team. This folder should include all items, including logistics and interaction documents, associated with this team until a better solution is generated.
./scratch
folder in the root of this project, along with its internal structure
README.md
file defining the details of the ./scratch
folder within the ./scratch
folder./engineering
folder. Note: this includes all engineer items and can be flexible on its internal structure./designing
folder. Note: this includes all design items and can be flexible on its internal structure./product
folder. Note: this includes all global product items and can be flexible on its internal structureAs a React Applications Developer and consumer of @momentum-ui/react-collaboration, I'd like to have the newly automated tokens available for consumption within this project.
In order to begin adopting the new tokens into MVP projects, our team should make changes to the @momentum-ui/react-collaboration project to consume the newly automated tokens.
css/scss
files to consume the new style tokens.In order to further improve the flexibility of token abstraction, and allow for additional changes per format, expand upon the existing token builder to allow for formats to be more than just an Array of strings.
options
and name
.In order to determine what components are inclusive of this, and how they should be implemented, an investigation needs to occur. This should exist within this project's documentation.
Add documentation to the @momentum-design/tokens
package, inclusive of core documentation along with TSDoc documentation.
./docs/metadata
folder of the @momentum-design/tokens
packageREADME.md
CONTRIBUTING.md
SCRIPTS.md
We need to automate a change log and release notes upon every release that will be published to the documentation site, to NPM when the versions get bumped, and to the repository
These should output markdown files
In order to determine if Harbor Elements
is a potential fit for our upstream @momentum-design/components
package, a thorough investigation must be completed.
./scratch/engineering
folderIn order to begin generating automation tooling, the mono-repo workflows should be configured to support it. Implement multiple flows within this project that allow for dynamic/intelligent CI/CD triggers that only run on necessary items within this project.
./README.md
- Package introductory documentation with template./CONTRIBUTING.md
- Package contribution documentation with template./SCRIPTS.md
- Package scripts documentation with templatebuild
- Should run all sub-scripts for generating a fully qualified distributabletest
- Should run all sub-scripts for testing an associated packageanalyze
- Should run all static-analysis sub-scripts needed to validate the changes meet style requirementsIn order to allow for other products to have a clean path to build their associated tokens into a streamlined interface, abstract the logic from @momentum-design/tokens
into its own @momentum-design/token-builder
package, and make it fully CLI/API accessible.
In order to allow for CLI runs of token-build tooling, add token build flows to the new @momentum-design/token-builder
package. This should allow for the following params to be provided in order to properly build consumable tokens:
config
- the configuration fileinput
- the input tokens directoryoutput
- the output tokens directoryIn order to determine what components are inclusive of this, and how they should be implemented, an investigation needs to occur. This should exist within this project's documentation.
Set up automation flows within GitHub Actions that will automatically analyze/test/deploy the @momentum-design/tokens
project to NPM.
As a Developer looking to consume this project. I'd like to have clear documentation indicating how to consume the project, contribute to the project, and run the scripts associated with the project.
The creation of all core documentation items for this project should be completed.
./README.md
file, inclusive of common core elements
CONTRIBUTING.md
./CONTRIBUTING.md
file, inclusive of common contributing elements
CONTRIBUTING.md
filesSCRIPTS.md
./SCRIPTS.md
file, inclusive of root ./package.json
scripts.A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.