Neos packages in a joined repository for pull requests.

Fund package maintenance!

Installs: 91 310

Dependents: 1

Suggesters: 0

Security: 0

Stars: 240

Watchers: 21

Forks: 186

Open Issues: 469


7.1.1 2021-08-25 09:13 UTC

This package is auto-updated.

Last update: 2021-09-07 11:44:28 UTC


Travis Build Status Code Climate StyleCI Latest Stable Version License Documentation API Docs Slack Discussion Forum Issues Translation Twitter Pull Reminders

Neos development collection

This repository is a collection of packages for the Neos content application platform (learn more on The repository is used for development and all pull requests should go into it.

If you want to install Neos, please have a look at the documentation:


If you want to contribute to Neos and want to set up a development environment, then follow these steps:

composer create-project neos/neos-development-distribution neos-development dev-master --keep-vcs --prefer-install=auto

Note the -distribution package you create a project from, instead of just checking out this repository.

The code of the CMS can then be found inside Packages/Neos, which itself is the neos-development-collection Git repository (due to the --prefer-install option above). You commit changes and create pull requests from this repository. To commit changes to Neos switch into the Neos directory (cd Packages/Neos) and do all Git-related work (git add ., git commit, etc) there. If you want to contribute to the Neos UI, please take a look at the explanations at on how to work with that. If you want to contribute to the Flow Framework, you find that inside the Packages/Framework folder. See

In the root directory of the development distribution, you can do the following things:

To run tests, run ./bin/phpunit -c ./Build/BuildEssentials/PhpUnit/UnitTests.xml for unit or ./bin/phpunit -c ./Build/BuildEssentials/PhpUnit/FunctionalTests.xml for functional/integration tests.

To switch the branch you intend to work on: git checkout 7.1 && composer update


We use an upmerging strategy, so create all bugfixes to lowest maintained branch that contains the issue (typically the second last LTS release, which is 4.3 currently), or master for new features.

For more detailed information, see and