Improve Alexa Smart Home Documentation.

[ochlocracy]

Proposed change

• improved documentation for the Alexa integration
• added the configuration section
• added supported integrations
• added how to enable features only available with configuration overrides.
• added example utterances available for entities.
• added styling for the kbd and samp HTML tags for voice input.

Utterance styling
The current code tag does not provide a styling that resonates with voice input/output. Using kbd and samp is semantically correct for this situation but the default browser style lacks the representation of voice. I reviewed how Google Assistant, and Amazon styled voice input in their documentation and created a style for situations semantically correct for voice input. e.g. p tags inside kbd tags. I welcome comments, as it's something that can be used through the HA documentation.

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase:
• This PR fixes or closes issue:

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

[frenck]

I've stopped reviewing halfway, because it is a huge PR and contains a lot of the same things.

Please:

• Ensure you have an empty line after each heading.
• Use common markdown, avoid the use of HTML. (The images are allowed).
• 1 empty line for separation is enough, more don't have a function in Markdown.
• Lines do not need whitespace at the end.
• Ensure headings are in level order.
• Try to avoid easy, simple, simpler, easiest, simply, they can be received condescending by the reader.

[frenck]

Header level if of, compared to the parent heading level.
Make a new line after adding a header.

[ochlocracy]

This is the only one I was unsure of exactly what you were asking. I assume you were saying "header level is off". I ended up removing this header since it's the same as the H1 for the page and restructured the headers for the entire page. Please Confirm.

[frenck]

A couple of commas and those type of things.
Furthermore, darn m8! Nice job! 👍

[ochlocracy]

Thanks for the help @frenck you are a machine 🤖.

[frenck]

Thanks for the PR @ochlocracy! 👍