devhub update

Long meeting today in devhub land! Here’s what was discussion:

• WP-Parser: methods need to be broken up into CPTs
• WP-Parser: amendments need to be made to how inline docs are parsed into the_content
• we discussed editing of content in the code reference in the WordPress Admin. We agreed that only admins should be able to edit the content and only in extenuating circumstances. @siobhan to open the following tickets:
  • that the_content be locked for code reference post types to admins only 411
  • that an internal flag system be added so that we can keep track of things that have been edited (with a view to the docs team ensuring that all inline docs patches are updated prior to a WP update 412
• we agreed that the theme and 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/ or can be cost-based plugin from a third-party. dev handbooks should stay as CPTs, and that @nlarnold1 is free to do as she chooses with the handbook plugin
• I made a list of proposed templates for the theme, but @nlarold1 has been using template parts and gave me an excellent lesson on how they work. Nicole to edit and update the google doc
• We discussed changing the prefix for the CPTs generated by WP-Parser. Currently it’s wpapi which will potentially be used by a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins and it would be nice to keep them separate.

#devhub