neos/neos-ui

NEOS CMS UI rewritten in React

@neos/neos-ui

, _(*1)

The Neos CMS interface written in ReactJS and a ton of other fun technology., _(*2)

Versioning

This repository follows the same versioning scheme as Neos itself. Release roadmap is available here, _(*3)

That means: * All bugfixes go to the lowest maintained branch * All new features go only to the 8.2 branch * New minor and major releases are made in sync with Neos/Flow. Bugfix releases may be available independantly, _(*4)

Currently maintained versions

• NeosCMS version 7.3: branch 7.3
• NeosCMS version 8.0: branch 8.0
• NeosCMS version 8.1: branch 8.1
• latest development happens currently in the 8.2 branch

Releases with just security updates

• NeosCMS version 5.3: branch 5.3
• NeosCMS version 7.0: branch 7.0
• NeosCMS version 7.1: branch 7.1
• NeosCMS version 7.2: branch 7.2

Browser support

The new interface supports all evergreen (i.e. self-updating) browsers, including: Chrome, Firefox, Safari, Edge, Opera and other webkit-based browsers., _(*5)

If you discover bugs in any of the supported browsers, please report them!, _(*6)

Features

• Blazingly fast Yarn 3 + ESbuild stack
• https://www.neos.io/features/editing-content.html
• https://www.neos.io/features/inline-editing-true-wysiwyg.html

Installation and usage

The UI is already included in the base Neos distribution. And on Packagist available via: neos/neos-ui, _(*7)

Updating

composer update neos/neos-ui

Installing latest development

For trying out the new UI, we recommend you to run the regularily released beta releases. However, if you want to stay on bleeding-edge, or want to help out developing, you'll need the 8.2.x-dev release. You can install the latest release using:, _(*8)

composer require neos/neos-ui-compiled:8.2.x-dev neos/neos-ui:8.2.x-dev

Contributing

Please follow the respective guides for contributing on OSX and on Linux., _(*9)

on Windows

1) Ensure you have the relevant version installed (see above)., _(*10)

2) Please install Docker for Windows., _(*11)

3) Run docker-compose up., _(*12)

4) Inside Configuration/Settings.yaml, set the following property for disabling the pre-compiled files:, _(*13)

Neos:
  Neos:
    Ui:
      frontendDevelopmentMode: true

6) Get an overview about the codebase. We've recorded an introduction on YouTube which gets you acquainted with the basics. Additionally, please get in touch with us on Slack in the channel #project-ui-rewrite. We're eager to help you get started!, _(*14)

on OSX / Linux

In order to start contributing on OSX / Linux, follow the following steps:, _(*15)

1) Ensure you have the relevant version installed (see above)., _(*16)

2) We require Chrome as well as the yarn(https://yarnpkg.com/en/) command and GNU Make(https://www.gnu.org/software/make/) to be installed on your system., _(*17)

3) The currently supported version of node is defined in .nvmrc file. If you have nvm installed, you can just run nvm install && nvm use from the project directory., _(*18)

4) Inside Configuration/Settings.yaml, set the following property for disabling the pre-compiled files:, _(*19)

Neos:
  Neos:
    Ui:
      frontendDevelopmentMode: true

5) Run the initialization script:, _(*20)

make setup

6) Get an overview about the codebase. We've recorded an introduction on YouTube which gets you acquainted with the basics. Additionally, please get in touch with us on Slack in the channel #project-ui-rewrite. We're eager to help you get started!, _(*21)

Guideline for PR and commit messages

Please see our guideline on how to write meaningful descriptions for your contributions., _(*22)

Doing upmerges

To do the upmerge run the following commands, _(*23)

git checkout 7.0 && git fetch && git reset --hard origin/7.0 && git merge --no-ff --no-commit origin/5.3
# review and `git commit`
git checkout 7.1 && git fetch && git reset --hard origin/7.1 && git merge --no-ff --no-commit origin/7.0
# review and `git commit`
git checkout 7.2 && git fetch && git reset --hard origin/7.2 && git merge --no-ff --no-commit origin/7.1
# review and `git commit`
git checkout 7.3 && git fetch && git reset --hard origin/7.3 && git merge --no-ff --no-commit origin/7.2
# review and `git commit`
git checkout 8.0 && git fetch && git reset --hard origin/8.0 && git merge --no-ff --no-commit origin/7.3
# review and `git commit`
git checkout 8.1 && git fetch && git reset --hard origin/8.1 && git merge --no-ff --no-commit origin/8.0
# review and `git commit`
git checkout 8.2 && git fetch && git reset --hard origin/8.2 && git merge --no-ff --no-commit origin/8.1
# review and `git commit`

Development commands

Writing unit tests

The unit tests are executed with jest. To run the unit tests, execute make test in your shell., _(*24)

Adding unit tests is fairly simple, just create a file on the same tree level as your changed/new feature, named [filename].spec.js and karma will execute all tests found within the spec file, other than that, just orient yourself on the existing tests., _(*25)

Use it.only(() => {}) and describe.only(() => {}) if you want to run a specific test and not the whole test suite., _(*26)

Integration tests

To setup end-to-end tests locally you have got to do the same things described in CircleCI workflow, namely take the test disribution and composer install in it, put the right branch into Neos.Neos.Ui folder and run webserver and mysql server with the same config as described in the test distribution's Settings.yaml (or adjust it)., _(*27)

For executing the end to end tests on a Mac with catalina or higher you need to permit screen recording. Open 'System Preferences > Security & Privacy > Privacy > Screen Recording' and check 'TestCafe Browser Tools' in the application list., _(*28)

Debugging integration tests

• View the recording via Sauce Labs. You can find the url in the beginning of the test output.
• Observe Flow exceptions and logs in build artifacts.
• You can trigger a SSH enabled build via the CircleCI interface and then login.

Just the end to end tests fail

It can happen that end to end tests fail caused by cached sources. So if you change PHP code for instance and don't adjust the composer.json it can happen that your new code change is not used because it is not part of the cache. In this case we need to flush the CircleCI caches manualy., _(*29)

We have introduced an environment variable called CACHE_VERSION. We need to change the variable to to new timestamp for instance to invalidate the caches., _(*30)

1. go to https://app.circleci.com/settings/project/github/neos/neos-ui and login
2. open the project settings and choose Environment Variables
3. Delete the CACHE_VERSION and create a new one with the value of the current timestamp

Retrigger the build and it should work., _(*31)

Releasing

You only need to trigger the jenkins release with the version you want to release. After jenkins has finished you need release a new version on github., _(*32)

License

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE., _(*33)