[BD-14] Orientation Note
- Connor Haugh (Deactivated)
With regards to you reaching out to work on Problem editor stuff,
There are three components that are needed to meet our current specifications for what makes up our intended “visual Editor”. The eventual goal is to synthesize these three components into one whole.
The first component is the V2 content Editors framework, which provides learning-context agnostic MFE support. This framework loads, saves, and navigates features for xblock editors. We have already utilized this framework for our work with the new Text and Video editors.
The second is a set of two reducers: one translates OLX into a javascript object (for the visual editor to pull from); the other does the inverse operation (for saving). This is the work that we believe is in scope for you, as it should start from the reducers written for the existing opencraft visual problem editor.
The third is the set of UI views and features which comprise the editing experience. We usually begin this kind of work with a “skeleton“ of the required React components.
As stated before, the eventual goal is to synthesize these three components into one whole. In order to best leverage the existing processes our team has in place, we want to spec out the skeleton for the UI container and its components in order to provide you with a reducer “contract” we are sure meets our needs. We estimate that we will complete that specification by Friday, June 24.
In the meantime, here are some resources for you to gain context on where we stand and where we are going. I feel as though we will need to establish some collaboration model to get this work done as well, so let me know what works best for you in that regard.
Best,
Connor
Resources:
An Intro To V2 Editors From OpenedXCon
Existing Editor Library, with close-to-code documentation