[ADD] Events: Create Attendees report page

[stepperpig]

Goal
Create a new Attendees reporting page in the Events documentation. Documentation currently includes a page on Revenues reporting that references Attendees reporting, but there is no existing official doc on the topic. This PR addresses that need.

Changelog
Created a new doc providing an overview of the Attendees reporting page + a brief example of intended end result.

Next Steps/Additional Notes
This doc is similar in structure to the Revenues report page. Potential next step is to re-organize both the Revenues report and this Attendees report page as sub-topics under a general Reporting overview page. This would potentially require additional reworking of these docs.

Version Scope
This PR should be FWP up to master. Any discrepancies in 19.0 will be addressed in a future PR.

[robodoo]

[stepperpig]

Hi @meval1006, got a PR for you to review when you have a moment!

[meval1006]

Hi @stepperpig, great start at a new events page. I have some edits I proposed and would like to check the page again before signing off. I have categorized my edits as either suggestions or corrections.

If you have any questions, let me know.

[stepperpig]

Hi @meval1006 this is ready for a re-review!

[meval1006]

Hi @stepperpig, good job with the example and the other edits. I just have a few more revisions, but once you're done with those, you can pass this to Felicia.

[stepperpig]

Hi @Felicious this is ready for a final review!

[Felicious]

Hi @stepperpig !

This is a really solid doc overall! The structure is clear, I love the tabs, and the flow is easy to follow, and it’s obvious a lot of care went into organizing the different views and keeping things consistent. That’s not trivial, especially for reporting documentation and one of the first few docs you're authoring from scratch on the team 😊

One thing to keep in mind (and this is more of a general challenge with reporting docs than an issue with your work specifically) is that this type of content is inherently tricky: it needs to stay generic, but still be actionable.

Right now, most of the descriptions are technically correct (they explain what each view displays) but in a few places they stop short of helping the user understand how to actually use that information. In other words, the "what" is clear, but the "so what?" is sometimes missing.

A small tweak that would go a long way is to anchor each view with 1-2 concrete examples of how it can be used to analyze event data (e.g., identifying registration trends, comparing attendance across events, spotting late registrations, etc.). This helps users understand not just what they’re looking at, but when and why they would choose that view.

Overall, you’re very close! With a bit more emphasis on actionable insights, it’ll be significantly more useful to end users (:

[stepperpig]

@Felicious ready for re-review!

[Felicious]

Wonderful work implementing my feedback, @stepperpig !

I found some super minor, non-breaking spacing and alignment issues, and after you implement those, this PR is ready for merge!

@robodoo delegate+

[stepperpig]

@robodoo r+