document how to create and publish a demo #415
Labels
kind/documentation
Categorizes issue or PR as related to documentation.
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
needs-triage
Indicates an issue or PR lacks a `triage/...` label and requires one.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/user-experience
Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Problem statement
During our last retrospective, we identified, that we want to enable any one of the team to create and publish feature demos asynchronously. To do so, we need to have a little guidance on how to create a demo session, how to publish it to our YT channel and which meta-information needs to be present.
Acceptance Criteria
core/docs
, maybe on the support website?core/docs
/priority important-soon
/kind feature
/kind documentation
The text was updated successfully, but these errors were encountered: