cc. @CAM-Gerlach #diataxis

• introduction
• tutorial
• reference
• guides
• concepts

Maybe it is better to swap Concepts and Guides:

• introduction
• tutorial
• reference
• concepts
• guides

FWIW, I teach sqlite3 directly from the current docs. They are VERY useful as-is.

I would like to know what problem is being solved here. From what I can tell, no user has ever had issues with the current arrangement.

FWIW, I teach sqlite3 directly from the current docs. They are VERY useful as-is.

Thanks!

I would like to know what problem is being solved here.

The top-level structure is flat. I'm suggesting to organise the sections under headings:

From what I can tell, no user has ever had issues with the current arrangement.

As I view it, this is a weak argument for keeping things as they are. There can be room for improvement, both in docs and code, even though no-one has taken the steps to create a ticket on the bug tracker.

Maybe it is better to swap Concepts and Guides:

At least per Diataxis, the most natural flow would have Explanations ("Concepts") last, since they are higher-level discussions of less urgent immediacy to most users...though, at least one of the "Concepts" subsections doesn't quite fit the "Explanation" mold, as discussed on the PR, and phrasing them as "Concepts" conveys more primacy than "Explanations".

FWIW, I teach sqlite3 directly from the current docs. They are VERY useful as-is.

Given your perspective, any additional details you could provide would be quite helpful. Are you referring to useful to yourself as an instructor? Or to your students—and if so, it would be helpful to know how you're evaluating that? Are they being used as a tutorial, reference, how-to/guide, or explanation—or some combination? And for context, what sort(s) of students are we talking here?

Also, do you have any specific concerns you could share about the proposed structure and its effect on your teaching and your students?