Page Builder Product Roadmap

Ability to create drag and drop menus and sub menus based on tag selections.

Preview mode sometimes doesn't show a 100% accurate component reflection as occassionally a style drops out.

The image upload process needs a more user friendly overhaul. Obvious issues at the moment are:

1. You can't crop an image within the system to the correct aspect ration. This has to be done outside of the page builder.
2. There is no folder structure visible so you can't choose a previously uploaded image, resulting in multiple versions of the same image on the drive
3. For larger images there is no progress bar to see if the image is uploading or not.

The plan is to remove the src field on the image component and replace it wih a select image button. You will then be able to:

1. upload a new image and choose an aspect ratio to crop the image to
2. select an existing image to add to the canvas from what is already uploaded to your library
3. see a progress bar for images being uploaded as an indication the upload is working

Ability to finesse mobile version of components with some differences to the desktop version of the same instance.

TinyMCE has gotten expensive and the facility it provides isn't as true a WYSIWYG experience as we would like to offer. The plan is to swap it out for a Notion style editor where the content blocks better reflect what is on the page.

Use of the WYSIWYG should be a last resort for text formatting (adding links, small areas of bold) or for large blocks of text such as a news article that isn't broken up into multiple sections or components.

We want to provide an editor that give the best user experience whilst also reflecting how the text will look on the published page

Ability to copy and paste a comonent into the same page.

This is a work in progress that will hopefully be released this year.

Although we can create templates manually nd register them to the code, it would be good if it was possible to build a template within a page and have it available in the left menu for future use.

As the components are usually registered on program build there may be some complexity with achieving this, but we are looking into it.

Based on the idea of having a container and pressing a button to add or remove columns, making it easier to have a 1,2,3 or 4 column layout.

Work in progress to get the CSS to duplicate more efficiently.

Linked to issue with double scrollbar above. If we fix one we fix both.

The editable text component is great for updating a set of text where the style shouldn't be changed and is nested into another component. However users wanting text are better off with the flexibility of the text wrapper component. Both exist in the menu which is confusing, so removing the editable text from the menu would remove this confusion.

Colour choices should be limited to the theme or branding of a website to keep things consistent. Adding limited colour buttons makes choosing the colour more efficient and consistent. For flexibility the last colour button should open the colour picker so it stil remains possible for users to choose other colours, but attempts to steer towards staying on brand.

As more features are added, users will need more initial help with building pages. A series of short videos can help as an additional training resource.

Some websites will need a lot of custom components making the left hand list get longer and harder to access on laptops. This will become more of an issue if users can create their own components. We need a better UI to search, select and drag components from a menu.

Low priority

Low priority

All image components will have the option to upload a mobile alternative image.

Useful for news/blog articles to differentiate from the creation date of the page as it may not be the same as the publish date.

To differentiate from browser title. For instance a page called home page should have an SEO friendly browser title, but the browser title doesn't make it easy to find the page in the pages list.

Currently supporting em / rem. Want to provide the option to also support pixel.