> I think this move was a mistake. They've thrown away the benefits of a incredible wiki-based platform Ideally, you want to cater to both the CLI centric work

> I think this move was a mistake. They've thrown away the benefits of a incredible wiki-based platform Ideally, you want to cater to both the CLI centric workflows of developers/build-systems and the WebUI centric workflows of everyone else (the old system). The Mozilla blog posts mention the JAMStack so I'm guessing that the intent was to port the server-side Django apps/editors to a browser-side framework like React or one of its alternatives. If the design and implementation of the new platform was perfectly executed then only the new functionality would be apparent; both systems are essentially "wiki-based". Platform transitions are rarely seamless as your lost content/metadata clearly shows.