Existing Publii plugins · repair or focused feature

One plugin change. One explicit handoff.

Choose a fixed £45 repair for one reproducible defect or a fixed £75 focused feature in one existing Publii plugin and one supported Publii version. Both include a written scope, a patch or tested installable ZIP, focused evidence, and install or rollback notes.

Describe the plugin change privately Email without an account

One bounded change · no upfront payment · no source or access requested during the public fit check

£45

One reproducible defect

Repair, prove, and hand over.

One supported Publii version, the smallest defect-specific change, one focused regression or reproduction check, and a reviewable patch or installable ZIP.

£75

One focused feature

Add one outcome to an existing plugin.

One supported Publii version, one existing public plugin, one bounded configuration, modifier, event, or output behavior, focused tests, and a reviewable patch or installable ZIP.

Payment for either scope is due only after the written acceptance checks pass. The £75 route is shared only after acceptance; it is never used for a deposit or unspecified work.

Public capability proof, not customer work

One defect patch and one focused feature, both tested publicly.

Publii pull request #2673 adds site-configuration cleanup after global plugin removal. publii-cdn pull request #3 adds opt-in feed-image rewriting without changing feed identity URLs. Both are pending upstream review and neither is merged, adopted, commissioned, or customer work.

Inspect pending defect PR #2673 Inspect pending feature PR #3 Guide: modify feed images without changing IDs

A good fit

An existing plugin with a public repository, release, issue, or minimal reproduction.
One defect or one focused feature on one supported Publii version.
Objective checks that distinguish the current behavior from the requested result.
A change reviewable as a small patch or tested installable ZIP.

Not in either scope

A new plugin from scratch, multiple unrelated defects or features, or a roadmap.
Publii core changes, unsupported private internals, content migration, or production site operation.
Marketplace submission, new paid dependencies, credentials, private source, site exports, or visitor data.
Security testing, compliance work, deceptive behavior, or guaranteed marketplace or business results.

Small change, explicit process

How it works

Send the public reference. Choose repair or feature, then include the Publii version, current behavior, requested result, and acceptance checks.
Receive a written fit check. I confirm the exact change, fixed £45 or £75 price, version, exclusions, delivery target, evidence, and handoff format before work starts.
Share only what is necessary after agreement. A public repository is preferred. No production credentials, full site exports, personal data, or payment details are needed.
Review the change. I deliver a patch or tested ZIP with the focused check and install or rollback notes.
Pay after acceptance. Payment is due only after the written acceptance checks pass. One scope-only revision is included if those checks identify a miss.

Can the change be specified without sharing a live site?

Choose the £45 repair or £75 feature scope, then send the public plugin, Publii version, current behavior, requested result, acceptance checks, and timing. I will confirm fit before requesting source or access.

Request the £45 / £75 scope Email the public scope