WordPress / WordPress/php-toolkit
Blueprints plugins
Open
Nobody has claimed this yet.
Architecture
V1
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
- The PHP library should make every part of the JSON schema extensible. All Core Blueprint features could be implemented as plugins. Any developer consuming the library should be able to customize what's accepted.
- Could Blueprint plugins be shipped as WordPress plugins? My gut says no, since the Blueprint executor can't
require "wp-load.php"as that would make it fragile and prone to any errors in the very WordPress it acts on. But maybe there's a way to do it? - Could, and should, the Blueprint.json file itself define a list of plugins? Why or why not?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the Blueprint executor and the Blueprint.json format referenced in the issue. Investigate how Core Blueprint features and JSON schema handling are currently defined, then determine whether extensibility and plugin loading have a defined boundary. Done would require an agreed plugin architecture and documented decisions about WordPress integration and Blueprint.json configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100