Skip to content

Contribute to TYPO3 Icons

TYPO3 Icons is maintained in the open. Contributions improve the shared visual language used by the Core, extensions and custom backend modules—from a more legible SVG to clearer usage guidance or a more reliable build.

Where your contribution fits

Start with the part of the project you intend to change. Each path has a different source of truth and a different review focus, but all changes use the same repository and pull-request workflow.

Icon changes

Refine an existing icon or add an asset that follows the established grids, naming rules and visual conventions. Work in src/, keep identifiers stable where possible and review the generated result at the sizes people will actually see.

Prepare an icon contribution

Documentation and tooling

Improve explanations, examples, templates, styles or build scripts. The documentation is part of the product: it determines whether developers can find the right identifier and implement it correctly without reading the repository source.

Set up the project locally

Releases

Publishing is a maintainer task. The release process turns reviewed changes into a versioned npm package, updates the changelog and creates the Git tag consumed by downstream projects.

Review the release process

Review-ready changes

Keep the change focused and explain the problem it solves. For visual work, include before and after previews at the intended rendered size. For documentation or tooling, describe the user path or failure that motivated the change and note how you verified the result.

Generated files should reflect their sources, not replace them. Edit the SVGs, templates or styles first, run the relevant build and review its output before opening the pull request. A focused contribution with reproducible checks gives reviewers the context they need to make a confident decision.

From branch to merge

  1. Create a focused branch from the current default branch.
  2. Change the source files and run the checks relevant to that change.
  3. Review generated assets and documentation locally.
  4. Commit with the project prefix that best describes the change.
  5. Open a pull request with context, verification notes and useful visual evidence.

Review may lead to small refinements. That is part of keeping a library used across many TYPO3 versions consistent: a local improvement also has to work as part of the complete set.