Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
@AquaticDisorder suggested the need to allow filtering of content (discussions, at least) by OS. Deploying OS-specific groups isn't feasible, considering the site was engineered not to use groups.
I suggested the use of a taxonomy (to which @mig5 concurred) but we are concerned that vocabularies tend to go unused.
Comments
Comment #1
ergonlogicI added an exposed views filter for the keywords vocabulary in a block, and a 'reset' button via the views_hacks module.
Comment #2
ergonlogicI added Community Tags (6.x-2.0-beta1), and activated it for the Keywords vocabulary, which I extended to discussions (in addition to book pages). I also added a block interface for tagging on discussion pages.
We could potentially extend this to the documentation too, but lets see how well received/used it is in discussions.
Comment #3
ergonlogicI'd appreciate some testing & feedback.
Comment #4
AquaticDisorder CreditAttribution: AquaticDisorder commented@ergonlogic, what I intended to get at is not necessarily O/S related more that:
So what do I think can be improved?
I think as the list of posts gets longer users are less likely to search through and see if the topic they are interested in has already been discussed previously and therefore are more likely to create an identical post, I think duplicate posts are less useful to have as obviously this just makes the list longer compounding the problem.
As a user what do I think of the "tagging" solution?
My main motivation in the first place was that I was looking at the discussion feature as the community space, and thinking how it could be improved to encourage the development of Aegir's community, and how it could be better leveraged to make the information shared by the communiy more available
As it was
The discussion feature posts "seemed a little disposable" more like a twitter stream which I know it kind of is but at the same time it can be a very good source of info which makes me think old posts should be more "user findable" if that's not daft?
I agree tagging is probably the best solution, I might say perhaps I would move the tags to display below articles, and maybe in the form too but apart from that I think @ergonlogic your work so far is excellent!
What now?
I think perhaps there's opportunity to improve the user experience even further.
Edit: Tidied up a tiny bit, I was a little tired when I wrote it but then I am now, gotta love the irony!
P.S I was trying to be helpful honest, post sounds a bit "what I think" I didn't mean to I'm only a novice you folks are amazing grandmasters to me!
Comment #5
AquaticDisorder CreditAttribution: AquaticDisorder commented@ergonlogic
When tagging the old release notes with "release-notes".
I noticed the url of the page is being changed.
e.g
"http://community.aegirproject.org/1.5" became
"http://community.aegirproject.org/content/15-release-notes"
"http://community.aegirproject.org/1.4" became
"http://community.aegirproject.org/content/14-release-notes"
mig5 kindly repaired my damage but I guess it needs looking at a little still thx.
Comment #6
AquaticDisorder CreditAttribution: AquaticDisorder commentedReading these posts again I see in number 2:
"We could potentially extend this to the documentation too, but lets see how well received/used it is in discussions."
So I was tagging documentation (oops sorry!)
1. Should authenticated users have permission to tag the actual documentation then?
2. Should I only have used: Client, Developer, Hosted, Sysadmin
I think the talk tab on the documentation pages is really good btw, perhaps users could add their tags here.
Wow mig5 undid my handywork quicker than I tagged it, it's like I was never there!
Comment #7
AquaticDisorder CreditAttribution: AquaticDisorder commented@ergonlogic is there anyway you can remove the "release-notes" tag and just leave the "release" tag on this discussion post plz- http://community.aegirproject.org/discuss/16-released.
I think that was me but who's counting :)
Comment #8
Steven Jones CreditAttribution: Steven Jones commentedMoving out of the 7.x-2.x queue.
Comment #9
anarcat CreditAttribution: anarcat commentedmoving out of the patch queue. what else is needed here?
Comment #10
ergonlogicWe need to just drop the community site entirely, in favour or readthedocs.org and stackexchange, or the like.