[Tracking] Information strategy for Keptn Docs

[mowies]

Goal

Come up with and implement a strategy to structure information in the Keptn Docs better and more easily digestible.

Details

Do some initial user interviews to find out the biggest pain points in our docs and what are easy quick wins, that can be implemented right away. After that, do some more interviews to see how the quick wins changed the UX of the docs page and work on some bigger and more long term structural changes to the docs.

Tasks

Preview Give feedback

1. Initial user interviews #2217
   research +1
   
2. Adapt Keptn landing page #2216
   documentation +1
   
3. Add a simple NOTES files to the Keptn Helm chart #2318
   helm +1
   
4. Improve docs search by customizing settings and page ranks #2319
   docs-infrastructure +1
   
5. Add missing metric setup after adding metrics provider on evaluatemetrics page #2320
   documentation status: ready-for-refinement +2
   
6. Improve CRD reference page intro paragraphs #2321
   documentation good first issue +2
   
7. Always link the word workload to the corresponding k8s docs page #2322
   documentation good first issue +2
   
8. Remove empty pages #2323
   documentation +1
   
9. Add required/optional info to all fields in CRD reference pages #2324
   documentation +1
   

   
10. Change custom search engine to a keptn owned one #2337
    chore docs-infrastructure documentation +3
    
11. PoC: ReadTheDocs for Keptn docs #2458
    research +1
    
12. New structure for documentation #2490
    documentation +1
    
13. Move auto-generated API reference #2494
    docs-infrastructure +1
    
14. Create separate page for HPA usage #2495
    documentation +1
    
15. Update architecture sections for Keptn components #2498
    documentation +1
    
16. Update integrate with apps page #2497
    documentation +1