🧩 WP Bones 3.1 β€” your own stubs

WP Bones 3.1 is out 🦴 your generators, your templates 🧩

πŸ“ Your stubs come first. Every make:* command reads the stubs/ folder of your plugin before the framework's, and tells you when it does.

πŸ“€ stub:publish copies the framework's stubs there to start from. A stub you edited is kept unless you pass --force.

πŸ“¦ deploy leaves them out of the package.

⬆️ composer update wpbones/wpbones

πŸ‘‰ Docs, boilerplates and live Playground demos:

Which generator would you change first? πŸ‘€

14 views

Add a comment

Replies

Best

Thanks for another steady update, Giovambattista. Leaving the stubs out of the deploy package is a small thing, but it shows you thought about real use

Β πŸ˜ŠπŸ™ thx - really appreciated