Plugin Development Kit (PDK)
- Easy to use API
- Feature equality between all implementations
- Automated building using a configuration file
- Easily configurable
- Extensible: If the default implementation does not fit your needs, you can modify it
The following terms are used throughout the documentation:
|App||Your implementation of the PDK. This is your plugin, app, module or extension that uses the PDK.|
|PDK backend||The PDK backend is the part of the PDK that is written in PHP.|
|Admin||The admin is the admin panel, dashboard or backend of your app.|
|Checkout||The checkout is the checkout page of your app.|
To get started with the PDK, you need to set up the backend and (optionally) the frontend. The backend is required for all other PDK functionality. The frontend is only required if you want to use custom checkout functionality.
The backend contains all logic to communicate with the MyParcel API. The backend is required for all other PDK functionality.
The frontend contains the logic to render the MyParcel components that communicate with the PDK backend in your admin panel and checkout.
The PDK is used in the following plugins:
Why use the PDK over an SDK?
We welcome contributions to the PDK. Please read our developer guide to get started.
The MyParcel PDK is open-sourced software licensed under the MIT license.
If you discover a security vulnerability within the PDK, please let us know via our contact form.