These are thoughts/ideas about potential tasks to implement for the community in 2020. The intent is to use this discussion to brainstorm ideas. I will then organize the ideas. In review meetings, we can begin to further refine the ideas and start to create actionable items which can then be put into Jira and implemented.
These ideas are in no particular order:
- Include "Start a Discussion" on article pages
- Re-organize article buttons (reply, quick reply, kudos, solution). By this, I think they should be organized along a single line
- The white space does not always work for me in terms separating content. I like how the SAS community uses lines to delineate sections.
- Search box on every page.
- Labels. Need to start incorporating labels and using those to find information. Re-do the work that was done previously to categorize messages. Maybe determine a way to automate that categorization? Would like to only use pre-defined labels across the site. Possible re-organization of categories? For example, one JMP Discovery Summit then use labels for years, location, topics, etc. to group data? When searching, you could search one knowledge base rather than several.
- Gamification. Use success points with Khoros for a gamification review. See Ranks and Badges for ideas on making the community aware of the possibilities.
- JMP Wish List. Determine improvements in the current process.
- Newsletter. Rather than have sections based on the community structure, have the sections more topic based, i.e. data table, scripting, etc.
- Analytics. Continue to gain a better understanding of the "health" of the community. When researching any items listed here, develop a set of graphs/stats so that we can discover areas of improvement.
- UI, add more structure and make that structure relatively consistent across the pages. I think the basic framework exists but might not be consistent everywhere. For example, for an article, have the article on the left then maybe a "properties" panel on the right. In this panel is where you could subscribe, get author information, etc.
- Information is a key goal for 2020. How do we make it easier for users to find the information they need. Also, it would be nice to expose them to new areas of interest as well that could be explored. Three ways of finding: search, browse by topic, "random" browsing.
- Groups. What can be done to encourage more participation in groups? Move to new Group Hub concept developed by Khoros.
- Post release notes in About the Community section. There are all types of changes: bug fixes, UI, back-end, etc. Maybe post release notes once a quarter that details the changes? I like the idea of transparency. Pushes would occur at the end of the sprint but we do not need to push at the end of every sprint.
- What can be done to improve SEO?
- Starting taking a closer look at Google Tag Manager results. What other data do we need to collect?
- Develop a continuous integration pipeline for the Community SDK and analytics
- Implement a testing suite for the SDK and scheduled tasks
- Develop a dashboard to show the overall health of the Community
- For development workflow, start using pull requests and have tester push code to master.
- Start pointing stories. More backlog grooming to gain a better understanding of the work that is involved.
- Spend time investigating accepted solutions vs. topics.
- Add the ability to navigate between articles. Currently, you need to view the list, click an item in the list, read the article, then go back to view the list to get to the next article.
