You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As we continue to develop components and work toward supporting external contributions for components, there is discussion as well as docs, which need to be had and created.
Describe the solution you'd like
An addition to our Contributing guide docs called "Contributing Components," where we will have an "in development" warning on top of the page. This will allow us to adopt a docs first development approach to our internal and external creation of Components. The PR associated with this issue will serve as a place for us to continue our discussion and add to the docs. as we progress.
Additional context
The need for this has come out of three related points of discussion.
How do we store and update (non-deployment) information relating to components for both "Enterprise" and "Open Source"?
How will we update and version the components as the Airy APIs continue to change?
How will we, eventually, support third-party contributions for components which are not part of Airy Core?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As we continue to develop components and work toward supporting external contributions for components, there is discussion as well as docs, which need to be had and created.
Describe the solution you'd like
An addition to our Contributing guide docs called "Contributing Components," where we will have an "in development" warning on top of the page. This will allow us to adopt a docs first development approach to our internal and external creation of Components. The PR associated with this issue will serve as a place for us to continue our discussion and add to the docs. as we progress.
Additional context
The need for this has come out of three related points of discussion.
Airy Core
?The text was updated successfully, but these errors were encountered: