This will add ability to undo and redo changes to widgets while editing a revision. It will also unlock the ability to add optional autosave while editing content.
We are bringing the ability to lock/unlock changes to particular pages (content freeze), preview and restore previous versions from the history and schedule automatic publication of an open revision.
Completely split the codebase of the user-facing websites from the admin panels. This will allow faster iteration on performance related tasks, quicker deploys, fine grained security and ability to expand our support from the latest version of Next.js to other frontends like Astro or Vue. Additionally, it will make updating the admin panels easier to test. The new admin will come with improved UX and visuals.
As part of the admin redesign, the media browser will be updated with better UX, faster loading and ability to find the right images faster.
Raketa Cloud keeps data in structured way. With this addition we’ll unlock even more possibilities for performant server-side personalizations. This will add ability to setup custom workflows when saving or fetching content from Raketa Cloud. Here are several examples:
These data processing hooks will be fully customizable by the particular website and can be integrated with multiple external systems. It can also be used for specific validations.
We plan to overhaul the process of managing static translations like form labels or error messages. We’ll setup an automated process for importing and exporting these strings plus ability to connect external provider like Lokalize or PhraseApp.
Sometimes widgets with multiple options have different presets that change their visuals when combining certain settings. To make building skeleton pages faster we are making these first class citizens and part of the widget UI. As a bonus these will be listed on the documentation site to help manage regression testing.
While currently we support basic showcase of typography, colors and widgets these are not usually enough in complex and growing design systems. That’s why we are elevating this into a more complex documentation site that builds automatically based on components, widgets and layouts to act as a single stop for regression tests and a documentation of how design and development work together.
This will add the ability to start multiple translations with a single click from a freshly created page.
While currently editors can duplicate pages and simulate templating, with this change we’ll make it easier to start commonly created content like resource downloads, events or blog articles (and its translations) with less clicks based on predefined temlates.
We are working on an Notion-like editor that will replace the current Markdown editors for WYSIWYG experience and ability to add custom formattings like detached styles for semantic headings and additional settings for adding links.
Ability to add discussions in revisions on a page or widget level. With email notifications for mentions and ability to provide approval when reviewing content before publishing it to the users.
We are also expanding the presence feature (which currently show indication where there are multiple editors visiting the same page) to also indicate the widget a user is currently editing.
This module will implement a translation memory in the content. Since all the data is kept in a structured and there’s a functionality to mark widget settings for translations the platform will provide an easy way of managing translations. This can also be hooked to translation APIs or translation agency software to automate the process of creating and updating translations without the need of going through the visual block builder.
Currently all websites have the ability to be cached in the edge layer (on Vercel or Google Cloud). While this reduces the chance of DDoS attacks and makes for extremely fast loading times it limits the ability to create personalizations. By adding this cache all non-user based personalizations can happen in the data hook layer and cached while providing additional ways of augmenting the content before serving it through the widgets.