Speeding up the React UI development with your help: funding

  • As we announced during Neos Conference and in previous blog articles, we would love to deprecate the current EmberJS based Neos backend with the release of Neos 3.3 LTS at the end of this year.
  • However, as we are an open source project which is largely developed during spare time or between paid projects, we cannot guarantee that we will be able to spend enough time on the React UI to get it to the quality we desire and you deserve.
  • Everyone who has worked with the beta of the React UI has given us extremely positive feedback.
  • We want to use it in projects ourselves and want to see most Neos instances switch to it after its release.

We want to make sure the new React UI is production-stable for Neos 3.3 LTS. To achieve this, we need a focused effort as a professional software projec…

@neoscms: Help us finalize the #neoscms #reactjs UI for Neos 3.3 LTS: – together we can get it done!

As we announced during Neos Conference and in previous blog articles, we would love to deprecate the current EmberJS based Neos backend with the release of Neos 3.3 LTS at the end of this year. However, as we are an open source project which is largely developed during spare time or between paid projects, we cannot guarantee that we will be able to spend enough time on the React UI to get it to the quality we desire and you deserve.

Everyone who has worked with the beta of the React UI has given us extremely positive feedback. They love the speed, CKEditor stability, the iframe approach, the extensibility and the list goes on. We want to use it in projects ourselves and want to see most Neos instances switch to it after its release.

To get there, we want to do the remaining development until version 1.0 of the React UI as a focussed software project, with fixed timelines, clear goals and commitments.

If you support the accelerated finalization of the React UI with 5.000€ or more, you will get a great return: You can give us one of your projects and we will test it with the new UI for three days. This is a win-win-win situation!

To be clear, here is what we will not do as part of the React UI testing:

If we spot some issues, we will give you feedback (e.g. if there is installation trouble, or anything preventing us from doing the testing).

Note: if you created custom (ember-based) inspector editors, they have to be manually ported to React; this is not covered here.

Speeding up the React UI development with your help: funding