In reply to Adevou Fera.

Right now, Gutenberg is wholly encapsulated in a plugin. It needs to remain that way for at least another year rather than become part of WP Core in that year. It can currently be installed, activated, deactivated and deleted like any plugin. This is the ideal scenario for a plugin with such functionality as Gutenberg provides.

However, it seems that it's not that likely to remain in plugin form for very long as we enter 2018. Instead, people will be required to install a plugin to disable Gutenberg instead (which already exists) to revert their site to it's pre-Gutenberg state where necessary. While it's a pretty backwards approach IMO, there's also no need for 2 versions due to WP's modularity.