There are a lot of gems not easy to find and figure out the right location.
We could add this in the training at least as a hint without taking too much responsibility for this setup.
Having this buried at [[community.plone.org]] under the wrong topic does not help.
My question is now:
What is a good practise to share inofficial community driven HowTos with our fans?
Avoid having examples given to be used by experts mistaken in a wrong connotation as recipes granting success guarantee to idiots, and you can rely on as dumbest user.
Stackoverflow was once a first class startpoint, but it seems not so much up to date for Plone.
My goal is to get this fixed asap and have a starting point to filter for upvoted best practise beyond the classic trainings.
See also:
https://stackoverflow.com/questions/tagged/plone
I quoted the url because the forum software generated a misleading preview
(this seems like barking up the wrong tree today and is quite dead with low Q&A rate and very few votes)
Here is always a good place. Because we have full control over the content in the Community Forum and it is well indexed by search engines, I'd favor here.
Plone 6 Documentation is another option. File an issue in the repo to discuss.
The reason why we decided to use this Discourse forum was precisely to gather all Q&A here, where, as Steve says, it is easily searchable and threaded.
I agree that collecting some recipes isn't going to work in training.plone.org, which is a collection of well maintained materials for giving a class. It sounds to me like the recipes you're talking about are for a lot of different topics in Plone, so really they should be integrated with either existing documentation or training materials.
We have had this discussion earlier and concluded it is a good idea to set up a best practice part that goes into the site or documentation part.
The topic was called Plone for dummies.
I have started a dropbox paper on this and invited tkim to review and improve.
He did give me some pointers already, but I haven't had the time to work on it.
@acsr You are most welcome to contribute to the best practices doc. Give me a pm and I'll set you up.