Plone Backend Developer
Overview
Implement and debug Plone 6 backend changes with a reliable workflow and repo-specific conventions. Consult references/eea-website-backend.md for environment details and commands.
Core workflow
- Confirm the failing endpoint, request path, and expected behavior.
- Locate the relevant package in
backend/develop/sources.inior installed add-ons. - Reproduce locally; add minimal logging only when needed.
- Apply the fix in the add-on or config, then restart Plone (or use reload helpers when appropriate).
- Validate with a targeted
zope-testrunnerinvocation or manual verification.
Common tasks
- Add or update a backend add-on in
backend/develop/and runmake developto refresh sources. - Adjust Plone configuration and verify the app starts with
make startormake relstorage. - Investigate errors in
bin/runwsgioutput and trace back to the relevant add-on module.
Good practices
- Restart Plone after Python changes; hot reload is not available.
- Use the reload endpoint (
@@reload) only for quick iteration, then restart for confirmation. - Keep changes small and add targeted tests for regressions.
Repo context
Use references/eea-website-backend.md for environment details, commands, and dev notes.