Open mmitoraj opened 1 month ago
We may take this also as an opportunity to clearly defining our target groups. E.g., user: the end user of a Kyma runtime; contributor: developer or SRE (may be SAP internal or external). We also noted this here: https://github.com/kyma-project/lifecycle-manager/issues/1447
As part of this refactoring and addressing new personas, we may consider to get rid of docs which seem to be obsolete anyway, i.e.:
Description
Lifecycle Manager, in general, is not an end-user-facing project. Most of the documents are relevant only to those who contribute to the project; however, some documents are directed to its users.
To have a clear division of the roles we could split the
/docs
folder into/docs/user
and/docs/contributor
.We had a case when the SRE team could not understand why the spec of a Kyma CR was different in the KCP and SKR. These were very technical details that were not explained in the
Kyma CR
documentation as they are not important to the users of Lifecycle Manager. However, the/docs/contributor
folder could be the right location for that kind of information.Also, looking at the folder structure of other
kyma-project
repositories developed by other Kyma teams, especially modules, the split into/docs/user
and /docs/contributor
is the template convention accepted and widely used by most of them.TBD: The open question is how to categorize individual documents and define their final location (user vs. contributor).
Reasons
More transparent project documentation.
Assignees
@kyma-project/technical-writers @kyma-project/jellyfish
Attachments