oops-wp
oops-wp copied to clipboard
A collection of abstract classes, interfaces, and traits to promote object-oriented programming practices in WordPress.
`PostType` objects do not currently throw an exception if a `$slug` property is not defined, which can be confusing to developers when trying to extend the `PostType` class. The `Taxonomy`...
The WordPress plugin editor must be enabled on custom post types by setting `show_in_rest` to true when registering the post type. We should considering setting this as a default value,...
We seem to have two types of interfaces, the Utility interfaces e.g. - [Hookable](https://github.com/WebDevStudios/oops-wp/blob/master/src/Utility/Hookable.php) - [Renderable](https://github.com/WebDevStudios/oops-wp/blob/master/src/Utility/Renderable.php) and those that refer to abstract classes. e.g. - [PluginInterface](https://github.com/WebDevStudios/oops-wp/blob/master/src/Structure/Plugin/PluginInterface.php) (implemented by abstract class...
We're looking to establish an abstract class that provides an interface for quickly defining and registering a custom metabox with WordPress.
The [EditorBlock structure](https://github.com/WebDevStudios/oops-wp/blob/master/src/Structure/Editor/EditorBlock.php) was developed as an initial attempt to capture the basics of what's needed to register a custom block for the WordPress editor. Unfortunately, in its current state,...
During an internal OOPS-WP/Gutenberg call this morning as part of 5 for the Future, we discussed the use case for providing style modifications to native Gutenberg blocks, both within the...