Resolved Posts plugin activated & widgets added; Learn Roadmap Proposal


Over the last two weeks, I’ve been working with the Meta team on the preferred way to collect and track non-technical roadmap or wishlist items for the the Learn WordPress initiative. I had initially proposed adding these as issues in the Learn GitHub repository. Concern was raised that we shouldn’t ask non-technical users to make a GitHub account or learn how to use GitHub to be able to comment or contribute ideas. We talked though several options before arriving on the solution I’m sharing with you today.

The Resolved Posts plugin has been installed on this site. The plugin adds a button at the bottom of each published post (when viewing on the front of the site) which toggles through three states: no value, to do (unresolved), and done (resolved). Unresolved posts have a red stripe on the left down the length of the post. Once resolved, the stripe will be green.

The 5 oldest unresolved posts will appear in a new Unresolved widget in the sidebar of this site. I’ve gone through all of the posts on this site and cleared the unresolved flag from posts that were informational or very old. I’ve commented on the four remaining posts that were unresolved asking for feedback to see if they should remain unresolved.

For the Learn WordPress roadmap items, each items should be created as a post on this site and include the #learn-roadmap tag. After publishing the post, mark it as a To Do. When viewing the #learn-roadmap tag page, a widget can be seen in the sidebar showing unresolved #learn-roadmap posts. This widget will also appear when viewing any post with this the #learn-roadmap tag. Going forward, I suggest we adopt the following:

  • if consensus to proceed with the idea is reached, an issue should be opened on the GitHub repository and a top comment be added with a link to the issue
  • once the GitHub issue is complete, the roadmap post can be marked resolved.

Please comment below if there is a better way to transition from roadmap post to GitHub issue for the developers to work on. I’ll leave this open for input until October 2, 2020.