Подключение CMS на Next/React front-end

Мы запускаем в Украине услугу психологического здоровья как веб-приложение React / Next и ищем внешнего англоязычного разработчика, который возьмет на себя текущую работу (мы готовы на 95% с самим приложением).

Ниже описание часть на русском и часть английском языке. Кому интересно уточните пишите / говорите ли на английском, какой почасовой тариф. 

Первая задача - лендинг должен быть визуально редактируемым, чтобы те же элементы можно было повторно использовать на новых страницах.

Вот некоторые из CMS, которые вы можете рассмотреть или предложить свою:

https://strapi.io/

https://reactbricks.com/

https://www.builder.io/

https://www.storyblok.com/

https://www.datocms.com/

https://tina.io/

Talking from the perspective of a user story, basically, a content editor should be able to login to a dashboard where the current public site is editable with available components and should be able to create a sequence of pages (like this example about stress pages) in our two languages just within this 3rd party solution. Then publish to dev environment and after testing select that only specific pages would be pushed to production while public site navigation is updated (if needed, because some page sequences will exist entirely outside the current menu.

Requirements:

1. visual cms for Next to be able to build our own static pages with predefined elements (titles, text areas, buttons).

2. support for multiple languages, so we would not need to check if we have not left out some pages untranslated when we create a new flow in one language. for the first version, we need two languages - Ukrainian and Russian.

3. Django then would be then used for content management on the internal app, not for any externally available pages, so it's not part of the scope.

4. Performance should still be good given the selected stack. does not matter if we need to push changes to some other environment to see the preview. does not matter if we have to wait for the pages to be optimised for publishing. A website can't be single-page application and content can't be served via Jvascript.

5. We need to think in terms of blocks/sections within the page, not page templates themselves. We need to be able to copy the "about us" page as a collection of blocks/sections with elements and then add/change the existing ones, all while editing the content.

6. Routing between pages will be nothing complicated since we will basically lead users to the same payment button. like creating a new landing flow for stress topic should be 2-3 pages and then same payment button. so page stress#1 should lead to stress#2 via customisable button links etc.