Agreed. Ideally we would fold this into the Content Guidelines, providing specific guidelines for each category, and then require that submissions are tagged with at least one category. So something like this:
All blog submissions must be tagged with at least one content category. Guidelines for each category are listed below.
I like that idea. I suppose, alternatively, we could make the “Tutorials” category applicable to a broader swath of content, to include “user stories” as well. I’m not sure what is best. Thinking more about it now, though, I wonder if we might require tutorials to answer the following upon submission:
- What question does your tutorial answer, or what problem does it solve?
Reading your updated submission now, I guess that’s what I would most like to have clarified. To address the concern someone raised in Zoom, we want to make sure the blog is not just adding more fragmentation to the farmOS community, which already has this forum, Riot, GitHub, the User Guide, etc. Namely, I think this blog can serve as a repository of material that is less open-ended and conversational than the forum or Riot, more niche and context-sensitive than the User Guide, and generally more conclusive and authoritative while still not requiring continued maintenance.
So yea, with that all considered, when I read “Conclusions: Inconclusive” in your post, that does make me wonder if it might be better suited to the forum. At least for now. But I think there is definitely the kernel of a good blog post in there, which would potentially answer: “How to use sensors and observations in conjunction to monitor farm conditions more effectively.” Perhaps even then it might make sense to categorize it as a “User Story”, because we don’t expect that it will be the one and only definitive solution to that problem, but that it will at least posit a few examples of ways you’ve personally managed to solve that problem within your specific context.