Migrating your stacks

This document is not finished… It will provide examples on how to convert a stack into a native Element Component.

This document only applies to existing developers that build stacks for RapidWeaver Classic. If you are a new developer to the Elements platform you can safely ignore this document.

To convert classic stacks to an Element Component it will unfortunately need to be re-written. However, once you get familiar with how the properties JSON file is constructed, you'll find converting your stack info.plist into this new format is fairly straightforward (and much more enjoyable to work with).

Porting your stack(s) over to Elements will also give you the chance to bring it up-to-date, making sure it's fully WYSIWYG, and uses the built-in Tailwind CSS theming system.

You can learn more about why your converted stack must use Tailwind CSS in the Component Styling section of this manual. We also recommended reading the Design System section of this manual.

Stacks to Elements Component Checklist

To give users a seamless experience when using built-in and third-party components you should ensure the following:

• Component is fully WYSIWYG in the Elements Editor

  • Settings and Admin options are not visible in the Editor (place these in the Inspector)

• Component uses Tailwind CSS

  • Uses the Tailwind classes found in the Theme Studio

  • Takes advantage of the Theme based UI controls

Developer Support

If you have questions about porting your stack to Elements or building a new component please visit the Elements Developer Forum. We're also happy to arrange a video call to give one-on-one support with converting or building your components.