Challenge 1: Organize a Collection — Possible Solution
====================================================================

Blog API (collection)
├── Posts
│   ├── List Posts
│   ├── Get Post by ID
│   └── Create Post
└── Comments
    ├── List Comments for a Post
    └── Create Comment

WHY THIS WORKS AS AN ANSWER
------------------------------
Two folders, grouped by RESOURCE (the same principle as the chapter's
Shop API example grouping by Products/Orders/Users) rather than by
HTTP method or by any other criteria: Posts holds everything about
posts, Comments holds everything about comments.

"Listing comments on a post" belongs under Comments, not Posts, even
though the request's URL likely nests under a post
(e.g. GET /posts/{id}/comments) — what matters for organization is
which resource the request is fundamentally ABOUT and returns, not
which URL path segment it happens to start with. A developer looking
for "how do I fetch comments" should find it under Comments without
needing to already know it's nested under posts in the URL.