Title: Flexibility required…
Last modified: December 13, 2018

---

# Flexibility required…

 *  [David Edwards](https://wordpress.org/support/users/scripturegeek/)
 * (@scripturegeek)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/flexibility-required/)
 * Not being one to knock a new interface, especially when it has some obvious improvements
   for new users, I do have some recommendations for future updates. WordPress is
   used more and more by web designers because they can offer their customers a 
   non-frightening option. With that in mind the average web designer can easily
   navigate html. As such a person, I find it an irritation not being able to switch
   between the two editors. I like to build it then tweek it. Often cutting and 
   pasting html snippets I have in my bag. Now I have to find the correct list to
   be able to switch over. This is a real time waster.
 * One of the other concerns I have about this upgrade is that it is steering away
   from the basic concept of WordPress. WordPress is meant to be a useful framework
   to hang your options upon. I feel the editor should be a plugin that we choose
   or reject. I feel on install, WordPress should ask you what editor you would 
   like to use and recommend the preferred plugin. More like the way Themes are 
   handled. Create a page that allows you to select and install your editor, keep
   it so you can switch between them as you try them out. This way the end users
   can vote with their feet.

Viewing 1 replies (of 1 total)

 *  [stinkykong](https://wordpress.org/support/users/stinkykong/)
 * (@stinkykong)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/flexibility-required/#post-10983291)
 * Thank you for your civil tone at at time where users’ anger appears more important
   than reason. It’s hard for me to understand anyone not knowing what they were
   getting into with so much dialog going on about Gutenberg for months and months
   and months.
 * In general, people should have a back-up and restore plan always prepared and
   of course, not after the fact. So if someone were to inadvertently update, they
   could back out of it on their own whether this were a core update, a plugin or
   theme, server being hacked, or whatever. Is this not right?
 * Additionally, there are plugins available to restore the old way, the Tiny MCE
   editor. We know even now that will end sometime so now is the time to start adjusting.
   We have plenty of time.
 * I must admit that I have had frustrations with Gutenberg but also enjoy a lot
   of what it is offering. So I’m convinced this is a growing experience. I’m not
   on fire about how good or how bad it is but it is the way WordPress is heading
   and anyone can choose the way they want to approach this, directly, head-on, 
   or in a meandering way… which ever way suits them. WordPress has been hugely 
   generous with time, development work, consideration, as well as communication.

Viewing 1 replies (of 1 total)

The topic ‘Flexibility required…’ is closed to new replies.

 * ![](https://ps.w.org/gutenberg/assets/icon-256x256.jpg?rev=1776042)
 * [Gutenberg](https://wordpress.org/plugins/gutenberg/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/gutenberg/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/gutenberg/)
 * [Active Topics](https://wordpress.org/support/plugin/gutenberg/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gutenberg/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gutenberg/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [stinkykong](https://wordpress.org/support/users/stinkykong/)
 * Last activity: [7 years, 9 months ago](https://wordpress.org/support/topic/flexibility-required/#post-10983291)