New Edit Content
My team laid its foundations: research, planning, the architecture and the base of the design. Then the project went to another team, and we started UVE.
Why it exists
The old editor was a JSP screen that opened from all over dotCMS: Content Search, Pages, the Site Browser, Tasks. The new one is its own Angular library, so every one of those entry points had to learn which editor to open.
Key decisions
-
Behind a feature flag
The new editor shipped behind a flag that could turn it on for every content type or only some, so it could grow next to the old one without breaking anyone's work.
-
The first fields
I built the first field types on the new base: text and text area, the calendar fields and tags, with tests for the shared utilities.
See it work
The hard part
We built it expecting to finish it. When it was handed over, the foundation had to stand on its own for the team that came next.
Where it is now
Another team carried it on from that foundation, while we moved on to UVE.