Assign unique heading identifiers for numbered headings

[AshleyHenry15]

When you add a number to a heading to represent a step in the process, that number gets added to the URL. Therefore, you are immediately limited to scaling up and growing without having to add annoying redirects.

Anytime you use a number in a heading, you should define a unique identifier. This is also a good practice for long headings or things that are subject to change.

The existing headings should be updated, you do it like this (strip the number from the URL):

## 1. Install from sources { #install-from-src }
...

[koverholt]

These are great points you raised in #109 and #110. The ADK launch last week rocketed 🚀 us into where we are today, which is awesome! As we're writing up the short- and long-term ADK docs plan and ADK community growth plan, we'd love to hear input from folks like you in the community! Especially as we're thinking about the top N OSS documentation and community growth principles to help our (quickly) growing user base 😁.

Just to kick off some ideas (we'll organize a more structured home for this soon!), I'll start with one of my favorite topics: standards and style guides! Some of my favorite style guides are:

• https://developers.google.com/style
• https://www.writethedocs.org/guide/
• https://docs.gitlab.com/development/documentation/styleguide/

Do you have any favorite doc style guides? Esp. when considering the different nature of OSS docs and the unique ADK community we're aiming to build here! 🙌