[Tracking] Reduce the use of distracting UI elements in the documentation

[lsgunn-teleport]

The current documentation uses a lot of custom components (Admonition, Details, Notice, Tabs, and so on). In most cases, these components reduce readability and impair comprehension more than they assist the reader. It's a pervasive problem in the documentation. We could also use some refinement in our design (font sizes for different heading levels, a less aggressive presentation for inline code and (especially!) code blocks.

See also
#93
#362

We’ll kick off this effort by reviewing and revising topics that need to be updated for other reasons. For example, Windows desktop supports local users for Community and Team editions in v14, so as part of updating the body for those enhancements, we'll minimize the disruptive components.

Tasks

Beta Give feedback

1. Update style guide with recommendations for using components
2. [Docs] Style guide: Terminology and usage conventions (proposed new style guide section) teleport#31664
   documentation size/md +2
3. Revise Desktop access topics to reduce over-styling and improve readability
4. docs: Update the desktop access introduction teleport#31599
   backport/branch/v12 backport/branch/v13 backport/branch/v14 documentation size/sm +5
   
5. docs: Desktop access: Move local Windows users content changes to a new version of the gett… teleport#31678
   backport/branch/v14 documentation size/sm +3
   
6. Revise desktop access-Active Directory script-driven teleport#31389
   backport/branch/v12 backport/branch/v13 backport/branch/v14 documentation size/sm +5
7. Revise Desktop Access manual active directory config teleport#31390
   +0
8. docs: Simplify the commercial prerequisites to get rid of overstyling teleport#31676
   backport/branch/v13 backport/branch/v14 documentation size/sm +4
9. Revise Server access topics to reduce over-styling and improve readability
10. docs: Draft of troubleshooting topics for Server Access teleport#31997
    backport/branch/v12 backport/branch/v13 backport/branch/v14 documentation size/md +5
    

[ptgott]

As a possible part of this project, we can add guidance in the docs UI reference for when to use Admonitions, Tabs components, Notices, etc. This comment is a good starting point.