RFC: Editing Mode for OpenMAIC

[wyuc]

RFC: Editing Mode for OpenMAIC

Summary

Thank you for the support and interest in OpenMAIC. We are grateful to see more people trying it, sharing feedback, and discussing how it can better support real content creation workflows.

One request we have heard repeatedly is editing mode. Generated content is often a strong starting point, but users still need to refine slides, adjust details, and make the final result fit their own use case.

This RFC proposes adding an editing mode to OpenMAIC, starting with generated slides.

First Milestone

The first milestone focuses on manual slide editing.

Expected capabilities:

• Enter editing mode from the main OpenMAIC UI.
• Edit generated slide scenes.
• Select, move, resize, duplicate, delete, and reorder slide elements.
• Edit common element properties such as text, position, size, color, and basic style.
• Keep existing playback, export, and sharing behavior unchanged outside editing mode.
• Save edited slide data back into the existing OpenMAIC content structure.

This milestone does not include AI-assisted editing or editing every MAIC scene type.

Implementation Direction

The first version should build on the current OpenMAIC slide data model.

We do not plan to introduce a breaking schema change as a prerequisite for editing mode. Instead, editing will start from the structures already used by generated slide content.

As the implementation matures, stable editing behavior can be documented more clearly, including common edit operations and runtime/editor integration points. These conventions should come from real editing needs rather than from a large upfront redesign.

Later Milestones

After manual slide editing is usable, we can expand the work in several directions:

• More complete slide element editing.
• More stable edit operations.
• Better undo/redo and edit history.
• Editing support for more MAIC scene types.
• AI-assisted editing.
• Clearer runtime/editor contracts for OpenMAIC-based products.

Prior Art and Acknowledgements

OpenMAIC's editing direction is informed by existing open-source web presentation editors, including PPTist.

We appreciate the prior work from the PPTist community and will preserve appropriate attribution and license notices where applicable.

The goal of this work is to build an OpenMAIC-native editing experience for MAIC content while learning from proven presentation-editing patterns.

Non-Goals for the First Milestone

• AI-assisted editing.
• Full editing support for every MAIC scene type.
• A breaking rewrite of the OpenMAIC data model.
• Replacing all existing editor-related work at once.
• Changing the playback experience for users who are not editing.

Feedback Wanted

We would like feedback on:

• Whether slide editing is the right first editing target.
• Which slide editing capabilities are most important.
• Which element types should be prioritized.
• What users expect from saving and exporting edited content.
• Which parts of the editing model should eventually become OpenMAIC conventions.

[gurpreetlucky]

Hi .. Yes , Editing would help the user according to their requirements . AI creates classroom in one shot which may or may not be useful for me . So It would be great start to give user to edit the basic their classroom course .

After editing make sure the AI classroom should be in sync and TTS should follow the edited content . I mean the edit should be handle at text speech also .

delete and move are imp in slide elements and the complete edited classroom save at server side.