Documentation fixes and improvements

[mtardy]

Content

Preview Give feedback

1. Add a reference page generated from the CRDs.
2. Add a reference page generated from the helm chart values #1287
   area/documentation +1
   
3. Write the "Try Tetragon on Kubernetes" to replace the Kubernetes quickstart guide.
4. Insist in the "Try Tetragon" guides that none policies presented are for production use.
5. Enrich the troubleshooting Tetragon guide: we already have a Debugging Tetragon but we could add more troubleshooting strategies: look at metrics, use bpftool, etc.
6. Write a dedicated concept page or subpage for advanced features like followfd or the operators targeted at sockets.
7. Split the huge concept page for tracing policies #1378
   +0
8. Add tracepoints example in the tracing policy documentation.
9. Add documentation for uprobes #878
   area/documentation +1
   
10. Test and document the limitations of the fields in TracingPolicy #709
    0 of 3
    area/documentation area/testing +2
11. Unify and organize how filters are documented in the TracingPolicy documentation #708
    +0
12. Document the available types of arguments for kprobes and tracepoints #707
    good first issue +1
13. Add documentation/tutorial on how to read Tetragon metrics #928
    area/documentation good first issue +2
    
14. docs: clarify beta status of Tetragon on the docs home page #1166
    +0
15. doc: automatically generate the tetragon daemon flags reference #1427
    area/documentation good first issue release-blocker +3
    

Web development

Preview Give feedback

1. Docs: update docs design #931
   +0
2. docs: fix sticky header, TOC scrolling and add search bar #1026
   +0
3. Make anchor links to be below the top navbar and not at the top of the screen #1431
   area/documentation +1
4. Font in the header bar is smaller than the font used in the documentation.
5. Monospace font used in code blocks looks bigger than the one for the standard text. They are both technically the same size but in different fonts.
6. Navbar on the left has wasted space at the end of the page. See [1].
7. Increase the maximum width of the documentation page
8. Provide an option to have documentation pages with unlimited width (for reference pages like the gRPC API).
9. Make the search work. See the Docsy documentation about that.
10. CSS for mobile: adapt the size of the section title, adapt the margin after the hero, hero illustration is not center (need to be cropped)
11. Fix the navbar and footer height, see docs: fix footer #1404 (comment)
12. Update to latest Docsy version

[1]: Navbar wasted space