Skip to content

Specify Pattern Reading Persona(s) #122

Open
@markus-gsf-seidl

Description

@markus-gsf-seidl

Is your feature request related to a problem? Please describe.
When writing patterns I struggle to find the right level of knowledge the average reader will have. I also saw reviews that specify to describe various levels of knowledge I would assume the reader should have.

Describe the solution you'd like
Describe what the reader should know, for example

  • For Cloud the reader should have a basic understanding of AWS/GCP/Azure, a basic understanding of... etc.
  • For Web the reader should have a basic understanding of ...

It would also make sense to describe it somewhere and maybe provide some links/documentation if the reader doesn't fulfill these 'requirements' instead of including them in the patterns at various levels.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions