search

carbon-design-system / carbon-for-ibm-dotcom

Carbon for IBM.com is based on the Carbon Design System for IBM
https://www.ibm.com/standards/carbon/
Apache License 2.0
269 stars 156 forks source link

IBM.com Library Foundation #209

Closed jeffchew closed 5 years ago

jeffchew commented 5 years ago

vladislav-saling created the following on Mar 25:

User story

This will be the IBM.com Library foundation stories, which includes the architecture we will be creating to support the overall future Dotcom design system.

Acceptance criteria

At a high level, this will be a monorepo that supports multiple packages to be deployed through a private npm repository. In addition, each package should have its own output as a website, serving as living documentation (markdown/jsdocs, pattern lab, etc).

Each package should follow semantic versioning (https://semver.org), and will stand up our own devops pipeline (with environment deployments/npm publishing) as a separate epic.

Tasks will be captured as separate stories under this epic.

Original issue: https://github.ibm.com/webstandards/digital-design/issues/656

jeffchew commented 5 years ago

On Apr 08, vladislav-saling commented: As @james-dow pointed out on slack, we might want to consider following https://next.carbondesignsystem.com/contributing/add-ons#creating-add-ons as our masthead/footer might be viewed at carbon addon in at least one scenario (application adopter usecase). Let's meet and agree we'll start with that.

jeffchew commented 5 years ago

On Apr 15, james-dow commented: We have a meeting later today to discuss the above with Carbon. Hopefully, we'll leave the meeting either with a clear picture on how to set up our add-on, if not an add-on repo itself.

jeffchew commented 5 years ago

On Apr 15, james-dow commented: After our meeting earlier today I polled the team and jump-started the process with Carbon.

See the open issue here. https://github.com/carbon-design-system/issue-tracking/issues/110

jeffchew commented 5 years ago

On Apr 19, james-dow commented: Got a response from Carbon. Since we decided to follow them into IBM, there is an extra step. I'll need to make a request here, and follow the next steps from there.

jeffchew commented 5 years ago

On Apr 22, james-dow commented: This got done over the weekend. I'm going to start creating issues based on next steps.

https://github.com/IBM/carbon-addons-dotcom

jeffchew commented 5 years ago

On Jun 05, Jeff-Chew commented: @hahnrob I'm debating about the use of this epic as a whole. It might make sense to create a v1.0.0 release then tie the epics under there to that and track the release that way. I'm wondering if we can then track which stories are going in which release (v1.1.0, v1.2.0, v2.0.0, etc)