This page used to provide an inventory of assets created and maintained by the Product and Solution Marketing team. We have since updated the inventory so it includes all assets and it can now be found within Marketing Strategy & Performance
We have kept the following info specific to the Product and Solution Marketing team as it may assist them in determining how to enter into the Marketing inventory.
The inventory files provide a standardized way to capture, find, and reference created assets (inventory) which can be used by everyone. The data is kept in the yml files in the /data/inventory/ directory. There is one file per team to make ownership clear and make management easier.
inventory folder lives under
/data of the website and is organized in the following manner to enable scaling to multiple groups. The thought is that each group can be CODEOWNERS for their own team inventory, but it should still be easy to search through the inventory of "everything" to find what you are looking for.
/data/inventory | ---- learn.yml (Technical Marketing - will change to team name in another MR) | ---- pmm.yml (Product Marketing) | ---- ... | ---- team_name.yml (Team Name)
The search through the inventory of "everything" to find what you are looking for it is important that all team files use the same format and data fields. This file represents the SSoT for what that format and fields are. If you are making changes make them here first, then make sure everything else follows.
Accepted field descriptions are (fields in bold are required):
- title*: (the display name of the asset) author*: (the author of the asset) team*: (the name of the team that created the asset) asset_type*: (currently one entry only. Expect this to grow as teams are added. asset type = video, demo) date_published*: (month and year content first published. In iso-date format. eg 2020-05) last_changed (date the asset was last changed) gitlab_release: (major.minor GitLab release # the asset is built about/on. eg 12.10) use_case*: (use case the asset focuses on. [Derived from customer use case page](/handbook/use-cases/). Acceptable values are: ) - vcc - ci - cd - devsecops - agile - simplify_devops - cloud_native - gitops - remote - other stage: (multi-select list of stages the asset focuses on. Values should match main entries in [stages.yml](/data/stages.yml)) category: (multi-select list of categories the asset focuses on. Values should match main entries in [categories.yml](/data/categories.yml)) link*: (link to the ungated asset) embedded_link: (link to embeddable version of asset - typically for videos and demos) gated_link: (link to the gated asset) short_description: (a short description of what the asset is about) learn: (values: true or false or blank. Does this asset show up on [email protected]. tech marketing team to add this only please)
If you have questions or need help please open an SM support request.