What documentation is most critically absent?

What documentation is most critically absent?
Your feedback will help the project determine prioritization.

I am surprised there has not been a comment.
I suppose this is very good news. :-)

I have a list, but I am inclined to address those items in contribution rather than share it.

Documentation gaps:

Releases without associated touches to documentation is a critical gap.
Application/system updates without even change or scope summary feels like a critical gap, which should be in system and available in documentation.
The What’s New page is not archived/logged any where so the next Release replaces the last What’s New.

brianthehughes
That is encouraging to see.

When new users arrive at GhostBSD, what gaps or shortcomings do they typically notice in the documentation?