If I could get the third free text answer: After the suggestion from @code-in-progress I’d like to take the “categroy” variant, where we could list “one-liners” for experienced users, that would fit nicely, don’t you think?
And we could collect more entries for that “category”, I’m quite sure there are a lot of useful links in my bookmarks…
But I’d maybe put this category in a “hide”-menu.
This one:
Advanced usage examples
Caution, use at your own risk, and only when you know what you do!
I voted against it because we already have a markdown dictionary, and the format of that just confused the shit out of me. I had to read it like 5 times before I decided it’s a one line markdown statement with odd choices.
Basically the way it’s written I had problems with, I guess not really the content.
I know I also confuse people when I explain things, but that was obtuse as an attempt at entertainment, I didn’t like it.
Is that still necessary? The default value has to be used for more than two and a half years. Practically all examples should have adopted the “new” default value till now.
And if not, the example is likely to be out-of-date on its own.
On the other hand it is a very well written guide, and it could work as an example for how to use the default value…
I lost it and thought it would fit in the template section along with some examples we add ourselves.
Now this one falls into the one-liner kind of thing, but that link alone has 25 separate examples. And hey, who doesn’t want to type in Morse code anyway?
I should have added a fourth question to the poll about “one liners”.
Should we be doing advanced stuff at all?
0voters
As I remember (all those weeks ago…) the idea was to provide basic “how to” posts in response to commonly asked questions. Actually the posts are getting more and more obscure - probably reflecting our own interests rather than those of non-technical newcomers.
Maybe we should be pruning… I like the idea of hidden advanced pointers, which seems to give the best of both worlds.
Though I’ve recommended Skalavala’s guide many times, I don’t think I’d add it as-is. I think it would be better to have a few posts that cover template basics more topically. That way, when they are referenced, people aren’t being sent to a confusing, encyclopedic collection of templates.
In accordance with the will of the people, I have created a new “For More Experienced Users” section and moved a few posts into it (basically, the ones I don’t understand).
Unlike macros it will return data types other than strings, but the template only renders on restart or if you call homeassistant.reload_custom_templates, so if the user isn’t careful they can end up with unreliable output.
Design question: have you thought about putting the data into a table? I had the same problem a while ago with the list for Midea A/Cs.
I thought, it might be better readable, if people give their information in one post per device, and a list in the starting post gives the link to that post.
I remember a poll, where the question was “Do you use Home Assistant?” 
