User blog comment:MisterWoodhouse/The first migrations to the Unified Community Platform/@comment-1807002-20200527192933

The UCP source editor is still a nightmare, how can we be considering migration. With a js source editor css affects it which is awkward and painful, on the test wiki it is pretty much unusable for me. The ucp js source editor imo has to be sorted before any migration.

This is very upsetting for I thought we were being listen to (I was reassured over and over again) and many are giving feedback on how bad the source editor is and soon I'll be force to use it- or not use it... since so far it has been borderline unusable for me (I have to use a non-ucp wiki to edit copy and paste into ucp source editor).

I'd be even more upset but I have been discouraged lately to edit- so my edits are minimal atm. I just thought we'd have more time, and see our top priorities (after bug fixes) be addressed, and the js source editor has not been (that I have seen) fully discussed nor plans for fixes yet.

Just doesn't seem right to migrate without a decent (source) editor. I think this is a mistake for the UCP without a better source editor first.