For "rich" content, particularly journal article-style pubs, we want to expose some kind of rich editor for string fields. This editor should include most of the functionality currently available to PubPub users (does not need to be real-time/multiplayer to begin with).
Why
Support Vanderbilt contract
Support Legacy to Platform migrations
Better demos to prospective clients
Assumptions
The editor will maintain the latest state of a single field of a Pub
For certain elements that should be children or siblings, the editor will hook into the API to create child pubs and render them where needed
The editor doesn't need to be collaborative to start, but should have a path for supporting it in the future
The editor is just one potential editor, essentially a "view" of a string field.
Open Questions
We want to support annotations both within this editor and for external content. Those annotations will create new child pubs. Is there a way to make this annotation process the same or similar for internal and external users?
For "rich" content, particularly journal article-style pubs, we want to expose some kind of rich editor for string fields. This editor should include most of the functionality currently available to PubPub users (does not need to be real-time/multiplayer to begin with).
Why
Assumptions
Open Questions