Next Generation Authoring FAQs
On this page we've included the answers to some common questions about using the Next Generation Authoring (Beta) release.
We're fixing issues as you feed them back to us. See the section, .
You can find a list of at the end of this page.
Common questions
How do I get Next Generation Authoring features?
You can benefit from the new 'look and feel' of the enhanced content authoring straight away just by switching it on. Learn about the .
To get additional features, your developers will need to make changes to your content type schemas. Discover .
Why is Next Generation Authoring already switched on?
Your organization has the option to turn on the new content authoring experience by default for all users. See .
How can the authoring experience be optimized?
Next Generation Authoring offers developers features, such as tab and grid layout, customizable components and content palettes, that they can use to .
Can I switch between the new and previous authoring modes?
Yes, during the beta release you can switch Next Generation Authoring on and off. We encourage you to switch to our next generation of content authoring and take advantage of the benefits it offers. See .
Why doesn’t drag and drop work all the time?
Sometimes if the items in your list span the full height of your screen then you will need to use the combination of click and mouse/trackpad to activate the drag behavior.
Will the new features work with the previous authoring experience?
Mostly, yes, Next Generation Authoring features can be used in the previous authoring experience. See the section.
Why am I being asked to save when I haven’t made a change?
One reason could be that your developers have changed the underlying content type schema. Simply save your content and continue.
Known issues
Why can’t I create complex conditional scenarios?
We don't currently support all of the features specified in the JSON schema conditionals reference. We've provided examples of .
We may extend our support for conditionals in the future. To help us identify which features would be most beneficial, please send us your feedback. See .
Why am I being notified of missing “_meta” on required fields?
Differences between how Next Generation Authoring and the previous authoring experience handled required fields, mean that in some cases you are notified that the "_meta" property is required on fields. We are working to resolve this very soon.
Limitations
Next Generation Authoring is designed to be compatible with our previous authoring experience and with your existing schemas and content. However, in some instances it may not be possible for the previous authoring experience to fully adapt to next generation features:
The previous authoring experience is not shown correctly
This is probably because you're trying to open a content item that contains these Next Generation Authoring features:
- Conditional fields
- Tabs
Tab and grid layouts
Content types with next generation tab and grid layouts will re-adjust to a single list of fields when you switch them to the previous authoring mode.