Download the PHP package zestry-dev/wp-toolkit without Composer

On this page you can find all versions of the php package zestry-dev/wp-toolkit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package wp-toolkit

Zestry WP Toolkit

A toolkit for building WordPress plugins where a file in a directory is a feature — drop one in resources/commands/ and it is a WP-CLI command, one in resources/admin-pages/ and it is a menu page — copied into your plugin under your own namespace, so it becomes your code rather than a dependency.

Quickstart

Run these from inside your own plugin's directory. zt is short for zestry toolkit, and the command is registered by your plugin's autoloader, so the plugin has to be active before init.

init asks for a namespace and a text domain, then copies the kernel into lib/Core/Kernel/ under your namespace. wp zt add copies each feature module you want beside it, and declares it for you.

Full walkthrough: Getting started.

What it looks like

Three files, and wp acme-plugin greet Alice works.

No WP_CLI::add_command(), no hook names. The module walks resources/commands/, wires each returned object, and registers it under your plugin slug.

What do you want to do?

Almost everything is the same two steps: add the feature once, then make a file each time you want one of them. The second command writes a working file into the directory the first command taught your plugin to watch.

I want to… Run Reference
Add a wp command wp zt add cli
then wp zt make command greet
cli
Add an admin screen wp zt add admin-pages
then wp zt make page settings
admin-pages
Expose an HTTP endpoint wp zt add rest-api
then wp zt make route widgets
rest-api
Register a post type wp zt add post-types
then wp zt make post-type book
post-types
Add a field to the editor wp zt add fields
then wp zt make field acme_rating
fields
Run something on a schedule wp zt add cron
then wp zt make schedule sync
cron
Run work in the background wp zt add queue
then wp zt make job send-receipt
queue
Create or change a table wp zt add migrations
then wp zt make migration create-books-table
migrations
Build a block wp zt add blocks
then wp zt make block card --dynamic --view=none
then npm run build
blocks
Give an AI agent a tool wp zt add abilities
then wp zt make ability publish-post
abilities
Store settings wp zt add options options
Render markup from a template wp zt add views
then wp zt make view emails/receipt
views
Share JavaScript between screens wp zt add assets
then wp zt make shared formatting
JavaScript

Three that are not that shape:

I want to… Run Reference
See what this plugin already has wp zt describe --installed wp zt describe
Find out why nothing happened wp zt doctor Troubleshooting
Take a toolkit release wp zt update --dry-run wp zt update

Nothing needs adding up front. Reach for one when you hit what it solves — the full list is under wp zt add brings along whatever the thing you asked for depends on.

What a plugin is made of

Everything a plugin is made of is a module, and bootstrap.php lists every one of them. Nothing is built that is not listed there — asking for an undeclared module throws — so reading that file tells you what the plugin has, and the key above each one says when it starts.

A module that does something on its own implements Bootable:

Path resolves a path when you ask it and has no on_boot(); Ajax binds its hooks when the plugin builds it, on the requests it serves, and does. That is why Ajax sits under a heading and Path does not — a module that acts on its own has to say when, and the top level throws for one that will not.

with() is how anything reaches anything — in a module, and in every file a module discovers:

The same instance every time, so two callers asking for Options share its state.

Documentation

Read once

Keep open

Guides

Reference

Every name below is what you pass to wp zt add — wp zt add meta-boxes, wp zt add request.

Requirements

Updates

Copying is one-way: a later release of the toolkit does not reach a plugin that has already run init. Nothing upstream can break your plugin, and nothing upstream can fix it either.

wp zt update is how you take a release when you want one. It re-copies everything under lib/Core/ — the kernel and every module you added — and before writing anything it names the files you have edited, so a fix never arrives at the cost of your own work. Files you changed are kept unless you pass --force; --dry-run reports and stops. Everything outside lib/Core/ is yours and is never touched.


All versions of wp-toolkit with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package zestry-dev/wp-toolkit contains the following files

Loading the files please wait ...