License and asset attribution
The documentation, code, and assets in this handbook are covered by different licenses. The split below helps you see what you can reuse freely and what needs extra attribution care.
License split
Section titled “License split”| Subject | License |
|---|---|
| Documentation and original visual assets | CC BY 4.0 |
| Example code, components, scripts, and project configuration | MIT |
| Third-party fixtures | Own license and attribution recorded individually |
CC BY 4.0 (Creative Commons Attribution 4.0)
Section titled “CC BY 4.0 (Creative Commons Attribution 4.0)”Applies to this documentation and original visual assets. It permits copying, distribution, and adaptation as long as you give appropriate credit and note any changes. This is a permissive attribution-required license, not public domain.
MIT (example code and project configuration)
Section titled “MIT (example code and project configuration)”Applies to example code, components, scripts, and project configuration. MIT is permissive and allows commercial and free redistribution, typically requiring that the copyright notice and license text be kept.
Attribution for third-party assets
Section titled “Attribution for third-party assets”- Any third-party fixture or asset records its own source, license, and required attribution separately, and does not default to the CC BY 4.0 / MIT branding.
- Assets from the legacy repository are migrated only after ownership is confirmed; images of unknown provenance are not adopted directly.
- This project prefers project-owned or programmatically generated assets; external images are out of scope until a maintainer approves an exception.
Notes for reuse
Section titled “Notes for reuse”- When reusing documentation, keep the attribution and state the source.
- When reusing example code, keep its MIT copyright notice.
- When using an image of clear third-party provenance, follow the license conditions noted for it and do not invent ownership in the body text.
Related
Section titled “Related”- If you have questions about the attribution of a particular asset, contact the maintainers via
mailto:support@webp.se. - The asset ownership audit and the method for recording third-party exceptions live in the (internal) maintenance guidance for this handbook.