After years of shipping with Gulp, run-s, and a patchwork of per-plugin build scripts, WPBones v2 collapses all of it into a single webpack-based pipeline. Every plugin built with WPBones now uses the same yarn dev/build/test/format/lint commands, the same webpack config, the same TypeScript + Jest + Prettier defaults. And to make the jump painless, v2 ships with php bones migrate:to-v2 — a one-command automated migrator that rewrites your plugin in place.

This is the biggest breaking change in the framework’s history, and we made the migration path as short as we could. If you’ve been putting off modernizing your WPBones plugin, this weekend is a good weekend.

What’s New in v2

✨ One webpack config, zero boilerplate

The old v1.x pipeline was a stack of gulp tasks orchestrated by run-s: one script to compile SCSS, another to bundle JS, a third to transpile TypeScript, a fourth to build React apps, a fifth to copy things. Every boilerplate had its own variation, and every plugin drifted.

v2 replaces all of it with a single webpack.config.js that auto-discovers entries from resources/assets/:

• Drop a file in resources/assets/apps/<name>.tsx → builds to public/apps/<name>.js

• Drop a folder at resources/assets/apps/<name>/index.tsx → same thing

• Drop CSS/SCSS/LESS in resources/assets/css/ → compiles to public/css/<name>.css

• Drop TS/JS in resources/assets/js/ → compiles to public/js/<name>.js

No more editing gulpfile.js to register a new entry. No more run-s coordination. Just save the file and webpack picks it up.

✨ Unified yarn scripts across every plugin

Every plugin built on WPBones v2 — from the leanest Base boilerplate to the full Mantine UI demo — now responds to the same five commands:

yarn dev       # watch mode (webpack + @wordpress/scripts)
yarn build     # production build
yarn test      # Jest with @wordpress/jest-preset-default
yarn format    # Prettier
yarn lint      # ESLint (WP preset)

Move from one plugin to another without re-learning the toolchain.

✨ TypeScript, Jest, Prettier — configured out of the box

