How to label, aggregate and expose issues, docs, forum posts and groups to Topic pages

Do we have any numbers/statistics on how much content we have to allocate a topic to?

Edit: Deleted my question...

subscribe and tags

there are new mockups available at http://groups.drupal.org/node/144584#comment-592174

i think taxonomy terms would be a good way to reference what a topic is interested in and to list the according issues.
still have to figure out which contents we could not reference using this approach

rara img tag

Only got five votes here, but it's an interesting idea https://groups.drupal.org/node/312903

Hopefully we find a way to make it a priority to try to gather together that knowledge rather than having it spread across individual issues.

changing issue summary input format to filtered html, so people can comment and edit. doesn't seem to be that much custom html needed anyway. (Related: #2210789: Allow comments on issues even if user does not have permission for the issue summary text format)

downloaded g.d.o image, then uploaded again and embedded.

Thanks YesCT (and @drumm)!

I wanted to reference Leisa Reichelt's writings about the Prairie Initiative where she wrote in her blog:

Topic page – a place where activity from across the Drupal network can be aggregated and people interested in this topic can ‘follow’ the topic. This allows people to self identify their expertise, people to find likeminded peers in the community, people to find mentors, people can more easily keep up with activity on Drupal.org related to their topic.

And also from her notable page on the issue queues:

Leisa: @lisarex - we could explore doing something quora-ish (seriously, I'm not on commission and there is plenty I *don't* like about it too!) - take a look at the Manage and Organise topic pages eg http://www.quora.com/Drupal-CMS/organize

and:

Leisa: I think this is a mixture of two things: 1. paving the cowpaths re: pinging the usual suspects on the topic at hand, but also 2. an opportunity to let people who might be 'watching' for an opportunity to make a small initial contribution to step up. I think it's important that we start thinking more about the quality of the response rather than the immediacy - we're used to just jumping onto IRC all excited and trying to get someone to jump on it immediately, I'd like to see less frenzy and a little more calm around the process of gathering the right set of people into the space to have the discussion rather than just pinging the person who is always available.

and:

eisa: So, people naturally want a way to be able to support ideas that they think are good/best ideas. If someone has already totally nailed a solution, sometimes all I want to do is say - in my expert opinion, I concur. That information is valuable to a community who is deciding on a direction to take not only how many votes but also who votes for it (I'm glad you raised this tho because I hadn't made the point that on Quora at least, and possibly also on StackOverflow?, different people have different 'weight' and a vote from someone who has runs on the board relevant to the topic (tags) or phase (eg. design vs coding vs documenting) would carry different weight than someone with less or less relevant recognised experience. I agree that chronological is definitely the best way to show how issues have evolved over time. The problem we are trying to solve is to make the process more efficient - the longer an issue runs, the more difficult it is to stay focussed and for new people to quickly grok what discussions have happened and where we're at with them. The detailed discussion about what is good/bad/indifferent about an idea can still happen - that would happen in the comments for each 'big idea'. It is different, i know.... I suspect it might be better in some ways and more challenging in others.

I think these are good ideas to bring into this discussion on d.o and hope it helps move this forward.

I don't have direct experience of Quora's Topic pages, but it is probably a good model still.

This issues has been kicking around in the back of my mind for a few weeks.

I think the idea of creating topic pages off tags probably makes sense, since these already exists on issues. Problem is, anyone can tag any issue "user experience" and that culd be an issue related to core, a contrib module, docs, d.o, anything, and it usually translates to "make it less bad for people to use".

General tags are going to create topic pages with a lot of content that isn't really related. If I look at this list, I am not really sure what these issues really have in common, other than a tag. If the idea is to appeal to newcomers, then having a bit of clarity is needed.
https://www.drupal.org/project/issues/search?issue_tags=user%20experience

Commerce and Git tags aren't great either. Marketing & Security aren't too bad.

Suggestions to discuss

• Most topic pages are specific to Core or Contrib. We need a place for the Drupal project as a whole (marketing, drupal.org, documentation)
• Topic pages are formed from two tags, or maybe tag + project (e.g Project: Drupal Core, Version: 8.x + tag: user experience = Drupal 8 User Experience)
• Having parent & child as well as 'related' topics is too much to manage manually. What happens when a lesser topic becomes a bigger thing? Or are we thinking of letting technology decide what topics are related?
• Put more emphasis on people. the mockups shown don't show who the mentors are, just who is most active (which isn't necessarily a good measure of knowledge/expertise)

Mockup to follow

Could we have some auto-aggregation but also rely on curators of certain topics to ensure that the right information gets brought up to the top?

Looking forward to seeing the mockups!

Highlighting people, particularly with official roles is good.

Topic pages should be formed when there's a good reason to do so. If there's enough interest in 8.x + UX then great. But there are already thousands of Tags. I think we should start with a few big topics and then branch out.

Here’s all my annotations/notes for the mockup. I'll do one for the main topic page next.

1. Topic home page and subpages sit within Community, and appear before Getting Started.
2. The topic page is a content type. The summary is editable by whoever has permission to edit the topic (suggest it’s a somewhat trusted role: documentation or the like)
3. Important links section is a place to manually attach/link nodes, such as the main page for the related group, an external link, another sub site on Drupal.org, etc. I suggest we give them the ability to create a link title that’s shown, rather than the URL.
4. People is the real purpose of this section. User avatars, full name, username, and self-selected role label (newbie, mentor, etc) should appear here. These are updated on the user profile page (issue TBD). The username links to the user’s profile page.
5. Some people would like to find a mentor. This would take user to a page with filtered to users of just mentors in this topic.
6. View people would take user to a page with filtered to users in this topic, but with the option to further filter by role.
7. Follow/following would work like it does with issues.
8. Topics would have a manually-set status. Active, minimal, archived (i.e. Drupal 6 UX should be archived :)), etc. We can determine if these are useful and what they should be.
9. Stats around the topic. These would be automatically generated.
10. Related topics, manually created. Suggest we stick with related, and not try to fuss with parent/child relationships.
11. Recent activity is all new and updated content that is tagged with the designated tags for the topic, or content from related groups (i.e. ALL content from the Usability group should appear here, probably, right? We can’t always rely on people to remember to tag things). This would also include people updates.

Thoughts?

Also... This page is pretty text heavy. Being able to (optionally) set an image might be nice... thoughts?

tagging. being referenced in LA talk https://events.drupal.org/losangeles2015/sessions/drupalorg-changes-supp...