Discussion: where do we publish and store research results?

The research group has a report ready to share as part of the sitebuilding research. Since it’s quite long, the group would like to choose the best place to publish it.

This report should be stored with other research results in the future, since these are likely to build upon and enhance one another. It’s best if these resources are easy to find and access. They should be something that everyone contributing to WordPress can refer back to in coming months and years.

This was discussed in Slack, but let’s open the conversation to more people.

Where should this type of content live?

In a series of posts on make/design
On a static page on make/design, announced with a post on make/design
In a static Google document linked to make/design post
Somewhere else?

This research is ready to publish, so please share your preference by leaving a comment on this post no later than Thursday, 31 January 2019. Thank you!

#gutenberg, #research

Mel Choyce 6:04 pm on January 29, 2019

Ideally, I think it should live somewhere within the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ ecosystem — whether that’s a page here, or on +make.wordpress.org/test. A series of posts would be nice for digesting the data, but I feel like either the entire report, or a link to each post, should live on a research page.
Mark Uraine 6:20 am on January 30, 2019

Multiple posts on make/design is a good call if the individual posts can reflect the ways in which the data or users were segmented. But I do agree that an overview page would be nice to give a high level view and link off to individual, more detailed, posts.
sarah semark 10:47 am on January 30, 2019

To add some additional context here, it would be good if we could have a place where all research resources live into the future. Ideally this would be something that we could scale to include the research resources, links to outside sources, as well as results of future studies.

The research resources currently include some legal boilerplate, guides for moderators, note-takers, and debriefing, a research plan checklist, and a research plan template. As more studies and usability tests are completed, I expect these resources to grow. A centralised place to store them within wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, even if it’s just a single page that links to posts, would be lovely, so that they’re within easier reach of anyone who’d like to use them.
Tammie Lister 7:21 pm on January 30, 2019

I would suggest going the simple route and a series of blog posts right now. Then we can work where it goes in the longer term, get the benefit of all the great research as soon as possible.

I do worry about a separate site both having a lot of work to do and also be ‘yet another place’ to go to, possibly easy to forget. My only other strong opinion on this is that I feel it shouldn’t just belong to design, or to that point a specific team, it’s valuable data for the entire project.