I’m not a web developer, so it may very well be “magic” to accomplish what I am suggesting.
It doesn’t seem impossible to use the body of the first post and display it like an iframe on the main site.
I know you didn’t ask but the why is because I think the cookbook should be part/included in the main documentation. It seems to be the the norm for most projects of this nature.
It’s incredibly difficult because there is no index. The entire page is hand selected, curated and hand written.
This entire section is hashed out by a group who care very much about differentiating good examples and patterns to follow. They go over it often and argue about it on a regular basis. There’s nothing automatic going on here I can assure you. And why Jack asked the question.
If I’m building this by hand what do we want it to look like…
And yes it very much has to be by hand right now. No magic.
And along with what Nathan said, HA and the powers that be may not agree with everything we put in the Cookbook, which is why some of it is there (has been bounced from requests to put it into the official docs), so there is very little chance of a full endorsement without full content control.
Being as it is it is UN-official, grass roots. You put it into the Docs beyond a link in the footer page or something it becomes official policy, and that isn’t going to and shouldn’t happen IMHO.
Cookbook stays as it is. 
Let’s form a coalition! 
(Happy with the outcome.)
The cookbook is well done. The problem is visibility. I’ve been using Home Assistant since before Lovelace and I never heard of the cookbook until a few weeks ago.
I think this is the wrong concussion. 52% voted for change. Because there were more choices for change, they didn’t agree on which change is best yet.
Also, if it will change, people who voted for no change might want to vote for a specific option.
Only 21 people voted. As samples go that isn’t significant. The change wouldn’t have been justified even if everyone had voted for it.
The current format works. Any progress on a link to make the cookbook easier to find?
What do we think of this guy for the cookbook?
Well, they took a several year hiatus and a bunch of stuff broke.Kinda a strike against for me. They seem to be back again.
The stuff is great when it works, but you have to be a Drew or 123 to figure it out. Very complicated. Need 2 blueprints to make anything work. Honestly I could never figure their stuff out. I tried twice…
Rookies (and me) sometimes struggle with their stuff.
If you go at it as a box of magic, then it all works.
I avoid blueprints because I don’t see what’s going on behind the curtain. Give me a YAML example, please.
The code is there, it’s not hidden.
These are among the more complicated is all. It’s like trying to figure out Petro’s config. I circle the drain when it gets that deep.
Sums up Home Assistant for me…
I don’t use blueprints either, which is why I asked. I liked his organised approach - seemed better than the random pile of stuff in the Blueprints Exchange.
That I agree with. They do good documentation.
Maybe wait a bit to see if he can sustain it this time.