Integrated editor - Frontend

Description Supports DITA authoring formats; DITA-OT implementation pending. Platform Status: partially implemented PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Notes DITA OT Not implemented yet Format implemented Is your DITA-OT out of the box or configure and customised. Currently authoring in DITA, don't want a different format. Product Owner Notes Not implemented DITA-OT Notes: DITA OT not implemented yet; implemented format; clarify OT configuration; maintain DITA authoring.

Description Platform Status: in roadmap PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Notes Plans for external editors (plugin) or integrated (bespoke) editors Oxygen or built in bespoke editor. FE team has done an investigation for building in house XML editor. Baseline editor, should feel familiar to oxygen (a bit slimmer) Narrowing down was done in conjunction with Product Team (Johan Elisson). Get a very clear list of feature requirements of an XML editor from AGCO. Add to roadmap and attach feature requirements and test criteria. Guide the users through the process of adding a "f.x." a hazard statement. Instead of adding markup (conref) directly in to the XML elements. Editor view that allows to right click, select ID, preview, then insert the conref and get a preview (in document) pulled from source element. Very UI driven. Helps with validation, instead of text based. Product Owner Notes Oxygen Need support for resolving graphics and maybe reuseable components.