But if I put on my āpessimistic thinking hatā, Iād be concerned that we only add to confusion for newcomers: Why does my example menu work in the playground but not on my site? That would give us two websites to ādebugā: the repository and the code thatās in the playground.
Problem of course is that Hugoās strength (its flexibility) becomes a disadvantage in a playground, since that playground likely always differ from someoneās local website. Or not?
The pessimistic hat is a handy hat to have around!
If there was one interactive playground website, I would imagine it to have the āmost common use case scenariosā ā a couple of menus, blog posts, categories, tags, a handful of pages etc. I think this would help beginners get off the ground. Then (blue sky hat on), when a user interacts with the playground website, a new instance of it is spun up just for that user.
Why does my example menu work in the playground but not on my site?
This question is much easier to answer if you actually have a working playground you can play with and break yourself.