Title: Learn WordPress Version Taxonomy Author: Courtney Robertson Published: January 7, 2022 --- [ ](https://profiles.wordpress.org/courane01/) [Courtney Robertson](https://profiles.wordpress.org/courane01/) 2:27 pm _on_ January 7, 2022   # Learn WordPress Version Taxonomy In [Learn WordPress](https://learn.wordpress.org), there is a taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies). based upon WordPress versions used internally for auditing content. [[ Originally, this was used as a means of comparing or auditing content to ensure it includes any information about the latest versions. It is a checkpoint to indicate we have recently reviewed this content. We now have several goals with this taxonomy: 1. This content has been confirmed with the corresponding release version. At this time, this is an internal use-case, but we could envision using this publicly in a changelog at the bottom of lesson plans, workshops, courses to view content from previous versions. 2. This content is contains new or important features about the latest release. This is public-facing and can help curate [a page of relevant content](https://github.com/WordPress/learn/issues/295) per release on Learn. The taxonomy created is now publicly accessible: [https://github.com/WordPress/learn/pull/292](https://github.com/WordPress/learn/pull/292). However, this may be quite cluttered with content comparison checks and not exclusive to features related to the current release. [⌊Learn WordPress lesson plan landing page highlighting the WordPress version filter located in the sidebar⌉⌊Learn WordPress lesson plan landing page highlighting the WordPress version filter located in the sidebar⌉[ Learn WordPress lesson plan landing page Thoughts to consider: * Should these live in 1 taxonomy area or should these live in 2 separate taxonomies? * How do we envision using that in the admin area? * How do we need data to publicly display now, and in the future? * What additional considerations should we have? We’ll leave this post open until January 14 before progressing to 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/) Issues. ### Share this: * [ Threads ](https://make.wordpress.org/training/2022/01/07/learn-wordpress-version-taxonomy/?share=threads) * [ Mastodon ](https://make.wordpress.org/training/2022/01/07/learn-wordpress-version-taxonomy/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/training/2022/01/07/learn-wordpress-version-taxonomy/?share=bluesky) * [ Facebook ](https://make.wordpress.org/training/2022/01/07/learn-wordpress-version-taxonomy/?share=facebook) * [ X ](https://make.wordpress.org/training/2022/01/07/learn-wordpress-version-taxonomy/?share=x) * [ LinkedIn ](https://make.wordpress.org/training/2022/01/07/learn-wordpress-version-taxonomy/?share=linkedin) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2022%2F01%2F07%2Flearn-wordpress-version-taxonomy%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/) 4:33 pm _on_ January 7, 2022 3. Something to think about would how to “uncheck” assets that are tagged for the current release when a new release comes out. 4. I love the idea of tagging each asset to denote which release(s) it is relevant for. 5. I’d probably recommend showing the release numbers in descending order, not ascending… as I believe the typical user will be looking for current new/current/content features. 6. Perhaps there’s a version/tag that is just “new” which denotes that the asset is for a new feature or release… and then that tag can easily be removed somehow when a new release comes out and it is no longer “new”. 7. * ![](https://secure.gravatar.com/avatar/eb8a100b34072d5a5ba15cb247f8f55f56cf228b60e71d74303a4e6f6a0b081d? s=32&d=mm&r=g) * [Hauwa Abashiya](https://profiles.wordpress.org/azhiyadev/) 3:26 pm _on_ January 25, 2022 * We don’t have a tag for new but we do have a way to make changes to the content and schedule the updates to coincide with a release. I can see the benefits of having a “new” tag though. I wonder if we could also use a featured section to convey what’s new. 8. ![](https://secure.gravatar.com/avatar/eb8a100b34072d5a5ba15cb247f8f55f56cf228b60e71d74303a4e6f6a0b081d? s=32&d=mm&r=g) 9. [Hauwa Abashiya](https://profiles.wordpress.org/azhiyadev/) 3:23 pm _on_ January 25, 2022 10. At present, the taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies). is only captured against Lesson Plans and Workshops. As our course catalogue grows we will need to identify what courses might need to be updated, having this against a course will help. 11. > Should these live in 1 taxonomy area or should these live in 2 separate taxonomies? 12. I think we should have 1 taxonomy that displays (at most) 3 version numbers on the front end. With [@dansoschin](https://profiles.wordpress.org/dansoschin/) idea about showing the release numbers in descending order. 13. > How do we envision using that in the admin area? 14. This is where I think having 2 taxonomies might help. One to indicate what version of WordPress was used to create the content and then another one to state “This applies to ” other versions of WordPress. I’m assuming that we will be using the latest version to create new content but unless it is a completely new feature, that content can be used for older versions of WordPress. New users will automatically navigate to the latest version but there might be existing users who for one reason or another need to stay on an older version. I don’t mean as old as 5.0 but within 3-5 versions. I think [@hlashbrooke](https://profiles.wordpress.org/hlashbrooke/) also suggested having no more than 5 on the landing page. 15. > How do we need data to publicly display now, and in the future? 16. This is where I like the idea of a changelog. The learner or facilitator can click on it to read more about changes made and the different versions of WordPress that it can be used for. 17. > What additional considerations should we have? 18. We should look at the findings of the UXUX UX is an acronym for User Experience- the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. audit and any additional audits we run to inform the decisions we make about what to include here. ### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/training/2022/01/07/learn-wordpress-version-taxonomy/?output_format=md#respond)󠁿 You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2022%2F01%2F07%2Flearn-wordpress-version-taxonomy%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 [← Social Learning Spaces Streaming Platforms](https://make.wordpress.org/training/2022/01/07/social-learning-spaces-streaming-platforms/) [Training Team Meeting Agenda January 11, 2022 →](https://make.wordpress.org/training/2022/01/11/training-team-meeting-agenda-january-10-2022/)