Feature Requests

Could you please add full Arabic support for the "Character" Text Effect? Currently, Arabic text does not render correctly It would be great to see proper support for right-to-left (RTL) languages like Arabic in this feature. Thanks for your support!

Allow users to password protect individual pages, rather than entire sites.

It would be super useful to have support for variables, similar to what Figma offers. Being able to attach specified values to things like padding, gap, or basically anywhere that allows a numerical input would enable a lot of systematic structure that's currently not natively possible. It could work similarly to how text style sizing works, where its possible to define a size based on the breakpoint. Variables could allow for a layer of abstraction in defining consistent system-wide values, such as "padding-large" being set to 128px on desktop and 64px on mobile, for example. This would make updating values across all pages much easier.

It could be really cool to add support for more viewport units (svh,lvh,dvh).

Ability to publish specific CMS items and standalone pages (instead of the whole site), as well as scheduling deploys for a later date.

When we need to create responsive variants with some functionality, variant count goes out of hand since we need to recreate the functionality for each breakpoint. If there was a way to control breakpoints in components separately from functionality, we would would dramatically reduce the number of variants and it would be much easier to update the functionality later once instead of having to remember to update it for all other breakpoints.

It would be helpful to have an option to remove all redirects at once. Currently, redirects need to be deleted individually, which can be time-consuming when managing a large number of them.

// Problem Currently, when creating repeatable content within a page (e.g. lists, sliders, or structured sections), we have to manually define multiple fields like: Item Text 01 Item Image 01 Item Text 02 Item Image 02 Item Text 03 Item Image 03 This approach becomes difficult to scale, harder to manage, and less flexible for dynamic layouts. // Existing Workaround Using CMS Collections helps in some cases, but it’s not ideal for repeatable sub-sections within a single page (e.g. feature lists, slider items, or modular content blocks that belong to one page rather than a collection). // Proposed Solution Introduce repeatable variable groups (or “nested repeaters”) that allow users to: Define a group (e.g. “List Item”) with fields like: -- Text -- Image -- Link (optional) Add/remove/reorder instances of that group dynamically Bind these groups directly within page-level variables or CMS entries

Ability to schedule a blog post or any other CMS content to only be published / taken off at a specific date