I agree with @stevemann! This just added confusion to new users in my opinion.
I would not think this should be a deciding factor. It is a limiter considering users may not be engaged via the forum yet. Decision should be made on potential new users, not what we have recently experienced. Cater to the non-experienced, not the experienced.
Just my opinion…
For a beginner to rebuild your system because they want to go from bare metal to virtualized is not that obvious.
On top of that, if you have automated your whole house, you want your HA to be available all the time so ‘starting over’ (how many of them know about the ability to restore a backup at onboarding…)
In the past I have given the advice to have a look at Proxmox because:
Of course, when virtualized, your HW/hypervisor becomes your SPOF.
I’m quite sure that more beginners run into issues with their HA compared to failing HW/hypervisor.
It all depends on the situation and having options is a strength with HA.
My suggestions:
For inclusion in posts referring to specific cookbook topics:
See the community-driven cookbook index for more topics you might be interested in or might like to contribute to.
For inclusion at the top of every cookbook topic:
This topic is part of the community-driven cookbook where you can find other topics you might be interested in or might like to contribute to.
Lol, my comment was totally sarcastic. I’ve read too many “I don’t know anything but I’m in the middle of brain surgery and need help…” posts.
I don’t disagree with the first one, but I have been more prone to copy the link out of the cookbook so they don’t have to double click or pull a section link out of the cookbook (like zigbee section) if they have fewer clues.
I was counting on the lower level posts themselves to point back up for more info.
The second one is much better than mine.
I might’ve expressed myself not well enough: I meant to add that in addition to the specific cookbook topic linked to in response to a particular topic.
A more complete example:
User X:
Some random question about a YAML error…User Y:
Your error is foo-bar-bas.If you want to better understand how to read YAML errors, see this cookbook page.
See the cookbook index for more topics you might be interested in or might like to contribute to.
Basically, I’m trying to cover both angles: If someone gets a link to a specific cookbook page, make them aware of the index in the post, but also, if you’re on a cookbook page, make it clear that it’s part of the index.
OK
I wrote quite a lengthy answer on a question on how to read a “simple” template, so I broke it out in a separate topic and linked to it from the cookbook:
I just read your other post and wanted to tag you here to ask whether we should make that part of the cookbook. You explained it very well.
There’s a new header Jack is loading on these.
I wasn’t sure if we already settled on something, but I put the last one in. On top and at the bottom, because the post is quite long.
I put it in a blockquote to make it stand out from the topic itself. Was that the intent?
@jackjourneyman Jack has been doing them, let’s look,
Here:
I had checked some, but probably ones he had not done (yet). But it is the same.
Don’t know if you fine folk take requests or not, but I have one because it frustrates me. Somewhere in these forums is a post where someone asks 'what is the difference between >-, |>, |, etc. when adding templates to yaml. But try searching for these characters? I would dearly love a reference to what they mean, their purpose, and how they’re read since they are used in examples everywhere without explanation. The cookbook would be a perfect place for it.
Yeah, the use of the characters don’t have any reference leading to their name: block scalars. See the description here https://yaml-multiline.info
Bookmarked! Thank you, that link was helpfull beyond measure. My post still stands though, it’s the usage of that YAML reference with Jinja Templates where you can also strip spaces (often new llines) without context is a 'thing I wish I’d known when I started… ".
At least Dev Tools>Templates gives you a good sense of the Jinja results.
Good one. I’m adding that to the index.
Having the cookbook link sentence at the beginning of the topics really detracts from quickly providing the information required. e.g. this one: Getting help in languages other than English
A non native English speaker is going to read the first sentance in a translator and likely dismiss the post as irrelevant.
Ya I was thinking the same. I might move them about 50 words down. I do similar for my Blueprint Posts, the first thing there is a TL;DR that shows well in the links, then I start with the business.
I was just going to change a couple of mine to see what they look like first before saying anything, but I agree.
Good point, Tom.