Docs: Split Traffic Analytics to a How-to guide and a Feature entry (Diátaxis)

[benjaoming]

Refs: #9746

---

📚 Documentation previews 📚

• User's documentation (docs): https://docs--9677.org.readthedocs.build/en/9677/

• Developer's documentation (dev): https://dev--9677.org.readthedocs.build/en/9677/

[benjaoming]

I think this fits quite well into the "Main Features" page which is the target of a later refinement.

So by adding the feature here, we can ensure that it's duly processed in a later iteration.

[humitos]

@benjaoming can we avoid using force-push? In particular, after getting reviews from PRs. Otherwise, it resets my review and forces me to see all the differences again instead of keeping the files already reviewed collapsed and showing only the new differences since my last view.

[benjaoming]

@humitos the force-push here happened because I merged in main by mistake.

[ericholscher]

This is close 👍

[benjaoming]

re: @ericholscher

I think it's probably better to draft new pages in our feature list for this, but I guess having them here before refactoring them later is OK?

I need a bit more guidance here. What sort of feature page do you mean? How should it be included in the navigation? The strategy for the 4 iterations has been to convert feature pages into explanation. We have talked about a structure for documenting features through some kind of pattern, but this was left out.

[ericholscher]

@benjaoming

I thought we explicitly said we're building the features list in the sidebar for now, and then moving it to Reference?

That is what I'm describing, is that analytics "feature" page, which will be under the sidebar Features page for now, but moved to Reference > Features later.

[benjaoming]

Ah, I missed that in the task list, thanks 👍

[benjaoming]

@ericholscher some new texts added, this is ready for another review.

[ericholscher]

Looks great!