In this guide:
- How will Editor improve my workflow efficiency?
- How will Editor increase my team's collaboration?
- What are the design best practices for Editor?
- Who would make a good Editor role?
- What are the use cases for Editor?
- What are use cases to avoid when using Editor?
- How do I prepare to incorporate Editor?
How will Editor improve my workflow efficiency?
Editor is a powerful tool in the Ceros ecosystem that allows your team to quickly and easily update and share experiences without even opening the Studio. Team members in the Editor role (typically non-designer roles) won't have to rely on and wait for Creators (typically designers) to make experience updates; they can do it themselves.
By being able to update any text or image in an experience, Editors will have a seat at your team's creative table. Your team's interactive content will be more scalable, and Creators will have more time to create, design, and publish original Ceros content.
Essentially, Creators use Studio to design and publish original content, while Editors use Editor to make changes and updates to the original content. Creators won't have to worry about Editors altering the core logic, layout, or design of their experiences. Meanwhile, Editors won't have to worry about designing anything when they only need to make minor changes. The roles work in collaboration to increase creative workflow efficiency.
How will Editor increase my team's collaboration?
Your team can utilize Studio, Editor, and templates to create a collaborative content production process.
A common best practice process would include the following:
- Creators design experiences and save them as a templates
- Editors open a template in Editor
- After making the desired changes, Editors publish the altered template as a brand new experience
Creators and Editors can also collaborate during the initial design process to develop templates that require minimal editing effort. To help do so, here are some important aspects of Editor to keep in mind:
- Editor enables users to update any text within a textbox, but they can not rearrange or resize the textbox itself.
- Editor enables users to change the font weight and color of text within a textbox, but they can not change the actual font.
- Editor enables users to swap out any image in an experience, but the new image must be the same size or larger than the original.
- Editor does not allow users to reposition, scale, or crop a new image.
What are the design best practices for Editor?
With the above aspects in mind, here are some quick design best practices when creating content for Editor:
- Allow enough breathing room, or white space, between assets on a page to account for longer textboxes. Though Editors can't resize fonts or reposition textboxes, Editor will automatically extend a textbox's bounds if additional lines of text are added. So, if Creators don't allow enough breathing room, they may run into issues with the longer textbox overlapping with other assets on the page.
- Size buttons and thumbnails appropriately. Like the first tip, consider breathing room when designing buttons or thumbnails that include text.
- Add all of your brand colors to the experience. Though the experience may not incorporate all the colors, adding them to its color palette will enable Editors to use them as they like. When altering text color, Editors are bound to the colors included in the experience's color palette.
- More extensive changes, like adding additional images to a carousel or removing assets, will require more hands-on collaboration from Creators.
- As with all scaleable design content, make sure to provide Editors with a brand guide to ensure proper asset usage and brand cohesion.
Who would make a good Editor role?
Designers, or those in a design-oriented role, are the perfect candidate for the Creator role. For the Editor role, some common, non-designer personas include:
- Internal Communicators
- Enablement Managers
- HR Managers
What are the use cases for Editor?
How your team will use Editor will depend on the content you plan on creating. Simpler experience designs will allow team members in the Editor role to work more autonomously, while more complex experiences will require more collaboration between Editors and Creators when making updates.
Regardless of how your team will you Editor, here are some common content use cases:
- Sales collateral
- Marketing content
- Case studies
- Landing pages
- Event collateral
- ABM pieces
- Recurring pieces
- Content requiring localization
- Industry/product-specific variants
- Product marketing
- Content that will go through versioning and variations
- Internal comms
- HR-specific content
What are use cases to avoid when using Editor?
As mentioned above, your team's Editor use cases and collaboration will depend on the content you plan on producing; however, here are some use cases to avoid when wanting to create easily scaleable content:
- Multipage experiences that require logic or layout changes
- Multipage experiences that require page re-ordering
- Experiences including quizzes
- Experiences including embedded objects that require swapping out
- Experiences including a lot of hidden content
- Experiences including complex data visualization
How do I prepare to incorporate Editor?
Your Ceros Customer Success Manager is prepared to help you incorporate Editor specifically for your needs. Reach out to your CSM to start planning for Editor. In the meantime, here are some questions to get you started:
- Who, or what team, in your organization will lead in creating and maintaining templates for your Editors? Think of someone who has a firm understanding of your brand guidelines, preferably a Studio user.
- Who, or what team, in your organization can ensure the templates created for your Editors are accessibility-friendly?
- Who on your team or in your organization would be a good candidate for the Editor role? There is no limit to the number of Editors roles your team can have.