Every v2 plugin ships with tsconfig.json (strict mode), jest.config.js, and .prettierrc — all wired to the @wordpress/* presets. You can use .ts / .tsx anywhere, write Jest tests next to your source, and run yarn format to keep everything consistent.

No opt-in, no separate setup step. Just write code.

✨ php bones migrate:to-v2 — the automated migrator

The breaking change story is tricky, so v2 ships with a one-shot migration command:

php bones migrate:to-v2

It removes gulpfile.js and package-lock.json, creates webpack.config.js / tsconfig.json / .prettierrc / jest.config.js from framework stubs, rewrites package.json scripts to the v2 set, drops gulp-era devDependencies and installs the v2 set (@wordpress/scripts ^31, typescript, glob, webpack-remove-empty-scripts). Run yarn install && yarn build afterward and you’re on v2.

We’ve used this migrator ourselves on 14 boilerplates. It works.

✨ php bones make:app with reserved-handle safety

Generating a new React/TypeScript app inside a plugin is now a one-liner:

php bones make:app my-dashboard

The command also refuses to create apps with reserved WordPress core handles (dashboard, post, common, jquery, wp-element…). We got bitten by this ourselves when a dashboard handle silently got dropped by WP core — now the CLI catches it before it becomes a mystery bug.

✨ 14 boilerplates, all re-released at v2.0.0

Every boilerplate in the WPBones family got the migration + a shiny new CLAUDE.md with an overview, smoke test steps, template-usage instructions, and a list of the framework surface it exercises:

• Base — the minimum starter (JS/TS, SCSS/LESS/CSS, a small React sample, a Jest test)

• TypeScript — strict TS showcase (interfaces, generics, unions, type guards, utility types)

• ReactJS — React with only @wordpress/* libraries, no third-party UI kit

• Mantine UI — full admin app: theming, dark mode, tabs, forms, modals, notifications, DataTable

• API — REST API routing with closures + controllers + permission callbacks

• Routes — admin menu routing + custom page routes + named URL helpers

• Blade — BladeOne templating (@foreach, {{ }}, partials)

• CPT — custom post types + custom taxonomies as service providers

• Cron — scheduled events via service provider

• Database — migrations, seeders, query builder, Eloquent ORM

• Hooks — plugin/hooks/*.php auto-inclusion convention

• Internationalization — POT/PO/MO/JSON pipeline with a working Italian translation

• Options — declarative config/options.php + live $plugin->options accessor

• Packages — demos of every official wpbones/* composer package

Each is a GitHub template repo — click Use this template, run php bones rename, and you have a working plugin.

🐛 v2.0.1 — inline-scripts routing fix

v2.0.1 lands today alongside v2.0.0 with a patch for a regression we caught during Mantine boilerplate testing. The short version: withInlineScript() and withLocalizeScript() now correctly route to adminAppsAssets when the handle was registered via withAdminAppsScript() — before v2.0.1, the inline script was silently dropped by WordPress because the handle wasn’t yet enqueued at the moment wp_add_inline_script() ran.

Any plugin combining ->withAdminAppsScript('my-app')->withInlineScript('my-app', 'window.MyApp = {…}') would have had window.MyApp come through as undefined. If you hit that, v2.0.1 is the fix. If you didn’t, you’re still getting it for free.

🚀 Docs, rebuilt

wpbones.com got a full refresh for v2:

• New Boilerplates section with a dedicated page per boilerplate

• Migrating to v2 guide walking through the automated migrator step by step

• WordPress environments comparison (wp-env, Valet, Local, DDEV, Lando, Playground, Docker, Vagrant) — pick the stack that fits your OS and workflow

• Stale Gulp references removed from core-plugin-files, getting-started, and official-packages

Getting Started

New to WPBones?

Pick a boilerplate that matches what you want to build, then:

gh repo create my-plugin --template wpbones/WPKirk-Boilerplate --public --clone
cd my-plugin
composer install
php bones rename "My Plugin"
yarn install && yarn build

Already on v1.x?

From your plugin root:

# Pull in WPBones v2
composer require wpbones/wpbones:^2.0.1

# Run the automated migrator
php bones migrate:to-v2

# Install the new dev deps and build
yarn install && yarn build

Review the Migrating to v2 guide for the full breakdown of what changes.

Links

• 🌐 Website & Docs: wpbones.com

• 📦 Framework on Packagist: wpbones/wpbones

• 🐙 GitHub: wpbones/WPBones

• 💬 Discord: Join the community

• 📋 v2.0.1 Release Notes: github.com/wpbones/WPBones/releases/tag/v2.0.1

• 🔁 Migrating to v2: wpbones.com/docs/migrating-to-v2

• 🧭 Boilerplates Overview: wpbones.com/docs/boilerplates/overview

About WPBones

WPBones is a Laravel-style framework for WordPress plugin development. It gives you an IoC container, service providers, Blade templating, Eloquent ORM, a CLI code generator, and all the patterns you already know from Laravel — adapted to the WordPress lifecycle. If you like Composer, yarn, webpack, and TypeScript as much as you like WordPress, this is the framework for you.

Introduction

The best maintenance tool is one that tells you where to look before you start cleaning. Scotty v2.0.2 adds two new Overview cards — Trash Summary and Environment Info — that give you instant visibility into what needs attention and what’s running under the hood. The dashboard widget got a complete rewrite with proper loading states and database metrics, the footer now credits the tools that power the plugin, and a dark mode bug that made confirm dialogs unreadable is finally fixed.

What’s New in 2.0.2

✨ Trash Summary Card

The Overview now includes a Items to Clean card that shows the total number of cleanable items across your site at a glance. Colored badges break it down by category:

• Revisions, auto-drafts, trashed posts, spam comments, orphan metadata

• Each badge only appears when items exist — clean sites show a green zero

• Click “Clean now” to jump directly to the Trash section

No more guessing how cluttered your database is — the number is right there on the dashboard.

✨ Environment Info Card

A new card in the Overview row displays your server configuration:

• PHP version, WordPress version, MySQL version

• Memory limit and max upload size

• Server software (nginx, Apache, etc.)

This data loads with zero extra queries — it’s pulled from the WordPress runtime at no performance cost. Useful for debugging, support tickets, or just knowing what you’re running.

✨ Redesigned Footer

The plugin footer has been completely rewritten:

• Left side: Docs link and Report Issue link with colored icons

• Right side: “Built with WP Bones | Mantine UI” with framework logos

• Clean, informative, and properly credits the open-source tools that power Scotty

✨ Smarter Dashboard Widget

The WordPress Dashboard widget has been rebuilt from the ground up:

• Loading skeleton while data fetches (was blank before)

• Error state with clear message if the API call fails

• Database Size and Cron Jobs count in a compact footer row

• Translated tooltips for all progress bars

• 19% smaller bundle — removed unused providers and CSS imports

• Fixed link — “Open Scotty” now goes to Overview instead of Trash

🐛 Dark Mode Fix

The modal confirm dialog title was invisible in dark mode — black text on dark background. Now uses var(--mantine-color-text) which adapts to the color scheme automatically.

🌍 Italian Translation Update

All 223 translatable strings are now covered with 100% Italian translation, including the new Trash Summary, Environment Info, and footer text. POT, PO, MO, and JSON files all regenerated.

Getting Started

New to Scotty? Install from your WordPress dashboard:

1. Go to Plugins > Add New

2. Search for “Scotty”

3. Click Install Now, then Activate

Already using Scotty? Update from your WordPress dashboard. All your settings and data are preserved.

Links

• 🌐 Website & Docs: scotty-plugin.vercel.app

• 📦 WordPress.org: wordpress.org/plugins/scotty

• 💬 Support Forum: wordpress.org/support/plugin/scotty

• 📋 Full Changelog: Release Notes

• ⭐ Rate us on WordPress.org: Leave a review

Built with WPBones

Scotty is built on the WPBones framework — a Laravel-style architecture for WordPress plugin development. The React dashboard is powered by Mantine UI, giving you a modern, fast, and accessible interface.

👉 Learn more about WPBones | GitHub

WP Bones, a renowned framework designed to streamline WordPress plugin development by providing a Laravel-like coding experience, has announced several updates that significantly enhance its capabilities. These updates focus on improving the handling of custom post types, deployment processes, and overall framework usability. Let's dive into the details of these exciting new features and improvements.

✨ New Features in Custom Post Type Management

WP Bones has introduced a range of new methods in its WordPressCustomPostTypeServiceProvider class, each designed to offer more control and customization for developers working with custom post types:

• Placeholder Title Customization: The new registerPlaceholderTitle method allows developers to set a custom placeholder title in the WP admin area, making it easier to guide content creators during the post creation process.

• After Title View: With the registerAfterTitleView method, developers can now inject custom views or HTML right after the title field in the admin area. This is particularly useful for instructions, custom fields, or additional metadata.

• Enhanced Column Management: The registerColumns method enables developers to define and manage custom columns in the post list view, thus improving the way information is presented and accessed in the WordPress dashboard.

• Post Meta and Meta Boxes Registration: Using registerPostMeta and registerMetaBoxes, developers can now register and manage post meta data more efficiently. These methods ensure that all necessary data is correctly associated with each post type and is easily accessible.

• Custom Labels Setting: The registerLabels method allows for the customization of labels used within the custom post type, helping to create a more tailored and intuitive user interface.

• Column Content Handling: The columnContent method provides a way to customize the content displayed in custom columns, offering more flexibility in displaying data relevant to custom post types.

See Boilerplate in Action

🛠️ Deployment Enhancements

WP Bones has also focused on improving the deployment process with new filters and commands that streamline how plugins are deployed and managed:

• Deployment File Management: New filters wpbones_console_deploy_dont_skip_files_folders and wpbones_console_deploy_default_skip_files_folders allow developers to fine-tune which files and folders are included or skipped during deployment, ensuring that deployments are both fast and accurate.

• Asset Building Control: The wpbones_console_deploy_build_assets filter provides an option to skip asset building during deployment, which can be useful for speeding up deployments or when working with pre-built assets.

🛠️ Documentation and Command Line Improvements

The WP Bones team has not only added new features but also made significant improvements to their documentation and command line tools:

• Updated Documentation: The documentation for custom post types has been thoroughly updated to reflect all the new changes. Additionally, a new core class documentation for custom post types has been introduced, making it easier for developers to get up to speed.

• Enhanced Command Line Tools: The php bones command has seen enhancements in package manager handling and reliability. The php bones install command now supports comprehensive package installation, which streamlines the setup process for new projects or when adding new dependencies.

💥 Important Deprecations

Developers should note the deprecation of the registerMetaBoxCallback property. To adapt to the new framework capabilities, use the registerMetaBoxes method instead. This change is part of WP Bones' ongoing efforts to streamline functionality and improve the framework's overall intuitiveness.

Conclusion

These updates to WP Bones make it an even more powerful tool for WordPress developers looking for a framework that supports rapid, streamlined plugin development. By enhancing the capabilities around custom post types and refining the deployment process, WP Bones is setting a higher standard for what developers can expect from a WordPress framework. Whether you're building simple plugins or complex solutions, these new features will undoubtedly enhance your development workflow and product quality. For more detailed information and to get started with these new features, visit the WP Bones Documentation.

The latest release of WP Bones, version 1.8.0, marks a significant update for developers seeking a robust framework for WordPress plugin development. This version introduces a suite of new features, bug fixes, and enhancements that streamline the development process and expand the framework's capabilities. Here’s a detailed look at what’s new and improved in WP Bones 1.8.0.

New Features to Enhance WordPress Plugin Development

WordPressScheduleServiceProvider:

One of the standout additions in this release is the WordPressScheduleServiceProvider, a new service provider dedicated to managing WordPress cron jobs. This feature simplifies the way developers schedule recurring tasks, aligning closer with the intuitive scheduling seen in frameworks like Laravel.

Command to Create Cron Jobs:

Accompanying the new service provider is the php bones make:schedule command. This command allows developers to easily create new cron jobs directly from the command line, making it a breeze to set up automated tasks within their plugins.

Boilerplate Enhancements:

WP Bones 1.8.0 introduces two new example plugins: WPKirk-Cron-Boilerplate and WPKirk-Hooks-Boilerplate. These boilerplates serve as ready-to-use templates that demonstrate best practices and provide a solid starting point for developing robust plugins using the WP Bones framework.

New Helper Functions:

The addition of wpbones_cache() and import() helper functions are notable for their utility in plugin development. wpbones_cache() offers a simplified way to manage cached data using WordPress transients, while import() streamlines the management of module folders, enhancing organization and efficiency in codebases.

File Property in Plugin Class:

The new file property in the Plugin Class, serving as an alias for the __FILE__ constant, provides a more intuitive way for developers to reference the main plugin file, further simplifying plugin architecture.

Bug Fixes and Improvements

Deployment Process:

Version 1.8.0 addresses a specific issue with the deployment process by excluding tsconfig.json from file synchronization. This change aims to streamline build and transfer operations, making the deployment of large plugins more efficient.

Text Domain Loading:

Improvements have been made to align text domain loading with the localization standards of WordPress 6.7. This ensures that plugins developed with WP Bones are fully compatible with WordPress' latest internationalization guidelines.

Enhanced Documentation and Usability

Command List Reorganization:

The reorganization of the command list in php bones enhances readability and usability, making it easier for developers to find and use commands relevant to their needs.

Updated Service Providers Documentation:

Documentation for Service Providers has been updated to reflect the new changes introduced in this release, providing developers with clear and concise information to take full advantage of the new features.

Boilerplate and Helpers Rewrite:

All boilerplates have been completely rewritten using the new wpkirk-helpers package. This not only enhances the project structure and maintainability but also ensures that the boilerplates remain a gold standard for plugin development in the WordPress ecosystem.

Improved Boilerplate Documentation:

The documentation for the Boilerplate has been significantly improved, addressing minor bugs and enhancing clarity to ensure developers have a seamless experience when using these resources.

Conclusion

WP Bones 1.8.0 is a testament to the framework's continued evolution, bringing WordPress plugin development closer to the standards and practices of modern web application development frameworks. With these new features and improvements, WP Bones is set to remain a preferred choice for WordPress developers looking for a structured, efficient, and powerful framework to build their plugins.

For developers already using WP Bones, upgrading to version 1.8.0 will provide immediate benefits in terms of development efficiency and plugin performance. For those new to the framework, now is a great time to explore its capabilities and consider how it might streamline your WordPress plugin development projects.

A Seamless Integration

For those unfamiliar, WP Bones is a framework designed to simplify the process of creating WordPress plugins. It borrows the elegance and structure of the Laravel framework, making it a powerful tool for developers. The introduction of the Raycast extension brings a new level of integration and productivity to the table.

What Does the Raycast Extension Offer?

The new extension is not just a tool but a transformation in how developers can manage their WordPress plugin development through Raycast. Here are some of the key features that make this extension a must-have:

• Notifications on the Latest Updates: Stay informed with automatic notifications about the latest versions of WP Bones, ensuring that you’re always using the most up-to-date and secure framework.

• Boilerplate Template Creation: Kickstart your plugin development with ready-to-use boilerplate templates. This feature saves time and sets up a standard structure for your projects right from the start.

• Quick Access to Documentation: Need help? Access the WP Bones documentation directly from Raycast with just a keyword search. This integration reduces the hassle of toggling between windows and streamlines your workflow.

• Useful Links at Your Fingertips: With direct links to FAQs, open issues, discussions, the WP Bones newsletter (this one), and the community Discord, the extension ensures that you have all the resources you need. This connectivity is crucial for both learning and troubleshooting.

• Always-On Menu: The extension includes a handy menu that’s always visible, providing quick access to all these features without interrupting your development flow.

Why Raycast?

If you're not already using Raycast on your Mac, here’s why you might want to consider it: Raycast acts as a command center, allowing you to execute commands and control your applications through a simple, unified interface. This can significantly speed up your workflow and increase productivity, especially when combined with the WP Bones extension.

Installing the Extension

Getting started with the new Raycast extension is straightforward. If you already have Raycast installed, adding the WP Bones extension is just a few clicks away. For those who haven’t ventured into Raycast yet, this might be the perfect reason to give it a try.

Conclusion

The new WP Bones extension for Raycast is more than just a tool; it's a productivity booster for WordPress developers. By integrating directly with Mac and Raycast, WP Bones is making plugin development as streamlined and efficient as possible. This is a clear signal that WP Bones is committed to enhancing the developer experience, staying relevant, and continually adapting to the needs of the WordPress community.

The latest release of WP Bones, version 1.7.0, introduces a suite of enhancements that streamline the development process for WordPress plugins by improving logging capabilities and database interactions. This update is particularly exciting for developers who appreciate the Laravel framework's approach but are working within the WordPress ecosystem.

Enhanced Logging Configuration

One of the standout features of this release is the addition of a new logging entry in the config/plugin.php file. This new feature allows developers to configure logging behavior directly within their plugin settings, making it easier to manage how information is logged and where it is stored. This change is supported by updated documentation that provides clear guidelines on how to leverage the new logging capabilities to monitor and debug plugins more effectively.

Refined Database Interaction

WP Bones 1.7.0 significantly refines how developers can interact with the WordPress database. The introduction of the DB::tableWithoutPrefix() method allows for querying database tables without the default WordPress table prefix, offering more flexibility in database design and management.

Additionally, the new $usePrefix parameter in the DB::table() method and the corresponding $usePrefix property in the Model, Migration, and Seeder classes make it possible to specify whether or not to use the table prefix during queries. This enhancement is particularly useful for developers who manage multiple installations or complex databases where control over table prefixing can lead to cleaner and more efficient code.

New Resources and Documentation

The release also includes the new WPKirk-Database-Boilerplate example plugin, which serves as a practical guide for developers to see the new database features in action. Furthermore, a new Templates section in the documentation has been added, providing additional resources and examples to help developers better utilize the framework.

Updates and Improvements

WP Bones 1.7.0 also includes several updates and improvements across the board:

• The Logging and Core Plugin Files documentation has been updated to reflect the new changes, ensuring developers have the most current information.

• The optional use of database table prefixes across various classes enhances flexibility in database management.

• The Database documentation has been revised to include the latest updates to the ORM capabilities.

• The WPKirk Demo plugin has been updated and improved, providing a better starting point for new projects.

Bug Fixes and Breaking Changes

This update also addresses a crucial issue where the Log provider prevented logs from being written to files or displayed in the console. Additionally, the paths for the Model and Eloquent model created by the bones command have been fixed, streamlining the development process.

However, developers should note the breaking changes in this release:

• The "log" entry in the config/plugin.php file is deprecated and replaced by the new logging setting.

• The "log_level" entry is also deprecated and should no longer be used.

Conclusion

WP Bones 1.7.0 represents a significant step forward in aligning WordPress plugin development with best practices from frameworks like Laravel. These enhancements not only improve the efficiency and flexibility of developing plugins but also ensure that developers can create more robust, scalable, and maintainable WordPress solutions. Whether you are building simple plugins or complex applications within WordPress, WP Bones 1.7.0 offers tools and features that will undoubtedly enhance your development workflow.

New Features to Enhance Your Plugin Development

Simplified Array Handling with wpbones_flatten_and_uniquify()

Arrays are fundamental in any development process, and WP Bones has added a new helper function, wpbones_flatten_and_uniquify(), which elegantly flattens and removes duplicate values from arrays. This addition is a boon for developers who frequently manage complex data structures, ensuring cleaner and more efficient data handling with minimal code.

Enhanced Plugin Management Commands

The WP Bones CLI has always been a powerful feature, and with v1.6.5, it becomes even more versatile. The introduction of the php bones plugin command allows developers to easily display plugin headers and perform related operations directly from the command line. Additionally, the php bones plugin --check-header command provides a quick way to validate plugin headers, ensuring they meet WordPress standards and avoid common pitfalls in plugin development.

Improvements and Changes

Streamlined Command Outputs and Documentation

The php bones command now greets users with a revamped intro message, making it more informative and user-friendly. Moreover, the update has removed verbose file listings during the php bones update command, which streamlines the update process by reducing clutter and focusing on essential information.

Documentation has also received significant attention in this release. With improved clarity and usability, developers can find information more quickly, reducing the learning curve and enhancing productivity.

Bug Fixes for a Smoother Experience

Enhanced HTML Component Compatibility

The HTML::select() component now correctly handles the multiple attribute (Thanks @bredecl). Whether you pass a comma-separated string or an array to the selected attribute, it will function seamlessly, making it more versatile for forms that require multi-select capabilities.

Eloquent Documentation and Update Command Fixes

The Eloquent ORM documentation has been updated, providing clearer guidance for integrating this powerful ORM into your WordPress plugins. Additionally, the php bones update command has been corrected to properly utilize the Domain Path from the plugin header instead of relying on a hardcoded localization folder, which enhances the flexibility and reliability of plugin updates.

View Class Inline Script and Style Enqueueing

A crucial fix in the View Class ensures that inline scripts and styles are correctly enqueued, preventing issues that could affect the performance and appearance of plugins.

Important Breaking Changes

Deprecation of Fluent Methods in View Class

Developers should note the deprecation of withScripts() and withStyles() methods in the View Class. These methods have been replaced by withScript() and withStyle() to standardize interactions and simplify the API. This change requires developers to update their existing code to accommodate the new method names, ensuring smoother functionality and maintenance.

Conclusion

WP Bones Framework v1.6.5 is a testament to the continuous improvement and dedication of the developers behind this project, aiming to provide a robust, Laravel-like environment for WordPress plugin development. These updates not only enhance functionality but also streamline the development process, making it easier and more efficient to build high-quality WordPress plugins.

Whether you are a seasoned WP Bones user or considering it for your next project, this new release offers compelling reasons to dive deeper into its capabilities. Happy coding!

One more thing…

From today, WP Bones is accessible using the URL wpbones.com 👏

The latest release of the WP Bones framework, version 1.6.0, marks a significant update for developers looking to streamline and enhance their WordPress plugin development process. Known for its Laravel-like elegance, WP Bones continues to evolve, ensuring it remains an indispensable tool in the WordPress ecosystem. This release introduces a host of new features, improvements, and updates that promise to improve workflow and expand functionality.

✨ What's New in WP Bones 1.6.0?

Enhanced Internationalization Support

In an increasingly global digital environment, making your plugins accessible in multiple languages is crucial. WP Bones 1.6.0 has added comprehensive internationalization support for ReactJS applications and blocks. This includes new npm scripts like make-pot and make-json to generate .pot and .json files respectively, ensuring that your plugins are ready for a global audience. Additionally, the framework now supports wp_set_script_translations(), further integrating with WordPress's core internationalization functionality.

Improved Documentation and Development Tools

Documentation is key to any framework, and WP Bones has expanded its already robust documentation to include Core Classes, Core Plugin Files, and FAQs. These additions make it easier for new developers to get up to speed and for seasoned developers to reference necessary details to enhance their plugins.

The introduction of new npm scripts such as package-update, check-engines, check-licenses, and format will streamline development processes and ensure code consistency and compatibility. These tools are designed to help developers maintain and update their plugins with greater efficiency.

New Boilerplates and Developer Tools

The release brings several new boilerplates, including the WP Bones API, Internationalization, Mantine, ReactJS, and Routes Boilerplates. These are ready-to-use examples that developers can utilize to kickstart their plugin projects, significantly reducing the development time and learning curve.

A new Flags Package has also been added, offering a method to manage static feature flags within your plugin, a technique borrowed from more advanced software engineering practices to control feature rollouts and testing.

UI/UX Enhancements

On the UI front, withInlineScript() and withInlineStyle() fluent methods have been added to the View Class, allowing developers to easily add inline scripts and styles, streamlining the process of making minor on-the-fly adjustments to plugins.

Changes and Improvements

The framework has not only added new features but also improved existing ones. The bones command now displays the WP-CLI version, and there have been minor fixes and improvements in the command's functionality. Documentation has been updated across the board, and both the WPBones demo and boilerplate plugins have been updated to reflect these changes.

Breaking Changes

Developers should note some breaking changes in this release. Several methods have been deprecated in favor of new ones to standardize and simplify the API. Notably, methods related to script and style handling in the View Class have been streamlined. Also, the localization folder in the demo and boilerplate plugins has been renamed to languages, which developers will need to account for in their existing projects.

🐛 Bug Fixes

WP Bones 1.6.0 also addresses several bugs, including an issue where admin scripts and styles were incorrectly loaded on the theme side of sites. Compatibility with macOS .DS_Store files has also been fixed, which is a welcome update for developers using Mac systems.

🤝 How to Adapt to WP Bones 1.6.0

To leverage the full potential of these updates, developers are encouraged to install WP-CLI, if not already done, to utilize the new npm scripts effectively. These scripts facilitate the localization process, making it easier to manage and update language files.

🧑‍💻👩‍💻 Welcoming New Contributors

This release also welcomes new contributors to the WP Bones community, like @bredecl, whose contributions help ensure that WP Bones remains at the cutting edge of WordPress plugin development.

Conclusion

WP Bones 1.6.0 is more than just an update; it's a comprehensive enhancement that broadens the framework's capabilities and solidifies its position as a must-have tool for WordPress plugin developers. By embracing these new features and updates, developers can expect not only to streamline their development processes but also to deliver superior WordPress plugins that stand out in the marketplace.

One of the key improvements in WP Bones 1.5 is the revamped deployment process, which now adheres to the rules set by the WordPress.org team. A notable change is the naming convention for the main plugin file, which has transitioned from index.php to a snake-case format based on the plugin's name. This adjustment, seamlessly handled by the php bones command, streamlines the development and submission of plugins to the repository.

In addition to these technical upgrades, the documentation for WP Bones has also received a comprehensive update, ensuring that developers have access to clear and up-to-date guidance on leveraging the plugin's features effectively. This emphasis on documentation underscores the commitment of the WP Bones team to supporting developers and simplifying the plugin development process.

But that's not all! WP Bones 1.5 brings another exciting development by aligning itself with WP Kirk Boilerplate, a complementary plugin that enhances the functionality and versatility of WordPress projects. By integrating WP Kirk Boilerplate with WP Bones, developers can leverage a powerful combination of tools to accelerate their development workflow and create more robust plugins.

One more thing…

In a further testament to its growing popularity and relevance in the WordPress ecosystem, WP Bones has made its debut on ProductHunt, a prominent platform for showcasing innovative products and services. This milestone signifies the increasing recognition of WP Bones within the developer community and highlights its potential to become a go-to solution for WordPress plugin development.

Vote WP Bones

The release of WP Bones 1.5 and its accompanying enhancements underscore the dedication of the development team to providing a robust and user-friendly framework for WordPress plugin development. By addressing key compatibility issues, improving deployment processes, and fostering collaboration with complementary tools like WP Kirk Boilerplate, WP Bones is empowering developers to create high-quality plugins more efficiently than ever before.

Stay tuned for more exciting updates and innovations from WP Bones as it continues to evolve and adapt to the changing needs of the WordPress ecosystem. Join the growing community of developers leveraging WP Bones to create cutting-edge plugins and unlock new possibilities in WordPress development. Let's embrace the future of WordPress development together with WP Bones at the forefront of innovation and excellence!

Introducing ReactJS Application Development

One of the most significant additions in WP Bones 1.4.0 is the ability to create full-fledged ReactJS applications right within your WordPress environment. With support for a wide range of additional packages, including popular ones like Material UI and React Router Dom, the possibilities for crafting dynamic and interactive web applications are now endless. Whether you are a seasoned React developer or just starting out, this integration opens up a whole new realm of creative opportunities for your projects.

See it in action

Enhanced Version Management

Managing versions and releases is now simpler and more robust with the improved php bones version command. This update streamlines the handling of patches and pre-releases, ensuring a smoother workflow and greater control over the versioning process. Whether you are tracking changes or preparing for a new deployment, this enhancement will undoubtedly streamline your development cycle and boost productivity.

Check out the Documentation

Revamped Documentation

In addition to these feature upgrades, WP Bones 1.4.0 brings a significant overhaul to its documentation, making it easier than ever to navigate and leverage the platform's capabilities. The new section dedicated to ReactJS applications serves as a comprehensive guide for developers looking to harness the power of React within their WordPress projects. Furthermore, the revamped documentation on Service Providers offers detailed insights and examples, empowering users to make the most of this essential feature.

Conclusion

With the release of WP Bones 1.4.0, the WordPress development landscape has been forever transformed. The integration of ReactJS, coupled with enhanced version management and improved documentation, cements WP Bones' position as a leading framework for modern web development. Whether you are a developer seeking to build cutting-edge web applications or a business looking to enhance your online presence, WP Bones 1.4.0 offers the tools and resources you need to succeed in today's digital ecosystem.

Join Forum

Upgrade to WP Bones 1.4.0 today and unlock a world of possibilities for your WordPress projects. Embrace the future of web development with WP Bones - where innovation meets versatility.

Stay tuned for more updates, tutorials, and insights on maximizing your WordPress development journey with WP Bones. Happy coding!

One more thing...

New X (Twitter) channel @wpbonesx

https://twitter.com/wpbonesx/status/1788543238795632944

Today marks a significant milestone for WP Bones enthusiasts as the demo of the WP Bones plugin can now be experienced online without any installation requirements. This achievement is made possible by the innovative technology of WordPress Playground, which is built on Web Assembly.

By visiting the WP Bones website, users can seamlessly explore how the WP Bones framework operates without the need for any complex setups or installations. This accessible demo not only showcases the capabilities of WP Bones but also provides a user-friendly way to delve into its functionalities.

For a hands-on experience of the WP Bones plugin demo, head over to wordpress.net playground now and witness the power of this dynamic framework firsthand. Don't miss out on this opportunity to explore the potential of WP Bones hassle-free!

What's New in WP Bones 1.3.4

Blade Templates Integration

Developers can now leverage the power of Blade templates, streamlining development and enhancing the flexibility of WordPress plugin creation. With BladeOne at the core, coding becomes more efficient and intuitive, mirroring the ease of use synonymous with Laravel.

Enhanced Documentation

Our commitment to user experience extends to comprehensive documentation. We have revamped and refined our online resources to provide clarity and guidance at every step. Whether you're a novice or a seasoned professional, navigating WP Bones has never been easier.

Streamlined Installation Process

Installing WP Bones is now a breeze, thanks to updates tailored to the latest plugin demo and boilerplate versions of WP Kirk. These advancements seamlessly integrate with GitHub templates, offering a cohesive environment for plugin development.

Join the WP Bones Community

As we unveil Version 1.3.4, we invite you to explore the possibilities with WP Bones. Whether you're a developer seeking efficiency or a business aiming for innovation, WP Bones empowers you to create exceptional WordPress plugins with ease.

Use GitHub Template

Download WP Bones 1.3.4 today and experience the future of WordPress plugin development firsthand. Embrace the simplicity of Blade templates, backed by a robust framework designed to elevate your projects.

Stay tuned for more updates, tutorials, and resources as we continue to evolve WP Bones and empower creators worldwide. Join us on this exciting journey of innovation and creativity.

Empower your WordPress journey with WP Bones 1.3.3 - Unleash the power of Blade templates, elevate your creations, and redefine plugin development with ease! 🚀

Let's code smarter, dream bigger, and create wonders with WP Bones 1.3.4! Together, let's shape the future of WordPress development.

Discover more at WP Bones and immerse yourself in a world of endless possibilities.

Empowering developers, inspiring creations - WP Bones is your canvas for WordPress innovation.

The Quest for Modernity in WordPress

One of the key goals of WP Bones is to infuse the WordPress ecosystem with the sophistication and efficiency of tools like Composer, npm, Laravel, and Gulp. While WordPress may lag behind in embracing the composer/vendor philosophy, WP Bones seeks to bridge this gap by offering a more contemporary development experience within the WordPress environment.

Embracing the Familiarity of Laravel

For developers familiar with Laravel, transitioning to WP Bones will feel like a natural progression. Drawing inspiration from Laravel’s elegant structure and practices, WP Bones integrates familiar elements while accommodating the nuances of the WordPress landscape. Although the direct integration with Composer is not yet feasible within WordPress, WP Bones strives to embody the spirit of Laravel in its approach to plugin development.

Navigating the WordPress Repository and Coding Restrictions

It’s essential to consider the unique coding restrictions and pre-submission guidelines when developing plugins with WP Bones for the WordPress repository. Understanding these constraints can help streamline the submission and approval process, ensuring that your plugin meets the stringent criteria set by WordPress.

The Composer Dilemma

Despite the allure of Composer’s vendor philosophy, the current architecture of WordPress falls short in fully embracing this approach. As a result, some of the remarkable features inherent to the composer/vendor architecture are not yet applicable within the WordPress ecosystem. Nevertheless, WP Bones strives to bridge this gap by amalgamating new and conventional development tools seamlessly into the WordPress environment.

Embracing the Laravel Spirit

If you harbor a fondness for the Laravel Framework, WP Bones will undoubtedly capture your interest. Drawing inspiration from Laravel, WP Bones encapsulates a familiar essence while navigating the unique constraints of the WordPress landscape. While the limitations of Composer integration persist, WP Bones offers a blend of Laravel-like features alongside distinct WordPress characteristics.

Unveiling the Mechanism

To delve into the intricacies of WP Bones, a preliminary perusal of the documentation is recommended. Subsequently, installing the WP Kirk Demo plugin unveils the panoply of WP Bones functionalities, providing a hands-on experience of its capabilities.

Unveiling the Advantages

WP Bones bestows an array of advantages to streamline WordPress plugin development:

• Rapid creation of WordPress plugin boilerplate in a matter of seconds

• Intuitive php bones command akin to Laravel’s artisan

• Compliance with PSR-2/PSR-4 standards for enhanced code readability

• Simplified plugin configuration through a cohesive config array

• Implementation of menus and page routes within a structured Controller architecture

• Integration of vendor architecture to augment plugin capabilities

Extending the Possibilities

In the spirit of Laravel’s extensibility, WP Bones allows for the integration of official packages such as:

• Actions and Filters JS

• Morris php

• Geolocalizer

• Pure CSS Tabs

• Pure CSS Switch

• WPTables

Additionally, developers are encouraged to craft their own extensions tailored to their specific needs.

In essence, WP Bones stands as a beacon for WordPress developers seeking a harmonious blend of contemporary development tools and the familiarity of Laravel-inspired practices. By embracing innovation and adapting to the unique WordPress environment, WP Bones paves the way for a new era of plugin development within the WordPress ecosystem.

Conclusion

WP Bones stands as a beacon for developers seeking a fusion of Laravel’s elegance and WordPress’s versatility. While challenges persist in fully realizing the composer/vendor architecture within WordPress, WP Bones offers a compelling solution for developers keen on leveraging modern development tools in the WordPress realm. Embrace WP Bones to embark on a journey that bridges the worlds of Laravel and WordPress, unlocking new possibilities in plugin development.

Contributing and Support

The WP Bones source code is managed on Github. There you’ll find all repositories and the official packages. You may propose new features or improvements by using the GitHub issues. Also, you can use the WP Bones Slack team to chat with me or with the community.

That’s all for me. Enjoy and let me know your feedback.

Why the Change?

The decision to migrate the documentation to a new platform stemmed from a desire to streamline the documentation process and provide a more user-friendly interface. While GitHub's wiki page served its purpose, I found the need for a more robust and customizable solution that could better cater to the community's needs.

Introducing Nextra and Vercel

To achieve this, I have opted to leverage Nextra as the documentation engine for WPBones. Nextra offers a modern and flexible way to create documentation websites with features like easy customization, theming, and better organization of content.

In addition, I have chosen Vercel as the hosting platform for the new WPBones documentation site. Vercel's reliable hosting services ensure fast loading times and seamless performance, providing users with a smooth browsing experience while accessing WPBones documentation.

Benefits of the Migration

This migration brings several benefits to WPBones users:

1. Improved User Experience: The new documentation platform offers a more intuitive and visually appealing layout, making it easier for users to navigate and find the information they need.

2. Enhanced Customization: With Nextra, I have the flexibility to customize the documentation site to better reflect the WPBones brand and optimize content organization.

3. Better Performance: Vercel's hosting ensures optimal performance, with faster loading times and reliable uptime, enhancing the overall user experience.

4. Community Engagement: By providing a more user-friendly documentation platform, I aim to foster greater community engagement and collaboration among WPBones users.

What to Expect

With the migration to Nextra on Vercel, users can expect an improved documentation experience with updated content, better navigation, and a sleek design aimed at simplifying learning for WPBones.

Thank you for your ongoing support, and I invite you to explore the new WPBones documentation site to experience the improvements firsthand.

Stay tuned for more updates and happy coding with WPBones!