9 Comments


  1. Hi Jeff
    “Can you see yourself using it as the primary method of creating content?”

    Not at the moment for the same reason you mentioned earlier…

    “I’m so used to creating content from the backend, it’s tough to imagine doing it any other way.”

    Plus working in the backend is no great hardship.

    I write all my posts on a local copy of my site and then cut and paste into the live site when everything is finished – change the image URLs and I’m done.

    Reply

    1. Great article Jeff! Keith i think that plugin will benefit new users the most i train people on using wordpress all the time and it very common for me to have to explain the difference between the front and back end repeatedly and even myself and i am very comfortable using the backend editors will often find myself toggling between a front and backend tab when doing certain posts.

      Reply

  2. In my opinion a front end editor will appeal mostly new WordPress users, and also non technical users that come from a traditional office background. Many people are used to MS Word and WYSIWIG editors and they simply find unnatural having to write a text and not knowing exactly how it will appear to the reader while they are writing it.

    Reply

  3. I think my novice writers will like it a lot.

    Works well for editors too, I can easily read and edit a story live.

    Can’t use it yet on my main site though, some conflict causing it not to load right. Hopefully we will get that figured out. I’m very excited about getting it going.

    Reply

  4. I can see the usefulness of this even for more experienced users, the formatting of content / images can often change dramatically between the backend and the theme in use on the frontend & you don’t want to keep switching between the two to see how paragraphs etc line up. Also, as mentioned in the article, typos that get past initial proof reads can be fixed one step quicker, which always helps :-)

    Reply

  5. I feel this is a great feature! Very useful!

    While writing lengthy articles can be done at both ends, I found it very practical to correct typos or change words and phrases, some things you just see later and easy improving and finetuning is a big help.

    Also having a two column setup and pictures (a successful first test made with page builder which shows you just blocks in the backend) and creating the balance between texts and pictures feeling just right is much easier from the front-end. While one can live with a lot I found eliminating the constant cylce “switch from back to front and back” a blessing!

    Obviously I used WP now for 4 weeks only and am not a professional writer.

    I vote for core integration!

    Thanks for your efforts!

    Reply

  6. From what I can tell most people responding are “single blog” people.

    But the problems of the WP core back-end are manifest when you run a theme.. such as a Directory, Classifieds, Real Estate, Vacation Rentals, etc.

    Where Users are permitted to self-register and to control their own posts — ads, rentals, for sale properties, etc.

    All of these commercial themes switched several years ago to customized Front End forms for creating and modifying posts. The User is redirected away from the “ugly” WP Dashboard in the WP Admin path. The User interface now exists inside custom forms and they never see the WP back end.

    But, every single WP plugin must be administered in the core back end if it has User menus and sub-menus that alter the content of a post.

    There is no way for a User (lesser roles than Admin) to utilize plugins that can only be seen in the WP core Admin dashboard.

    I have a calendar plugin for Rental Bookings and Availability that offers the User (owner of posts) many options for creating and embedding their own calendars and reply forms into each post (rental type) they create. Unfortunately, my users have no access to these fine features because the plugin, as all WP plugins, can only be used in the WP backend. And the theme directs them away from the default backend.

    Many new plugins can be written IF the back end options and settings can also show up in a custom front end.

    If a plugin is installed that shows a menu and sub-menus to an Author role in the Wp Admin Dashboard then those tabs ought to be replicated in the User front end of any well built theme template. All back end functions that a plugin bestows upon a User ought to automatically be made available in a Front End menu, too.

    Reply

Leave a Reply