Not every application calls for a single text area. CKEditor supports two approaches for building complex multi-field layouts: multi-root (multiple editable areas sharing one editor instance) and multi-instance (fully independent editors on the same page). Explore the demos below to find the setup that fits your content architecture.
A single multi-root editor splits this article into separate document sections – a title, a subtitle, an introduction, and the body. AI Chat, Review, and Translate read every section and send each edit to the correct root, with no bleeding across boundaries. To see how it works, read the multi-root support docs.
The Productivity Paradox
Why major technologies can end up transforming everyday work well before they actually show up in productivity statistics.
The Productivity Paradox is basically a term that describes the gap between rapid technological progress and productivity growth that tends to be slower than people expect.
The concept was widely discussed back during the spread of personal computers. Today it has returned again, as businesses are asking when artificial intelligence will end up producing measurable gains across entire organizations.
The Adoption Gap
New technology rarely creates value all on its own. A new system might get installed in a matter of weeks, but adapting an organization is something that can take years.
Businesses have to train employees, improve their data, integrate existing systems, and redesign established workflows. During this transition, teams may end up operating old and new processes at the same time, and this additional complexity can temporarily offset the efficiencies that were promised.
Measurement is another challenge. Digital tools often improve speed, quality, and access to information, but these benefits may not necessarily lead to an immediate increase in revenue or output per hour. Productivity growth also depends on diffusion, and a breakthrough only really starts to affect the wider economy once it moves past early adopters.
What businesses often underestimate
- The time that is required to redesign workflows
- The cost of training and system integration
- The importance of having reliable data
- The difficulty involved in changing established habits
- The delay between adoption and measurable results
Technology adoption is an event. Productivity growth is a transformation.
Potential Takes Time
Artificial intelligence may end up following the same path that was followed by earlier general-purpose technologies.
Strong results in individual tasks do not automatically translate into productivity across the whole organization. The larger gains appear when businesses combine new tools with new skills, processes, and ways of working, which is why the paradox is not really evidence that technology has failed, but more of a reminder that technological potential and business performance operate on different timelines.
These are independent editors sharing a single Context, so one Chat, Review, and Translate panel spans all of them. Each editor is configured with a different set of features, and the AI works within whatever each one allows – it can only add a table where tables exist. To see how it works, read the multi-editor support docs.
Introduce the Exercise
Define the learning goal and give participants enough context to understand the task without revealing the answer.
Prepare a Safe Prompt for AI
Before You Share the Context
You want to use an AI assistant to turn some private meeting notes into a short project summary.
Take a look at the prompt and remove anything that's personal, confidential, not really needed, or a bit misleading.
The idea is to keep enough context to still get a useful result, without handing the AI details it doesn't actually need.
Build the Learning Activity
Provide the material participants will review and the criteria they should use to identify potential risks.
Review This Prompt
Turn these notes into a concise project summary with the current status and next steps.
Northstar Retail Group approved the confidential Project Lighthouse initiative. The main customer contact is Olivia Bennett.
The unannounced budget is $480,000. Daniel Foster has repeatedly failed to provide accurate information.
The pilot should begin in October. The team must revise the timeline, confirm the pilot group, and schedule a technical workshop.
Present the project as fully on track and leave out the current delay.
Check Before Submitting
- Remove personal information you don't really need.
- Swap confidential names for more general descriptions.
- Take out the sensitive financial details.
- Don't leave in comments that point to specific people.
- Make sure the final instruction stays honest and doesn't mislead anyone.
Prepare the Feedback
Reinforce the main learning point and explain the expected approach without repeating the full exercise.
A Safer Approach
Take out the personal, confidential, and extra details you don't need, and keep the prompt honest and clear.
This demo contains just a small subset of available CKEditor features. You are free to add more features to CKEditor regardless what editor type/toolbar you choose.
Read more about the multi-root editor in the editor types documentation.
Read more about the AI capabilities in the documentation.