masteris unsafe.3.xis the stable branch.
Papi has a different approach on how to work with fields and page types in WordPress. The idea is coming from how Page Type Builder in EPiServer works and has been loved by the developers.
So we though why don’t use the same approach in WordPress? Papi is today running in production and has been easy to work with when it came to add new fields. Papi don’t have any admin user interface where you should add all fields, we use classes in PHP, where one class represents one page type and in your class you add all fields you need. It’s that easy!
v3.2.0 will likely be the last release I plan to work on as the core maintainer of Papi since my focus has shifted from WordPress to doing more JavaScript and Go projects. I hope you understand my decision to step back from the project, if you have any questions or would be interested in take over some of the maintenance of the project please let me know. I will still be around answering questions and helping any new maintainers. Some bug fixes and/or pull request may be added (but no new versions) since me and my colleagues use Papi internally and will be continuing doing it.
If you're using Composer to manage WordPress, add Papi to your project's dependencies. Run:
composer require wp-papi/papiOr manually add it to your composer.json:
"require": {
"php": "^^7.4",
"wordpress": "^4.6",
"wp-papi/papi": "^3.2"
}Install dependencies:
make deps
Build CSS:
make css
Build JavaScript:
make js
Visit the readme file for testing.
You can check if your contribution passes the styleguide by installing PHP CodeSniffer and running the following in your Papi directory:
make lint:php
Visit the contributing file.
If you discover a security vulnerability within this package, please send an e-mail to Fredrik Forsmo at [email protected]. All security vulnerabilities will be promptly addressed.
MIT © Fredrik Forsmo