WordPress, GPL and plugin distribution

WordPress core

WordPress is distributed under GPLv2 or later. The project's WordPress plugins need a specific GPL-compatibility and distribution review; do not assume a plugin becomes proprietary merely because it is independently packaged or commercially sold. WordPress guidance treats plugins as derivative works subject to GPL-compatible licensing, although legal questions about scope can be nuanced.

HSLG-specific boundaries

Keep HSLG Presentation, App API and Documentation Publisher as separate installable plugins, with distinct file manifests and third-party notices. Their source/header licences, distribution rights and dependencies must be recorded individually. Check that the plugin archives exclude private source notes, secrets, developer tools and unlicensed media.

Release steps

Check every shipped PHP/JS/CSS file's origin and rights. Include the applicable source licences, copyright attribution and any vendor notices. Check any copied WordPress starter code and upstream MIT/Apache dependencies for conflicting terms. Where GPL source availability or notices are required, make them available with the shipped distribution and preserve upstream notices.

Not a bypass

WordPress installation, wp_mail(), WP-CLI revision handling and the REST API do not themselves grant rights to redistribute upstream code, hosted content, logos or photography. Keep ownership review separate from operational deployment.