One thing that trips me up when I see this 4 quadrant structure for documentation is when to go with a tutorial and when to go with a how-to. Curious how others delineate between those.
- Tutorial: learn how the system works
- How-to: recipes for common use-casesHow-to(s) is a cookbook, targeting specific use cases, and may not particularly cater to novices.
Following this standard, a tutorial may contain a simpler or more contrived example; it may contain things you'd never do in production.