Just updated this guide for 2024: https://community.home-assistant.io/t/editing-the-documentation-and-creating-a-pull-request-on-github/9573 any point including it in the cookbook?
2 Likes
I don’t think it fits with the cookbook introduction paragraph. But I really like it and I do think it belongs either somewhere in the cookbook, or as a pinned topic by itself in the community guides, or both.
I think we can add a “Contribute to the project” heading and put it there. Maybe some dev guides could go there too.
4 Likes
Editing official documentation is very useful.
+1 for adding it to the cookbook.
“Getting Started With HA” contains a bit if everything.
A new section with “contribution to the project” also makes sense, but I wouldn’t mind having this particular topic more towards to community and beginner chapters.
A similar guide on how to contribute to translations would also he a good start for beginners to get involved.
Did it get added? Can’t see it. Mind you, Tom’s been busy… 
Edit: I’ve put it in the “More experienced users” section.
Edit, Edit: See below.
Good idea - done that. Can’t get the “11” right, though. The blue numbers only seem to go up to 10.
1 Like
Given the interest lately, should we have more about voice assistants?
I personally could do with a clear explanation of the difference between using a voice client (Alexa, Voice Assistant PE) and custom sentences/intents. There seem to be clear limitations on the latter (no LLMs), but with the former you can’t use existing speakers. It isn’t very well documented.
There are also several different ways of using Alexa which could be made clear. I’ve noticed one or two people conflating them and getting stuck.
A fun thing might be a comparison of the different voices available, with samples. (My personal favourite atm is “Brian” from Amazon Polly - elderly butler who has been at the sherry.
1 Like
Yeah, the “help us help you” page does the same thing you did with 11. I changed the 10 to one-zero to match the one-zero visually.
1 Like
I haven’t made any progress like I had planned, and I’ve really lost steam on the idea. As I read through what I’ve wrote, I’m starting to realize it’s not possible to achieve what I had set out to do. There’s just too many topics that I wanted to cover and it’s not possible to make it easy to read at the same time. I think having the topics split up into different posts like the cookbook already does is the best way to do this.
I’m open to anyone who wants to move the guide forward, or I’m also open to deleting it or taking any valuable pieces and moving them into other parts of the cookbook.
I know the feeling!
Leave it for a while before you delete it - someone else may be able to add to it.
Still worth doing, I think. Newcomers are always asking for this sort of thing.
jackjourneyman (quoted from a private post…)
If we want to increase use of the cookbook, it might be useful to mention it as a resource when we link to a cookbook post. At the moment users might follow a link on a specific topic without realising what else is there. Or maybe put the link to to cookbook index at the top of cookbook posts - ATM it’s at the bottom and probably doesn’t get seen much.
ME Replying…
Suggestions?
A cool 1 sentence with a link anyone to add to them all maybe?
I’ll start.
For more helpful posts like this, click on [The Community Cookbook] for an index to many more.
Let’s start there
Add, subtract and strawman things…
1 Like
250 posts is TLDR. Put in regular links to it in the post. Perhaps you do but its too long to read back.
True…
I forget that because it’s always one of my open browser tabs,
I quote from it a dozen times a day…
I think it’s good to have a link to the main topic where one posts cookbook links.
Perhaps having a link at the top of each cookbook topic to the main one would be useful too to show people that there’s more. I know there’s already a link at the bottom of a first post, but it’s easy to miss.
1 Like
I’ve looked at the cookbook, but there is a glaring omission. Why is Install Home Assistant Operating System (I.E. Generic x86-64) missing from the index?
I don’t understand the fascination with ProxMox on minimal hardware.
It is a huge mistake to send new Home Assistant users to install ProxMox on a dedicated server like a Raspberry Pi, Intel NUC or other micro PC.
Installing ProxMox requires an understanding of Linux, and if a new Home Assistant user could get ProxMox installed and configured, then they wouldn’t likely be here asking how to install Home Assistant.
HAOS on bare metal:
- Flash the HAOS image to the boot drive.
- Reboot.
That’s it. Done. No learning curve for Proxmox, Docker, VM’s. No USB or Network issue. No managing disk or memory allocations.
The downside of bare metal? Your Home Assistant host computer is just that. Dedicated to one task. It just works.
If the user needs to run other programs on their Home Assistant server that aren’t available in an add-on, migrating to ProxMox can always be a solution later.
I just added it. Thanks for the catch.
Because nobody brought it up, until now. No conspiracy. That’s why we have this topic.
Good – in the spirit of a community forum.
Anyone that’s been here more that a week should have permission to edit it. Just follow the guidelines laid out.
1 Like
I haven’t found that to be a limiting factor for many people on this forum, and that’s including substituting any word for “Linux”. 
Really, people seem more than happy to go out on a limb with little advance thought at all.
Do you want familiarity with Linux to be a prerequisite for beginners? Anyone who can install and configure ProxMox probably won’t be in the “Beginners” section of the cookbook in the first place.
But, I am of a conflicted mindset here. Too often I see posts from people who shouldn’t be trusted with anything more complex than a flashlight, let alone a Z-Wave switch with Scenes.