Design: CI/CD catalog detailed page - Beta
Problem
Today we rely solely on README.md
to be the interface to be used for the CI/CD catalog, as we would like to collect and display components metadata automatically, we need to come up with a standard design that could be scalable and customizable by our users.
Intended users
Solution
When navigating from the index page to the detail page users will see the readme.md, from there they should be able to see all available components in that repository. For each component we want to generate as much meta-data information as automatically.
The detailed page could consist out of the: A way for the users to view all available component For each component we would need to surface
- Inputs table (or empty page when no input is defined) with:
- Parameter (inputs)
- Description (not planned yet)
- Default value
- Mandatory/option
- type (not planned yet)
- in a single repository we can have multiple components, users should be able to access those components from the detailed page
- The component is from the type of template (single file yml)
- Each component could have inputs
- There could be a component without any inputs
Edited by Dov Hershkovitch