Define and categorize metrics about almanac.httparchive.org

[tunetheweb]

@rviscomi approximately how many metrics do you expect in a chapter?

The original post had the following:

Subject Matter Expert (Author)
Responsible for providing an interpretation of the HTTP Archive data for specific chapters aligned with their area of expertise. For example, in the JS chapter, explain what the implications are for the number of bytes and CPU execution time to be rising. 1-2 paragraphs per metric are expected plus an intro and summary conclusion. Think of it like one blog post in a series written by many authors.
During the planning phase 5, experts should ensure that their chapters contain the necessary metrics to accurately capture their state. Also help us identify if there are any metrics that we are currently unable to capture so we can work on getting them in place for next year’s edition.
Time commitment: 2 hours in April to coordinate on chapters’ metrics, 4 hours in August to write interpretations.

So you thinking about 5 metrics in a chapter with a paragraph or two for each? Or 3? Or 10? Or 100? While it can of course depend on the topic and the author, I think it would be good to set a rough benchmark as a guideline so we're all roughly on the same page.

[rviscomi]

@bazzadp great question. 10 metrics per chapter on average sounds like a good amount. It's a balance between being comprehensive while respecting authors' time and readers' attention.

And 1-2 paragraphs per metric SGTM. We want readers to understand the implications of each statistic but we don't need to be overly verbose to get the point across.

These are loose guidelines and authors have the freedom to write more or less as they see fit. During the review process we can make adjustments as needed.

[rviscomi]

Leaving this open as we finalize subject matter experts assigned to each chapter.

Note to self for next time: assigning experts to chapters first gives us the chance to get their input on the metrics much sooner.