Convert Level sections into headings and lists in docs/01-understanding-github-web-structure.md

[taylorarndt]

Please implement the following changes in docs/01-understanding-github-web-structure.md (this issue is for implementation, not just tracking):

1. Replace the Level code block under '## 1. GitHub's Three-Level Structure' with explicit headings and lists.

Example structure to implement:

Level 1: Your Account / Profile

• github.com/your-username
• github.com/settings/...
• github.com/notifications

Level 2: An Organization or User's Space

• github.com/microsoft
• github.com/community-access
• github.com/github

Level 3: A Repository - where all the work happens

• github.com/community-access/accessibility-agents
• github.com/community-access/accessibility-agents/issues
• github.com/chore: update agent manifest accessibility-agents#42

2. Ensure the headings use appropriate heading levels (H2 for the three Level headings, or H3 if you prefer to keep the existing H2 '1. GitHub's Three-Level Structure'), and ensure the example URLs are formatted as bulleted lists for quick scanning and keyboard navigation.

3. Keep the explanatory text that follows ("Most of this workshop happens at Level 3.") in place and update any cross-references or anchors if needed.

Notes:

• File: docs/01-understanding-github-web-structure.md
• Assignee: @accesswatch
• Labels: documentation

Please implement the changes directly in the file and open a PR when ready. Thank you!

[taylorarndt]

I want to make the structure of the website easier for people to find — opening this thread to discuss ideas and get feedback.

@accesswatch @maintainers: please share your thoughts and accessibility concerns here. Does converting the Level code block into explicit headings + bulleted lists improve scanability? Any preference for H2 vs H3 for those Level headings?

If you agree, we can implement the change in docs/01-understanding-github-web-structure.md and open a PR. Thanks!

[taylorarndt]

I want to make the structure of the website easier for people to find — opening this thread to discuss ideas and get feedback.

@accesswatch @maintainers: please share your thoughts and accessibility concerns here. Does converting the Level code block into explicit headings + bulleted lists improve scanability? Any preference for H2 vs H3 for those Level headings?

If you agree, we can implement the change in docs/01-understanding-github-web-structure.md and open a PR. Thanks!

[taylorarndt]

Closing — what I thought were tables were actually ASCII art diagrams. These have been addressed in PR #168 which converts them to SVG images with prose descriptions below each one.