Thanks for the comments - more are very welcome.

I’ve been doing some more thinking/investigating so thought an update would be useful.

Tags I wouldn’t need to lock tags down as much as I thought. I already have tag groups (I’m not sure if you see these). With a bit of rearrangement I could create a tag group for each new category which lists the ‘mandatory’ tags for the category. By mandatory I mean that at least one tag from this group must be added to every post in the category. Multiple tags can be added to a post.

I would also probably add an “I don’t know” type tag into each group for those instances where there doesn’t seem to be a useful tag. This tag would allow me to monitor its usage and either add a more relevant tag to a post if there is one, or consider adding a new tag to the group if that makes sense (and then add that tag to the post). The “I don’t know” tag is therefore a kind of temporary position holder because it’s not really that useful in a general sense.

After the mandatory tags/groups are added it would still be possible for people to add their own tags.

So as an example, in the Support category the mandatory tags might include Davis VP2, Ecowitt, Weather Display, CumulusMX, PWS Dashboard and Satatoga, i.e. a mixture of hardware, software and templates. You would need to pick at least one, and you could select more than one if required. If the question was about, e.g. Reolink webcams and there was no mandatory/optional tag for Reolink then you could still add Reolink as an additional tag to your post.

Tag groups might be used across multiple categories, e.g. the group of hardware, software and template tags would probably be mandatory in both Support and Advice categories.

There would probably be some tags with restricted usage, e.g. my “Rabbit Hole” sub-category would probably collapse inside the General category, but I’d have a “Rabbit Hole” that only I could apply to a post.

Categories I’m thinking that a drastic pruning would work. I’m classing categories in three ways (with one slight exception):

Curated - Content created by admin/mods with read-only access for everyone else.
General Access - Open for posts and replies by all registered users.
Private - Limited access special access categories. These would have individual access groups and would only be visible to those with access. Some of these already exist, e.g. for admin/mod discussions and private projects with invited members.

My current suggested list of categories would be:

  • Announcements - Curated with low volumes of posts about the forum, e.g. there will be downtime at this time, etc.
  • Support - General Access. For all questions of the type “I’m trying to do this but it’s not working like I think it should”, e.g. “I can’t get WD to upload my files by FTP”. This category would have the ‘Solved’ option enabled.
  • Advice - General Access. For all questions seeking advice on a subject, e.g. “What’s the best place to mount a solar sensor
  • Weather- General Access. Discussions about “the weather”, e.g. new records, weather photos, etc.
  • Development Projects - General Access-ish. This would be for discussions about weather related projects, e.g. software or hardware development. This would be a place for discussions about projects that are actively being developed. On release further discussions would go into the other categories. An access control group of active developers would be created. Only these people would be able to create new topics, with one topic per project (new versions of software would probably be new projects). Everyone else would only be able to reply to project topics. This is to try to keep discussions about active projects into a single thread for easier management.
  • Knowledge - Curated. This would hold the current Knowledge Base and FAQ categories.
  • General - General Access. This is “it doesn’t fit anywhere else” category, e.g. content that would currently go into the Chatter sub-category would be here.
  • Private - Private (obviously!) There are sometimes reasons for hidden categories with limited membership for projects, e.g. there was a category for testers of the new Discourse forum when I was setting it up. These categories will have specific member group and possible specific hidden tags. You’ll only see them if you’re part of the discussion so most people won’t see these.

There may be some other categories I’ve not thought of yet (and I’m open to suggestions) and the names may not be the best (I’m also open to suggestions of better names). I think seven visible categories is a good number and I think everything that’s currently on the forum fits into one or other of these. Seven categories means they can all be listed in the side bar and the current mind-bogglingly big list of categories and sub-categories would disappear.

Other thoughts are:

  • Topics not posted to within a period, e.g. 6 months, will be locked meaning that old discussions don’t suddenly reappear. New topics will be required, but these can still have a link to the old topic or quote from it.
  • The current read-only archive categories will be incorporated back into the categories listed above, but will be locked for new replies.
  • The category headers will be more descriptive and describe what should be posted in the category and what access is available.
  • You can search on words and tags, so you could see all topics with the WD tag wherever they were posted or if you wanted to be more specific you could search for the WD tag in the Support category where the post also contained “February”.

That’s all for now!