What kinds of rules can ProseMirror enforce?
You can define what is allowed in a document. For example, an incident note can require a title before the summary. This rulebook is called a schema. ProseMirror supplies the pieces for representing and editing that structure. You choose how someone inserts a section or changes a heading.
What should your app keep with the document?
Store the document as JSON, which records the content and how its pieces fit together. Keep the schema version and a way to open older versions. If a saved document uses a section type you removed, plan how to read or convert it before removing its definition.
What transfers to a new editor?
The original JSON is a record of your ProseMirror document. A different editor needs rules to understand your custom sections. If you make an HTML export, define how each custom section becomes page markup and check what the receiving app keeps. Your app must also preserve any separate files the document references.
What does your team maintain?
Core modules such as the document model are MIT-licensed. Plan for assembling the editor, storing documents and maintaining the schema and controls as the app changes.
How would you plan an incident-note template?
Use a fictional delivery delay. Draw a title, a summary and an optional follow-up. Keep this exercise on paper.
- Draw the allowed structureDecide where follow-up belongs and whether a summary may contain another heading.
- Draw the conversionImagine replacing Follow-up with Next action next year. Decide how you would reopen a saved note written before the change and how another app should display its text.