This mod provides several commands centered around managing the WP Bones WordPress plugin framework. It provides quite a few commands for varying uses, so there should be something for everyone! Take a look at the scenarios below to get a feel for how you might use the extension.
WP Bones is a lightweight framework that offers tools and guidelines to simplify WordPress plugin development. Bones aims to allow you to write plugins in a manner similar to developing a Laravel Framework application.
Sadly, WordPress architecture doesn’t currently support composer/vendor philosophy yet. This is why some amazing features of composer/vendor architecture can’t apply yet.
Also, see Before submit to WordPress repository section for more coding restrictions information.
The aim of this framework is to use both new and standard development tools in a WordPress environment. If you like Composer, npm, Laravel and Gulp, here is the framework for you.
If you know Laravel Framework, you will love WP Bones Framework too. I was inspired by Laravel while developing WP Bones. Even though, as you can imagine, the WordPress environment doesn’t support Composer as we wished. So, you will find a lot of things similar to Laravel and some others very different.
Developed by Undolog.
I am open to requests for features, bug reports, and edits to the code made by the community.
Distributed under the MIT License.
See your WP Bones status at a glance
You can access the documentation and filter by search keys, then view the results in a browser.
Allows you to select the GitHub WP Bones template that suits your needs, so you can create your scaffolding in just a few seconds.
Ask a question about WP Bones and get an AI-powered answer based on the documentation.
View the latest WP Bones release notes.
Color.PrimaryText and follow the current appearanceloading.svg, which is not in assets — the regular logo stays visible, and isLoading already shows the spinner@raycast/api 2.x and @raycast/utils 2.x⌘⇧P: ⌘P is reserved by Raycast and was being ignoredENOSPC) so the command no longer crashes when the Raycast cache journal can't be writtennull/non-object/missing items array)1.10.0 vs 1.7.0)useEffect priority chain — error state no longer gets overwritten by other statesuseStreamJSON with useFetch in search documentation for more reliable resultstemplates.ts and use-wp-bones-template.tsxuseVersion() hooks with comprehensive error handling mechanismsuseBoilerplates()API fetch to retrieve boilerplate list with comprehensive error handling and fallback mechanismuse command to create for improved clarity and semantic precisionpackage.json removes owner