Cookbook and other forum things
Posted: Tue Nov 24, 2020 2:36 am
### Cookbook management
Someone rised an interesting matter.
Very old recipes are indexed the same, but belong to incompatible releases. Google and the site search seems to not care.
Suggestion
From now ownard, to be approved, a recipe should include in the name the release number it was made for. Lacking the version means pending the post until corrected.
Alternative
Subdivide the cookbook section into subsections each one aimed to a major (or compatibility mattering) release.
Archive the old recipes and warn people to re-release the recipe in the proper section if they care for.
### Upgrade the experience
I dunno if phpBB allow for this, but other forums benefit a lot by:
Reactions for posts. This allow to immediately spot relevant content
Status updates. This create community engagement and micro-discussions that doesn't deserve opening a thread (using DISCORD is not the same as having a discussion in the central hub of an engine, as many other experiments around proved).
Someone rised an interesting matter.
Very old recipes are indexed the same, but belong to incompatible releases. Google and the site search seems to not care.
Suggestion
From now ownard, to be approved, a recipe should include in the name the release number it was made for. Lacking the version means pending the post until corrected.
Alternative
Subdivide the cookbook section into subsections each one aimed to a major (or compatibility mattering) release.
Archive the old recipes and warn people to re-release the recipe in the proper section if they care for.
### Upgrade the experience
I dunno if phpBB allow for this, but other forums benefit a lot by:
Reactions for posts. This allow to immediately spot relevant content
Status updates. This create community engagement and micro-discussions that doesn't deserve opening a thread (using DISCORD is not the same as having a discussion in the central hub of an engine, as many other experiments around proved).