Title: Proposal: Learn WordPress Content Maintenance Process Author: Destiny Kanno Published: May 29, 2024 Last modified: July 23, 2024 --- [ ](https://profiles.wordpress.org/piyopiyofox/) [Destiny Kanno](https://profiles.wordpress.org/piyopiyofox/) 11:34 pm _on_ May 29, 2024   # Proposal: Learn WordPress Content Maintenance Process In last week’s Training Team ([see Slack thread here](https://wordpress.slack.com/archives/C02RW657Q/p1716423202827589)) meeting we brought up the question of “**what content are we obligated to leave on learn and until what version of WordPress do we need to support”**. This question is a critical one as the team is currently working on relaunching Learn WordPress with a fresh new design and streamlined content experience which includes Learning Pathways, Courses, and Lessons. Part of this project includes content deprecation for Tutorials and Lesson Plans, and a push toward presenting content on the site that is new, fresh, and relevant. Here’s some takeaways from the discussion on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/): * Content that is not relevant to current coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. features of WordPress should be removed (ex. classic editor) * We could view the [WordPress version usage stats](https://wordpress.org/about/stats/) to decide what content is most relevant and should be the focus for our team. * We can use WordPress and PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php) usage metrics to guide our content maintenance process - More than 70% of WordPress installs are using either 6.5 or 6.4. - Historically the project maintainers have used 5% as the baseline, ie if more than 5% of WordPresses are using that version of PHP, then support it (this currently aligns with the above point). * The team should review content every 6-12 months for relevancy ## Proposed path forward * Adopt 5% baseline for content, which equates to supporting the last two versions of WordPress * Create a content maintenance review process that is run twice a year * Triage GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) for content issues which can be closed based on the new baseline ## Contribute to this conversation Here’s some questions to help keep the conversation going: * Do you agree with the proposed 5% baseline for content relevance? Why or why not? * Should there be exceptions to the 5% rule in certain circumstances? If so, what might those exceptions be? * What are your thoughts on the proposed bi-annual (twice a year) content review process? * How can we ensure that the content review process remains thorough and effective? * What strategies could we adopt to effectively communicate content deprecations to our learners? * What other metrics or data sources could be beneficial for informing our content maintenance process? **Please share your thoughts on this topic by June 13th, 2024** ### Share this: * [ Threads ](https://make.wordpress.org/training/2024/05/29/proposal-learn-wordpress-content-maintenance-process/?share=threads) * [ Mastodon ](https://make.wordpress.org/training/2024/05/29/proposal-learn-wordpress-content-maintenance-process/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/training/2024/05/29/proposal-learn-wordpress-content-maintenance-process/?share=bluesky) * [ Facebook ](https://make.wordpress.org/training/2024/05/29/proposal-learn-wordpress-content-maintenance-process/?share=facebook) * [ X ](https://make.wordpress.org/training/2024/05/29/proposal-learn-wordpress-content-maintenance-process/?share=x) * [ LinkedIn ](https://make.wordpress.org/training/2024/05/29/proposal-learn-wordpress-content-maintenance-process/?share=linkedin) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2024%2F05%2F29%2Fproposal-learn-wordpress-content-maintenance-process%2F%23respond&locale=en_US) 1. ![](https://secure.gravatar.com/avatar/5463e1794423dfcc9a1e56ab51c235c2c41f9519c8c147aea1724cdd363b7009? s=32&d=mm&r=g) 2. [Dan Soschin](https://profiles.wordpress.org/dansoschin/) 9:14 pm _on_ June 3, 2024 3. **Do you agree with the proposed 5% baseline for content relevance? While 5% is not a big number, I’m not sure it is necessary to remove content that is still relevant and factually accurate, even if it is dated. However, I think it could include a note if parts of it are out of date. If there is a minimal cost to hosting the content and it is being used, even by a few people, I think it’s useful. 4. **What are your thoughts on the proposed bi-annual (twice a year) content review process?** I believe it is very important that any content that is available is factually accurate. It will negatively impact perception, satisfaction, and adoption, if people access invalid content. So long as there are resources available to review content, twice a year seems reasonable to me. 5. **How can we ensure that the content review process remains thorough and effective?** Could there be a two-part process? Each piece of content is reviewed independently by two contributors and then if they both agree it should be removed, then so be it. If they disagree, a team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. or 3rd person and be the tie-breaker? 6. **What strategies could we adopt to effectively communicate content deprecations to our learners?** I like the idea of sharing the content depreciation process transparently on the Learn page and even making a note on each piece of content when it was last reviewed. 7. ![](https://secure.gravatar.com/avatar/360d5569069eaef664606ca04e691a5122cd451ede8ef85cac31d5d0c5be76e7? s=32&d=mm&r=g) 8. [Cynthia Norman](https://profiles.wordpress.org/cnormandigital/) 2:50 pm _on_ June 6, 2024 9. I don’t feel removing content will be necessary. Instead, I propose tagging content with metadata such as which minimum version of WordPress you need for it. 10. I also like using a deprecation process fits well with my way of thinking as it’s marked “older” but its relevancy could still exist for older sites. I like [@dansoschin](https://profiles.wordpress.org/dansoschin/) idea of deprecation transparency and a “last reviewed” note. All of this could be stored as metadata. 11. I think older content can remain with notes indicating what newer content learners could consider instead if their needs aren’t being met with the older content. Carefully considered metadata can also help with finding the desired content. 12. I believe the topic of relevancy is subjective as we all have different WordPress environments to work with. For me as a developer, I’m constantly needing help with taking over older sites and searching for content on how that site was built. For example, a site built using a classic theme and CMB2 pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost- based plugin from a third-party. used for metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes. 13. * ![](https://secure.gravatar.com/avatar/6b17e68ac4e17dfc7fbf67117de5241c4319f20ec294956dcb247034625cd3a1? s=32&d=mm&r=g) * [Destiny Kanno](https://profiles.wordpress.org/piyopiyofox/) 2:32 am _on_ June 11, 2024 * > For me as a developer, I’m constantly needing help with taking over older > sites and searching for content on how that site was built. * Very interesting point here! * Is this something you exclusively look for video content on (and does that currently exist on Learn?), or do the Codex, Documentation and Developer Handbook sites have this info? - ![](https://secure.gravatar.com/avatar/360d5569069eaef664606ca04e691a5122cd451ede8ef85cac31d5d0c5be76e7? s=32&d=mm&r=g) - [Cynthia Norman](https://profiles.wordpress.org/cnormandigital/) 11:06 am _on_ June 13, 2024 - I prefer to learn from video so I’m on YouTube a lot or I wind up on a forum such as stack overflow. With video, I like to know when it was created and try to match that up with when the site was built. 14. ![](https://secure.gravatar.com/avatar/e7b27b178ff5a141aa26976d2f17272a6483508f92d4fc6a210bcf8df560921f? s=32&d=mm&r=g) 15. [Courtney Robertson](https://profiles.wordpress.org/courane01/) 7:09 pm _on_ June 6, 2024 16. +make.wordpress.org/docs/ +make.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/](https://wordpress.org/)/ support/ 17. ![](https://secure.gravatar.com/avatar/e7b27b178ff5a141aa26976d2f17272a6483508f92d4fc6a210bcf8df560921f? s=32&d=mm&r=g) 18. [Courtney Robertson](https://profiles.wordpress.org/courane01/) 7:13 pm _on_ June 6, 2024 19. +make.wordpress.org/support/ +make.wordpress.org/polyglots/ 20. ![](https://secure.gravatar.com/avatar/2a8ae1349ffc717ca00609d1b256f69c12b39fc742c5a0242194a8b9112ddb7c? s=32&d=mm&r=g) 21. [Estela Rueda](https://profiles.wordpress.org/estelaris/) 7:21 pm _on_ June 6, 2024 22. Removing outdated content from the site is not necessarily a good idea. There are lots of sites that use the classic editor and still need access to that information, for instance. In docs, we add (deprecated) to the title or add a banner at the beginning of the article with a legend saying _“This feature works with version x.x”_ or something similar and, give a link for the article with the feature replacement, if it exists. A content review process should be in place, to update the lessons or any relevant information on the topic, but unless there is a way to know that a lesson/course is not being used, these should not be deleted. 23. ![](https://secure.gravatar.com/avatar/e7b27b178ff5a141aa26976d2f17272a6483508f92d4fc6a210bcf8df560921f? s=32&d=mm&r=g) 24. [Courtney Robertson](https://profiles.wordpress.org/courane01/) 8:03 pm _on_ June 6, 2024 25. I appreciate the effort put into rethinking the Learn WordPress content maintenance process, but I have some concerns. 26. 🚩 **Impact on SEO and Link Integrity** Removing content, even if outdated, can negatively impact SEO and create broken links for sites that reference our resources. This could harm the support and documentation teams significantly. For instance, [older content pages](https://drive.google.com/file/d/1V6vqxLdgfeLH-6mkyj0ECvWIkTA6Y6fv/view?usp=sharing) like “/lesson/how-to-log-in-with-wp-admin/” received 11,400 views with a 37.82% engagement rate, indicating their continued relevance. 27. 💡 **Alternative Approaches** 28. * **Deprecation Notices:** Instead of removing content, we could add a banner or note indicating the content is outdated but still available for those who need it. This approach aligns with how we handle deprecated features in documentation. * **Metadata Tagging:** TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. content with the WordPress version it applies to, helping users understand its relevance without removing it. High engagement rates for content like “/tutorials/” (86.79%) and “/lesson-plans/” (90.4%) show that users still find value in older content. 29. 🔄 **Content Review Frequency** A bi-annual review process is great, but let’s ensure it’s thorough. Perhaps a two-part review process where content is independently reviewed by two contributors and escalated to a team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. if there’s a disagreement. [Engagement data](https://drive.google.com/file/d/1V6vqxLdgfeLH-6mkyj0ECvWIkTA6Y6fv/view?usp=sharing), such as the 82.09% rate for “/tutorial/exploring-wordpress-6-5/”, supports the need for regular reviews to maintain high engagement. 30. 📣 **Communication Strategy** Transparency is key. We should clearly communicate any content deprecation on the Learn page and mark each piece of content with its last review date and relevant version tags. Courses like “/course/getting- started-with-wordpress-get-setup/” with a high engagement rate (69.86%) suggest that users respond well to clear communication. 31. 🌐 **Diverse Use Cases** Many users work with older versions of WordPress for various reasons. Removing content could leave them without crucial information. Keeping content with appropriate notes ensures we cater to a wider audience. The high engagement across different content types, such as “/lesson/introduction- to-wordpress-2/” with a 90.52% engagement rate, indicates varied user needs. 32. 🤖 **AI and Content AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia. org/wiki/Accessibility)** With the increasing use of AI for support and troubleshooting, it’s important to recognize that AI systems are likely to reference content from Learn.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/](https://wordpress.org/) directly to end users who may not even visit the site. These users might seek help from their host, theme, pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party., etc., and the AI will use the available content to provide solutions. Ensuring that this content is accurate and comprehensive, even if marked as deprecated, will maintain its utility in various support contexts. 33. 📜 **WordPress CodexWordPress Codex Living online manual to WordPress.org [https://codex.wordpress.org/](https://codex.wordpress.org/) and HelpHub References** It’s worth noting that the [WordPress Codex](https://codex.wordpress.org), while outdated, is still live and serves as a valuable resource for many users. Additionally, the kickoff of support docs “HelpHub” ([reference](https://make.wordpress.org/support/2015/01/kicking-off-helphub/)) shows that maintaining older content with proper context can still be beneficial. The [future plans for HelpHub](https://make.wordpress.org/docs/2023/02/07/future-plans-for-helphub/) include ideas around footer changelogs similar to the [Appearance Widgets Screen](https://wordpress.org/documentation/article/appearance-widgets-screen-classic-editor/). Conversations between Docs and Training teams have also been held previously to link our content closer at a per-blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. level. Docs is waiting for Training’s redesign to complete to start linking to our video content especially, ensuring the page links are well situated. 34. Thanks for considering these points. Looking forward to the ongoing conversation. 35. * ![](https://secure.gravatar.com/avatar/6b17e68ac4e17dfc7fbf67117de5241c4319f20ec294956dcb247034625cd3a1? s=32&d=mm&r=g) * [Destiny Kanno](https://profiles.wordpress.org/piyopiyofox/) 2:40 am _on_ June 11, 2024 * > The high engagement across different content types, such as “/lesson/introduction- > to-wordpress-2/” with a 90.52% engagement rate, indicates varied user needs. * This is part of the Beginner WordPress User learning pathway, so it would not be part of this deprecation conversation. * > It’s worth noting that the WordPress CodexWordPress Codex Living online manual > to WordPress.org [https://codex.wordpress.org/](https://codex.wordpress.org/) * I’m glad you brought this up. It looks like both the Codex and Documentation sites are hubs for information for older versions of WordPress that our users can access– also, we link to them on Learn. 36. ![](https://secure.gravatar.com/avatar/2a69844cfaf58d8e23da4a9a1a582b9767997e3a3ba77b201a2d45f304ac7ca8? s=32&d=mm&r=g) 37. [Jenni McKinnon](https://profiles.wordpress.org/ninianepress/) 8:58 pm _on_ June 6, 2024 38. Thanks for the proposal. I agree with everything that has been said in the comments so far. Here are some more thoughts that I have on this that may be worth considering: 39. > Do you agree with the proposed 5% baseline for content relevance? Why or why > not? Should there be exceptions to the 5% rule in certain circumstances? If > so, what might those exceptions be? What strategies could we adopt to effectively > communicate content deprecations to our learners? 40. I think this is great. Backwards compatibility has been a consistent process that’s still important and keeping content that’s still used is in line with that. I don’t think that we need to delete old content from previous releases. Not only could it still be important for some users, but I think having historical context is crucial for future contributors even decades from now. If WordPress survives all of us, it would be even more critical for future contributors to have something to draw from, especially if there are less and less people who have the historical context for past features as time marches onward. 41. There are release notes and changelogs, but they don’t explain things as in depth as Learn content and it could very much help future contributors make informed decisions. 42. I don’t think we should delete content, but instead have a process for noting which releases (in a range) so people know when the feature rolled out and when it was deprecated. Tags, links to updates and the other suggestions commented are all great options. Re-categorizing could also help. 43. > What are your thoughts on the proposed bi-annual (twice a year) content review > process? How can we ensure that the content review process remains thorough > and effective? 44. I think content reviews could benefit from a similar process that the Docs Team has: We have release project boards in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) where we track updates on an ongoing basis. 45. A bi-annual content reviews will require an exorbitant amount of work to organize and finish in a timely manner. Given that documentation articles and updates don’t ever get finished in time for a release, I don’t know how practical it would be to organize a sprint for what could potentially be mountains of work. 46. I also think the Docs and Training Teams should work very closely for content as well as updates since they’re so heavily related. As such, I think we should aim for these teams to be heavily interconnected. 47. > What other metrics or data sources could be beneficial for informing our content > maintenance process? 48. Taking another look at other open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects who have regularly updated and maintained documentation or similar could be helpful. Maybe even looking at the process that some companies use like LinkedIn Learning may also be useful. 49. I’ll have to think about this question some more. 50. * ![](https://secure.gravatar.com/avatar/e7b27b178ff5a141aa26976d2f17272a6483508f92d4fc6a210bcf8df560921f? s=32&d=mm&r=g) * [Courtney Robertson](https://profiles.wordpress.org/courane01/) 9:03 pm _on_ June 6, 2024 * I would love to see the Training team resume the work that fell off last release, ensuring that all is logged the way Docs does. I am quite happy to mentor contributors to assist with this. [Training and Docs have long worked together](https://wordpress.tv/2022/03/30/milana-cap-birgit-pauli-haack-courtney-engle-robertson-femy-praseeth-akira-tachibana-wordpress-release-6-0-trac-ticket-triage-for-docs/) on how we approach releases, but it seems to need a refresh. 51. ![](https://secure.gravatar.com/avatar/e2f5cdfaa31c9d539c55861f832b36b07fbfbf98fbbf5075042d136331e81a42? s=32&d=mm&r=g) 52. [Jono Alderson](https://profiles.wordpress.org/jonoaldersonwp/) 1:25 pm _on_ June 9, 2024 53. Worth noting that there’s a middle ground before we reach “delete”, where we could tactically (or automatically) _noindex_ pages that don’t meet a relevancy or currentness threshold. 54. That’ll prevent them from showing up in Google etc, and _should_ also prevent them from showing up in on-site search mechanisms. 55. Then they’re addressable via direct links, but not otherwise discoverable. 56. That’ll also mean that we don’t need to consider the (considerable) overhead of configuring and managing 301 redirects for deleted content (without having, say, a handy SEO pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. in place to manage this), as well as updating all of the content that links to those pages… 57. ![](https://secure.gravatar.com/avatar/af98b4302728984cfc6255c7f94f7d6ba10e51787f68c0842d15d2005b57db57? s=32&d=mm&r=g) 58. [Benjamin Evans](https://profiles.wordpress.org/kaitohm/) 9:31 am _on_ June 10, 2024 59. As another point to consider, I calculated how much content Learn currently hosts. As of this comment, **Learn has around 166 hours of content. **(See details below.) To put into perspective, if 10 contributors dedicated 3 hours a week to review published content, it would take them 6 weeks just to consume all content without considering any time to consider feedback or apply updates. 60. The amount of content Learn produces will only continue to grow, so a comprehensive review process that looks at all content at certain intervals is not realistic. The team will need to identify what the most impactful content is and build a maintenance process around that limited subset of content. 61. _For reference, below is how I calculated the total amount of content._ 62. * There are 157 Tutorials on YouTube. The total watch time is 32 hours and 43 minutes. * There are 102 Tutorials that are not on YouTube. If the average length was the same as those on YouTube, the total watch time would be 21 hours and 15 minutes. * There are 122 Learning Pathway videos on YouTube. The total watch time is 13 hours and 10 minutes. * There are 151 published Lessons Plans. Based on a random sampling of 3 lesson plans, the total time to read through this would be 38 hours and 30 minutes. * There are 570 lessons on Learn. Based on a random sampling of 3 lessons, the total time to read through this would be 60 hours and 9 minutes. 63. ![](https://secure.gravatar.com/avatar/6b17e68ac4e17dfc7fbf67117de5241c4319f20ec294956dcb247034625cd3a1? s=32&d=mm&r=g) 64. [Destiny Kanno](https://profiles.wordpress.org/piyopiyofox/) 3:10 am _on_ June 11, 2024 65. Thank you so much to everyone who has commented on this so far! I’m taking a stab at summarizing most of the feedback gathered so far in this conversation and proposing some potential next steps based on what has been shared to help further this discussion. 66. ## Ideas proposed 67. Utilize metadata tagging and a “last reviewed” note 68. Two independent content reviews, with a third to break any ties 69. Share our content deprecation process Transparently on Learn WordPress 70. Docs and the Training Team could work more closely around content review 71. The team will need to identify what the most impactful content is and build a maintenance process around that limited subset of content. 72. ## Considerations 73. Content review and maintenance for out of date content (as defined by out threshold) is time consuming for contributors and takes away from more relevant and up to date content creation. 74. The overhead of configuring and managing 301 redirects for deleted content (without having, say, a handy SEO pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. in place to manage this), as well as updating all of the content that links to those pages. 75. Any content that is available should be factually accurate; otherwise it will negatively impact perception, satisfaction, and adoption, if people access invalid content. 76. The [WordPress Codex](https://codex.wordpress.org/), [Documentation](https://wordpress.org/documentation/), and [Developer handbook](https://developer.wordpress.org/) sites offer information on older versions of WordPress 77. There’s a middle ground before we reach “delete”, where we could tactically (or automatically) noindex pages that don’t meet a relevancy or currentness threshold. This will prevent them from showing up in Google etc, and should also prevent them from showing up in on-site search mechanisms. 78. Learn WordPress currently has around 166 hours of content, and this will only continue to grow. It’s neither feasible nor sustainable to give our ever-growing out of date content the same weight as more up to date and relevant content. 79. ## Potential next steps 80. This conversation is still ongoing, but I’d like to share some potential next steps now based on everyone’s feedback so far, and invite others to give their input on what I’ve gathered below: 81. Develop the deprecation/out of date evaluation framework Create a data-driven framework and review checklist for content deprecation inclusive of: — Reviewing the view stats of video content marked for deprecation (Ex. If we are seeing low viewership for certain out of date content, then we deem it safe to deprecate)— Reviewing the view stats of Lesson Plans — Have a two review process, with a third review to “tie break” as needed — Research what other modern learning websites( even for certain products) leave deprecated/out of date content up on their Learning sites and how do they maintain that content? 82. * Set up bi-annual review cycle 83. Ensure the Training Team (and other Make teams) has a shared understanding of what Learn WordPress’s content commitments are — For example, we have the [WordPress Codex](https://codex.wordpress.org/), [Documentation](https://wordpress.org/documentation/), and [Developer handbook](https://developer.wordpress.org/) sites which contain plenty of out of date content for those not on the most recent versions of WordPress. Do we really feel it’s necessary to duplicate this content further on Learn WordPress? — Is Learn WordPress the site where folks come to about the most relevant and up to date content on WordPress? Is it the place where we encourage and guide folks to be at the forefront of the software? 84. ![](https://secure.gravatar.com/avatar/32a72213be1308473f692b1dccfc44607bd88f11ea92f3ceaefef4b91f1fe4b3? s=32&d=mm&r=g) 85. [Adam Wood](https://profiles.wordpress.org/adamwood/) 9:24 pm _on_ June 11, 2024 86. Worth noting that all our post types (Lesson Plans, Courses, Lessons and Tutorials) have the WP Version metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. field, so we can already tag this content. 87. Re the new design/build: 1. The new designs don’t display this WP Version information at the moment. 2. I don’t think there is a need to delete content. For the deprecated post types we’re ensuring that there are functioning archive and single templates for these, so even though tutorials and lesson plans won’t be available via the navigation they will still be reachable, and it sounds like this is good from an SEO stand point. Please let us know if we need to noindex them as well. 88. * ![](https://secure.gravatar.com/avatar/6b17e68ac4e17dfc7fbf67117de5241c4319f20ec294956dcb247034625cd3a1? s=32&d=mm&r=g) * [Destiny Kanno](https://profiles.wordpress.org/piyopiyofox/) 5:49 am _on_ June 28, 2024 * > Please let us know if we need to noindex them as well. * [@adamwood](https://profiles.wordpress.org/adamwood/) Let’s move forward to noindex them. 89. ![](https://secure.gravatar.com/avatar/8c89447051442fa67f733cd23f299ed361f51e5129ee4b00a1f5d83fc2178a09? s=32&d=mm&r=g) 90. [Milana Cap](https://profiles.wordpress.org/milana_cap/) 8:10 am _on_ June 18, 2024 91. If there’s a tutorial/lesson/course/etc. relevant for a specific WordPress version, then it can not be outdated, as long as that WordPress version is available for download. At Docs, we WANT to have documentation for different versions but technically it is not possible at the moment. Unless that WordPress version is significantly changed, all the content that addresses it is NOT deprecated but rather relevant. And you do not need to update/maintain it, unless there’s a significant change in that version (which will not happen). 92. Please, do not remove that content completely. Maybe in the future we’ll have a proper place and architecture to let that content coexist with contemporary one, which should be a goal for such important CMS. Until then, hide it somewhere if it’s making confusion, but please, don’t delete it. Thank you :heart: 93. ![](https://secure.gravatar.com/avatar/6b17e68ac4e17dfc7fbf67117de5241c4319f20ec294956dcb247034625cd3a1? s=32&d=mm&r=g) 94. [Destiny Kanno](https://profiles.wordpress.org/piyopiyofox/) 5:53 am _on_ June 28, 2024 95. Thank you for your feedback everyone! I have created [Project Thread: Content Maintenance Process Update Phase 1](https://make.wordpress.org/training/2024/06/28/project-thread-content-maintenance-process-update-phase-1/) where we can continue shaping this process together. ### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/training/2024/05/29/proposal-learn-wordpress-content-maintenance-process/?output_format=md#respond)󠁿 You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2024%2F05%2F29%2Fproposal-learn-wordpress-content-maintenance-process%2F&locale=en_US) to post a comment. This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/) # Post navigation [← Training Team Meeting Recap – 23rd May 2024](https://make.wordpress.org/training/2024/05/29/training-team-meeting-recap-23rd-may-2024/) [Meet 2024 Interim Co-Rep: Jamie Madden →](https://make.wordpress.org/training/2024/06/04/meet-2024-interim-co-rep-jamie-madden/)