https://www.swyx.io/documentation-levels is my proposal. match documentation features to project maturity.
Level 0: Basic proof of concept
---
Example audience: you/colleagues/hobbyists One sentence description for github headline README with API docs - goal is to save yourself from looking at source code
Level 1: v0.x
---
Example audience: greenfield early adopters. Ok with missing documentation, they are here for the idea. can contribute code/docs
One paragraph description with more context - could be a sales pitch but also give an idea of when to use you
Feature list/Project Goals Install + Config Instructions
Level 2: v1
---
Example audience: brownfield early adopters. Ok with bugs, they have some problem that isnt well addressed. Needs convincing.
Comparison vs comparable libraries
Problem Statement - what you solve, how the developer/end user is better off with your thing than handwritten. aka Why You Exist
Basic Examples
Live Demos
Level 3: vX
---
Example audience: early majority user. Wants ease of use, quick wins. Need to be very reliable. Needs content to sell solution to team
Project Status badges
Tutorial
Third Party Plugins/Libraries
How-To Guide/Cookbook/Recipes
User/Maintainer Content
Official Blog/Project and Meeting Notes
Talks
3rd Party Blogs
Video Tutorials
Podcasts
Comprehensive Examples
and so on (up to level 6 in the doc)