Add info on teaching automations

[robmarkcole]

Description:
Add info on teaching automations, since the teaching events were removed

Checklist:

• Branch: Fixes, changes and adjustments should be created against current. New documentation for platforms/components and features should go to next.
• The documentation follow the standards.

[MartinHjelmare]

Only templates require the raw tags.

[tjorim]

Could you please expand on that a bit more? When to use, when not etc.
This is pretty unclear in the 'documentation documentation' in my opinion.

e.g.

Configuration

The Configuration Variables section must use the {% raw %}{% configuration %} ... {% endconfiguration %}{% endraw %} tag.

The '... tag', I see multiple tags? Should we use both those tags or is it in this case just poorly rendered and do we only use the {% configuration %}-tag?

Embedding Code

You can use the default markdown syntax to generate syntax highlighted code. For inline code wrap your code in {% raw %}`{% endraw %}.

Are those {% raw %}-tags something we should include? Is this again a case of bad rendering and does the documentation actually just mean to use ` for inline code?

[robmarkcole]

@tjorim my reading of it is that only the contents of the yaml (i.e. configuration) files should be enclosed in the raw, so my example service data should NOT be enclosed. Is this correct @MartinHjelmare ?

[MartinHjelmare]

We don't want jekyll to try to process the curly braces in jinja templates. So we use the raw tag to temporarily disable tag processing. Read more here eg:
http://ozzieliu.com/2016/04/26/writing-liquid-template-in-markdown-with-jekyll/

So to answer the question, only literal yaml that contains templates, ie curly braces, needs to be contained within raw tags. But of course there are other cases where we need to disable tag processing. Trying to list that is out of scope for this review.

[frenck]

Merged a little too quickly.. there was a spelling error.

[frenck]

you -> You

[frenck]

Furthermore, this is not related to a parent PR, so it targets an incorrect branch. It should have been the current branch.

[MartinHjelmare]

No it is related to a parent PR. It was just not linked.

[frenck]

@MartinHjelmare In that case, it should have been linked before merging.

Could @robmarkcole or you add the link please?

[MartinHjelmare]

This was a follow up of #5789.

[frenck]

Thanks, @MartinHjelmare! 👍

Parent PR: home-assistant/core#15439