Dec 062018

If you haven’t heard, WP 5.0 featuring Gutenberg is here. If you haven’t had a chance to form your opinion about it, do ensure that you download a copy of the “Classic Editor” plugin to recover from any shock caused by Gutenberg. Displaying behaviour that has been symptomatic of Gutenberg all along, I will move my sites to WP 5.0, but I will keep my wife on 4.9.8 before things stabilize. I will additionally install Classic Editor because the new WP 5.0 text editor is just too crippled, and Gutenberg suffers from an exceptional amount of bloat.

Having said the above, here is Photonic version 2.12 to go with WordPress 5.0.

  1. Magnific Popup Support:
    People are usually concerned when they have 13 of something. Well, for those superstitiously minded folks, here is cause for concern: Photonic has added support for its thirteenth lightbox – Magnific Popup. Unlike PhotoSwipe (which is also from the same developer), Magnific was a lot easier to code for, and was reminiscent of some of the easier coding I have had to do for Photonic.
  2. New Features / Changes:
    This release features a number of small additions / changes:

    1. I have moved the “Lightboxes” options from under Photonic → Settings → Generic Options to its own header, Photonic → Settings → Lightboxes.
    2. Consequently I have added a lot of customization options to the lightboxes, and I will continue adding more over the next few releases.
    3. I have added the capability to launch a lightbox from a slideshow. Currently this works only if your lightbox is LightGallery or Magnific, but I will be expanding this feature.
    4. There is a new option to remove the photo count from Google Album displays, under Photonic → Settings → Google Photos → Hide Photo Count in Album Title Display.
  3. Bug Fixes:
    1. In some cases slideshows were not stretching to the full width. This should be working now.
    2. There was a bug in the interactive flow that was causing a zero-impact JavaScript error while trying to create a new gallery. This has been patched.

Hope you enjoy the new release.

Nov 262018

I have released version 2.11 of Photonic with the following changes:

  1. JavaScript Optimization
    When Photonic started out in September 2011 it only had support for two lightboxes – Colorbox and Fancybox. About a month later I added support for PrettyPhoto, and then for a long period of time I didn’t add anything else. About 4 years later I added support for Swipebox, and I haven’t looked back since then, adding multiple lightboxes and amping up the capabilities of each script. During this process though, the core JavaScript file for the plugin kept getting bigger and bigger. Finally when I added support for PhotoSwipe last month I realized how big the JavaScript had become, and at that point I had to take stock and do some rewriting.

    So, in this version I broke down the core JavaScript and primarily separated each lightbox script into its own file. The net result was a reduction in size of almost 45%!

  2. Bug Fixes
    1. In the previous release I had made a change to have Flickr calls within a collection be executed in parallel. This had a side-effect: the sort order of albums in a collection stopped being respected. This should be fine now.
    2. There was an undetected bug since a long time: Instagram image sizes were being hardcoded, resulting in weird displays. This has been addressed.
    3. The interactive gallery creation flow had a bug that was causing it to crash for PHP versions < 5.5. This too should be fixed now.
  3. A small change I have made is to make the “display link” for Flickr be a little more “specific”. E.g. If a photo is in an album its link in Flickr will be specific to that album instead of the user’s photostream

Hope you enjoy this release. As always, if you are enjoying the use of Photonic please leave me a good word as a plugin review.

Nov 112018

WordPress 5.0 is on the horizon, and nothing in WP history has faced as much backlash as the inclusion of Gutenberg in WP 5.0 core. While the powers that be in the core development team portray Gutenberg as the light at the end of the tunnel, an overwhelming number of developers and users are of the opinion that the light is that of an oncoming freight train rather than one of hope.

I have written about my initial impressions about Gutenberg in the past and I will not endeavour to do so again. I do want to voice my disappointment with the poor quality of support and documentation around Gutenberg, though. On the one hand WP wants everyone to embrace Gutenberg with open arms. And on the other, it has made it extremely difficult for advanced plugins to operate with Gutenberg. Issues and support queries go unanswered for weeks if not months, there are JS errors that pop up in the JS console, and the code doesn’t do what the documentation says it should.

In any case, Gutenberg WP 5.0 is scheduled to be released on 27th November, and if it does, well, that is what this post is about. Version 2.10 of Photonic has just been released and this is what is included:

  1. Gutenberg Support:
    Just in case it wasn’t clear from all that I have written above, this release has Gutenberg support. Do see the documentation before you attempt to use “Convert to blocks” though. Also refer to the dashboard menu item, Photonic → Prepare for Gutenberg.
  2. Shortcode Replacement:
    Gutenberg implementation necessitated that users should be able to change existing Photonic-specific gallery to another shortcode before attempting to “Convert to blocks”. For this purpose there is a shortcode replacement utility bundled under Photonic → Prepare for Gutenberg.
  3. Advanced Settings:
    I have added a new sub-section under Photonic → Settings → Generic Options, called “Advanced”. Under this:

    • I have moved the SSL and performance logging options there.
    • I have added an option to increase the cURL timeout for cases where the connection between a server to the photo provider is slow.
    • I have also added an option to turn on debug tracing. So far this only helps print out the entire response in the interactive workflow.
  4. I have put in some performance optimization to make calls to Flickr collections in parallel. This helps reduce the time taken to fetch a collection.
  5. Bug Fixes:
    The following bugs have been fixed:

    • The default album search by user was failing for SmugMug galleries. This should be alright now.
    • I have also fixed an issue where the layout='strip-above' setting was not working for the slideshow layouts.

Hope you enjoy this release of Photonic!

Oct 092018

I had to release a quick patch for a minor z-index issue affecting Photonic. The symptoms would only be seen if one were to use the Interactive Workflow for inserting a gallery, where the gallery would suddenly disappear under a translucent overlay. There is no impact to the rest of the plugin due to this fix.

I have also been implementing Gutenberg support under the hood. While the implementation doesn’t seem very difficult so far, the learning curve is exceptionally steep, particularly if one wants to avoid going into ReactJS to build / transpile packages. This is causing a fair bit of trial and error and no small amount of frustration, but I am hopeful of getting this done well in time for the official release of Gutenberg.

Oct 082018

I have released version 2.01 of Photonic a few minutes back. Thankfully my tests for version 2.00 paid off and I didn’t receive any overwhelming bug reports. Correspondingly these are the changes for this release:

  1. PhotoSwipe
    Photonic now has support for its twelfth lightbox – PhotoSwipe. This was a long-pending request which I finally was able to support. PhotoSwipe is rated very highly among developers for being light, modular etc. However my thoughts are different – PhotoSwipe is built to be used without JQuery, and as a result its core size is quite big (41KB of JS). This would be fine if sites didn’t use JQuery, but most WP themes and plugins use it. As a result there is no bandwidth saved by the script for more than 90% of the cases, instead the script ends up being larger than it should have been. Consequently, a lot of things like the lightbox markup are not included in the script and have to be handled by developers implementing the script.

    In any case, despite its quirks almost everything has been supported in Photonic using PhotoSwipe, except for Flickr videos.

  2. Instagram had changed (again) how high-resolution images can be accessed, so I had to tweak the code for the same. Consequently I have removed the explicitly defined sizes for HD images and replaced it with an option, “Largest”. This will automatically pull the image with the highest resolution.
  3. In 2.00 I had added a feature to allow searching for images in SmugMug. Unfortunately this ended up not respecting the album’s native sort order. I have fixed this issue.

Do let me know of your feedback regarding the Interactive Workflow – I would love to hear your thoughts! As always, if you like Photonic and the support you receive, a good review is greatly appreciated!

Sep 302018

After a few weeks of intense development and testing (which always gets exponentially harder when I have to travel internationally for work), version 2.00 of Photonic is now finally available for use. As alluded to earlier this is a massive release. The following are what’s new in this release:

  1. New Interactive Workflow
    This is by far the biggest piece of development I have done for Photonic since the original release – almost 5000 lines PHP, JS and CSS code! On the surface this does a very simple thing: it creates a new button in the editor:
    Add / Edit Photonic Gallery

    Add / Edit Photonic Gallery

    Clicking on the button is what triggers the magic. Unlike the traditional way of fumbling through the helpers to find album ids and folder ids, the workflow does all the heavy lifting for you.

    The traditional way of adding a gallery via “Add Media → Photonic” still exists. The “new way” has multiple advantages in addition to the obvious. For one, even if you are not in the visual editor, you can select the text for the shortcode in the text editor and click on the “Add / Edit Photonic Gallery” button to get the interactive workflow.

  2. Default Users
    As a part of the interactive workflow, one crucial feature provided is that of a “Default user”. This is a feature that has been requested every now and then over the years, and I finally got around to adding it this time. Simply put, if you set up a default user you don’t need to explicitly supply one in a shortcode. This feature is available for Flickr, SmugMug, Picasa and Zenfolio. Google Photos and Instagram don’t need this as they need back-end authentication, so the authenticated user is the default user.

    As a happy corollary of the above, for Instagram you now don’t need to hunt down your user id – the authenticated user’s photos are displayed by default.

  3. Zenfolio Enhancements
    Zenfolio, while having a comprehensive API, has been lacking in several areas. E.g. there is no way to combine a user and a search term in a single API call, which results in there being no easy way to show all photos for a user. There are several other such shortcomings, but in this release I have managed to bridge the gap with respect to several such challenges in addition to providing new features:

    1. Zenfolio recently made the move from HTTP to HTTPS. Photonic has been modified to reflect that.
    2. Zenfolio authentication is now supported. Note that unlike other providers, Zenfolio has a custom authentication process (not OAuth1 or OAuth2). This causes a different looking authentication flow, where, unlike other providers you have to enter your Zenfolio password here. Note that Photonic does not store this password anywhere!
    3. You can now search for photosets for a user using specific text terms or categories. Previously this feature was not user-specific. Note, however, that Photonic has to make multiple API calls to support this, and there might be a performance hit based on how many photosets you have. See the examples in the demo page.
    4. You can also use the photoset_type filter (i.e. Gallery or Collection) for user-specific photosets. See the examples in the demo page.
    5. The kind attribute (i.e. Recent or Popular) now works for user-specific photosets.
    6. The filter attribute is now supported for Zenfolio for filtering photosets by id.
  4. Other Additions / Changes
    1. You can now display photos at a user level and at a folder level for SmugMug galleries. This was earlier only possible at an album level. You can also filter the photos by text or keywords. See the examples here.
    2. I have added the capability to track performance for each gallery (Photonic → Settings → Generic Options → Generic Settings → Performance logging). This is turned off by default to reduce the output added to your page markup. However, please feel free to turn it on to see why a gallery is loading slowly.
    3. For native WordPress galleries you can now set a tile_size in the “Justified Grid” and “Mosaic” layouts.
    4. The download URL for Flickr has been modified to reflect the original image.
    5. You can now disable the visual editor by individual post types. This is useful if you are facing conflicts with some plugins, but not other plugins. This is available under Photonic → Settings → Generic Options → Generic Settings → Disable Visual Editing for specific post types. The thermonuclear option to disable the visual editing capabilities completely still exists (Photonic → Settings → Generic Options → Generic Settings → Disable shortcode editing in Visual Editor)
    6. If a native WP gallery is using additional plugins to add videos to the output (e.g. Media Library Assistant), Photonic can now display the video in a lightbox as a part of the gallery.
    7. I have removed the JQuery Masonry script bundled with Photonic and switched to the one that comes out of the box with WordPress. Note that this is only used for old versions of IE.
  5. Bug Fixes
    1. There was a “short-term cache” bug for Google authentication, which caused a user to see the previous user’s photos for the first 30 minutes after the authenticating user was changed. This should work fine now.
    2. There was an issue where, in the “Random Justified Gallery” layout, there was a visible “pop and realign” happening whenever the “Load More” button was being clicked. This has now been addressed.
    3. Google Photos’ API change that was causing errors while fetching albums due to a reduction of the maximum number of photos that can be pulled has been taken care of.

Gutenberg is not yet supported for now, but very soon it will be. The interactive workflow takes me most of the way for Gutenberg integration.

Aug 302018

Google made an unannounced change to its Photos API on 29th or 30th August, wherein it changed the maximum number of photos returned in a single call to 100 from 500.

Unfortunately this is a breaking change – if you pass a number > 100 the API returns an error … and this affects Photonic. Photonic by default displays the maximum permissible number of photos or albums to minimize API calls, so if you don’t pass a count or photo_count parameter to the shortcode, it will default the value to 500. As a result of this a shortcode that was working until yesterday might now not work. To remedy this you have two options:

  1. Go to the file wp-content/plugins/photonic/extensions/Photonic_Google_Photos_Processor.php, line 52. You will see this:
    'count' => 500,

    Change it to this:

    'count' => 100,

    Save the file, and all your shortcodes will be fine now.

  2. If you are uncomfortable making the code change above you can explicitly define the count=100 attribute on shortcodes for Google Photos. This will take a bit more effort on your part, but will be just as effective

Why am I not releasing this fix myself? I am about 75% done with the big changes that I had talked about last week, so I don’t want to release the above as a patch and disrupt something else unwittingly. It has been included with the next version of the plugin though.

Aug 262018

I love Google and I have several very close friends working for them. But there is one aspect of Google that is irritating: they phase out things without putting an effective transition plan in place, and often without offering any replacement. They did this with Reader (I haven’t forgiven them for it), they did this with Picasa (though they did replace Picasa’s web-version with Google Photos in a painful process), and FeedBurner, if people are to be believed, is surely on the chopping block.

Remember Feedburner? If you don’t, I don’t blame you. The service was a rage in the previous decade, but Google has let it slide into a slow and painful obscurity. Probably the only reason Google still has it alive is that this is a customer-to-customer service that they cannot terminate (as opposed to Reader or Picasa, which were Google-to-Customer). In any case, bugs in FeedBurner have not been fixed since 2012, and no new features have been added since 2010.

As it happens though, this site has used FeedBurner for a while now. But wary of being left out to dry I took the plunge and moved to MailChimp. If you are an “Active” subscriber to this site I have migrated you over to the new email-subscription service. You should almost certainly be receiving this post via MailChimp on 27th August. I have deactivated the FeedBurner link, but if you still receive a second email from the old service, please let me know and I will look into it.

Aug 232018

One of the only criticisms against Photonic is that it is hard to use, with users being required to look at multiple places to construct a shortcode. The criticism is justified, because building a “flow” for inserting a shortcode wasn’t on my agenda when I started out with the plugin.

But Photonic is now going to finish the eighth year of its existence and the plugin has evolved from its humble beginnings to something truly complex and extremely versatile. The thorough but wordy “Media Insertion Screen” does have its limitations both in terms of development as well as usage, and in spite of having a set of “Helpers” the UX is not particularly optimal. I have received direct requests / feedback via the support forum to at least support some sort of a “default user” feature if nothing else, and while I have always been saying that something is in the works, there was no way for me to demonstrate this.

And now, unless some higher priority ad hoc development comes up I am happy to announce that the next release of Photonic will feature a much more friendly way to generate the shortcodes.

To start off, you are presented with a popup that asks you to select the source of your gallery:

Pick your source

Step 1: Pick your source

The first screen is pretty much like the type='...' attribute of the shortcode, i.e. it is the main switch. The fun begins after this. Once you select your source you are presented a context-sensitive set of options:

Pick the Gallery Type

Step 2: Pick the Gallery Type

Above you see the options for SmugMug, but the list changes based on the source. E.g. for Flickr you can pick a collection, for Zenfolio you can show a group hierarchy etc. The cool thing now is that rather than describing via words what combinations of view='...' can be used with what, you now have a predefined list from a dropdown.

Once you make your choice you are presented with a graphical interface showing the result of your selections:

Step 3: Make your choices

As you can see, there is no more hunting around for an album in the Helpers section. Everything is presented to you here directly and visually. Again, the output is contextual. Let’s say in the previous screen you had picked “Multiple Albums”. Then, in this screen you would be able to select multiple albums instead of a single one.

After this screen you are taken to the options for layout, specifying counts etc. and the shortcode is generated accordingly.

A Good News / Bad News Situation

Obviously the changes I am making will greatly enhance usability, which is good news. Also, for people happy with the older interface I will be keeping that around; I have no desire for Photonic to end up like Gutenberg 🙂

The bad news is that though I have already written 3700+ lines of code for this, I still have considerable ground to cover. The key remaining pieces are:

  • The entire Instagram module
  • Most of the native WordPress module
  • Populating each field individually from a shortcode already in the post (i.e. deconstructing the shortcode)
  • Most of the integration with TinyMCE

If I were to assign a percentage of completion I would say I am 60% there, but the amount of testing this sort of a feature demands is insane. Hopefully the final product will be worth the wait!

What makes things tougher is that as I keep developing this, I keep realizing some missing functionality that can be added to the plugin. E.g. in Step 3 above I let you search for photos on SmugMug—this is a brand new feature as are several others such as filters for Zenfolio.

And with Gutenberg hanging upon my head like the sword of Damocles I am approaching the crossroads where I have to decide whether to bundle Gutenberg support in this iteration of the plugin or the next.

Do let me know what you think! I would love to get your inputs.

Aug 142018

It is a sign of changing times when I get surprised by news specific to WordPress. I had heard about Gutenberg and the whole discussion around Facebook patenting REACT in a different context (about DIYThemes suing Automattic), and filed the information away as something not to be unduly concerned about.

Then, three weeks back, as I was looking to install a plugin from my WP dashboard, I noticed that a new “featured” plugin showed up, Gutenberg. It naturally accessed the information I had filed away and I started looking at it. Two things stood out at a first glance:

  1. It has a horrible rating.
  2. It is going to be a part of version 5.0 of WP.

At the time of starting this article Gutenberg holds an average rating of 2.4 out of 5 stars over 882 reviews, with a whopping 503 single-star reviews. That is more than all the reviews Suffusion and Photonic received their whole lifetimes! What is more alarming is that the rating is dropping by the hour and it wouldn’t be a shock to see it plummet to 2.2 by the time I am done.

The Poorly Rated Featured Plugin – 2.4 and Sinking

My curiosity piqued I started going through the reviews and I installed the plugin to take it for a spin. After playing with it for a few weeks in addition to formulating an opinion about Gutenberg I have, daresay, psychoanalyzed the reason behind Gutenberg. But before I go there here is some background. People familiar with me and this website are aware of these, but for those who aren’t, I promise to make it quick.

Background 1: Theme Development Experience – Suffusion

I was the author of a WordPress theme that was the highest rated free theme available on while it was active, mainly liked for the insane number of options it provided in terms of customization. I stopped active development of the theme in 2013, and it was eventually yanked from the repository by a zealous but poorly informed naysayer in 2016.

While the theme was in existence one of the main features I had provided was that of “Custom Layouts”. This was way back, in February 2012 – something that tells you how far ahead of the times Suffusion was! The design challenge I had at that time was, “How do I support layout customization using standard WP constructs, let people add advanced content, and not get into shortcodes etc.?” The answer that instantly came to mind was “Widgets!” I ended up providing a good number of widget areas that could be customized into fancy layouts and have any widget added to those. In theory you could build a page entirely comprising widget areas and add anything you want to them.

Background 2: Plugin Development Experience – Photonic

While I stopped work on the theme many years back, I have had a plugin running for over 7 years now that deals with the ability to insert galleries from sources such as Flickr, SmugMug, Google Photos etc. I have until now had a rather plain interface for inserting the shortcode corresponding to these galleries and that is one of the key limitations of what is an otherwise superlative piece of code.

Background 3: Experience Beyond WordPress

As a part of my WordPress life the only people I interact with are people who used to use my theme and those who use my plugin. So my experience with end-users editing content in WordPress on a day-to-day basis is low. However as a part of my day job I am a senior technical strategy and solution design consultant at a Big 4 Consulting company, having worked with multiple Fortune 500 companies. So I do have a good feel for enterprise class tools and what users expect.

Why Gutenberg

Now, to the main point of the review.

It has been a pebble in my shoe that WordPress has generally been a laggard with respect to innovation. Many facts point to this:

  1. For all talk of being a “Content Management System”, the native features built in to support content management have been sparse, and it has often had to rely on plugins to handle its many shortcomings. It has always amused me that this list that kicked up a firestorm in December 2011 is still mostly relevant, and the moment someone points out “Oh, WP is not a CMS”, there is a response pointing to a whole list of plugins. The point is, why hasn’t this been in core?
  2. Take menus – WP joined the party pretty late, in 2010, while several self-respecting themes offered a way out, not to mention competitors such as Joomla. Eventually WP picked on something developed by Woo and delivered menus with version 3.0. Even when introduced, the first version did not support automatic addition of new posts / pages.
  3. In many senses 3.0 was a watershed moment in the history of WP. They also released Custom Post Types in that version, because they realized that simply having posts and pages was not going to cut it in the CMS world and they needed something more meaty.
  4. Then there were post formats. Introduced in version 3.1 (in February 2011), post formats were introduced as something to quickly publish a post without making it look like a regular post (mostly as a counter to Tumblr). Think of them as out-of-the-box custom post types that can be formatted individually by themes.
  5. Next, customization: for the longest time WP had other recommended ways to handle theme settings, till it finally released the Theme Customizer in 2012. Even when it did so the interface was deemed so poor that very few theme developers jumped on the implementation (the adoption was a lot poorer for premium themes). A more large-scale adoption occurred only when the WP Theme Review Team forced all themes on .org to use it or be removed from the theme repository (I was compelled to pick the latter and had my theme removed). Obviously the WPTRT has no jurisdiction over premium themes, so several big-name themes still have other (better?) ways to enter options.

The point is, WP core was built as a blogging platform in the beginning, and has been playing catch-up ever since, trying to be seen as a more serious content management system. In fact to the uninitiated, the moment you mention “I work with WordPress”, the first response is, “Oh, the blog thing?” To that effect, what it says on is the truest definition of WordPress:

WordPress – No Official Pretensions towards Being a CMS

“WordPress is open source software you can use to create a beautiful website, blog, or app.” At its heart it is nothing more, and certainly not a full-blown CMS. And therein lies the ambition of wanting to be seen as something bigger.

Gutenberg is the first major shift towards a serious CMS, wherein WP is not telling developers, “This is an API. Now build something that others can go and play with,” a la custom post types. Rather it is telling end-users, “This is the result of an API. Now go play with it.” In fact in the list of shortcomings I referenced in the link above, the lack of a good WYSIWYG editor features high. TinyMCE is good as a content editor, but it is no design editor.

Gutenberg is the first major shift towards a serious CMS, wherein WP is not telling developers, “This is an API. Now build something that others can go and play with,” a la custom post types. Rather it is telling end-users, “This is the result of an API. Now go play with it.”

There is also another aspect – the money. If you are reading this, you are likely the user of the self-hosted version of WordPress, which you downloaded from But chances are, you were introduced to this via its more famous cousin, The .com version has many competitors, primary among them being Wix and Squarespace. They apparently have a better visual editor that WordPress is trying to ape (this is hearsay – I have no experience with them). If true, you will notice that the theme of playing catch-up is not limited to a desire of being a better CMS, but to also reclaim the share of the pie that it has lost out.

The Underpinnings

So how does Gutenberg work? It essentially introduces a very simple concept – a “block”. A block is a self-contained unit that could have pretty much anything – a block of text, an image, a gallery, a video etc. or another block. Seems very similar to a widget, doesn’t it (apart from the nesting of course)? The only difference is that a widget can operate within a widget area, but a block operates within a post. In fact, it does pretty much what every theme / plugin that offers custom layouts does – it provides you with an ability to insert arbitrary HTML markup at places of your choice.

Where a Gutenberg block has an edge over other methods is that it uses a very simple and innovative method to identify itself: an HTML comment! To quote examples from the documentation:

<!-- wp:image -->
<figure class="wp-block-image">
    <img src="source.jpg" alt="" />
<!-- /wp:image -->

The above shows an image block and …

<!-- wp:latest-posts {"postsToShow":4,"displayPostDate":true} /-->

… shows a block of the 4 latest posts.

Of course, since WordPress has complete control over the platform it is able to define an API and work with such syntax. The advantage of having a comment is that even if you are able to disable Gutenberg (go back a version?) it will not show you unwieldy shortcodes the way custom layout plugins do. The other advantage of course is that since this will be a part of the core, it will not matter which theme or plugin you are using – the content will always be there.

The Public Opinion

A lot has been said about Gutenberg and the overwhelming dose of vitriol (i.e. most of the 1-star ratings) directed towards it points to a few things:

  1. People are seriously concerned about the amount of disruption it will cause to their clients.
  2. People are seriously concerned about how many of their critical themes plugins will stop functioning with Gutenberg.
  3. They think it is unnecessary, or at least not needed as a part of the core. Most people would be OK with a gradual phase-in.

There is a lot of additional constructive good feedback too among the 1-star ratings, though this is mostly covered in the 2-star ratings:

  1. The most common comment is regarding the way Gutenberg disrupts the writing process. Most people believe (myself included) that switching back and forth between the keyboard and the mouse is extremely distracting. Gutenberg makes you acutely aware of this.
  2. Gutenberg is buggy. 900+ issues buggy.
  3. It isn’t close to being as feature-rich a design editor as some commonly available alternatives such as Builder or Elementor are.

Curiously enough WordPress claims the intent of Gutenberg is post editing (where it doesn’t do well according to point 1) above and not a design editor (where it downright sucks according to point 3), while most users see it as an amalgamation of both that fails to deliver.

What has been rather unsavoury in case of Gutenberg though is that the WordPress forum moderators are stepping into multiple threads, often threatening and sometimes proceeding to remove single-line 1-star reviews. In several cases they have stopped discussions on review threads when none of the parties concerned objected. It is almost as though a bad review of Gutenberg is seen as an affront to the moderators themselves and they feel obligated to police the reviews. The same enthusiasm is missing when it comes to any of the other plugins in the repository.

My Opinion – A Much Needed Step Poorly Executed

As a WordPress user Gutenberg makes no sense to me for the following reasons:

  • When I write content for my posts I simply switch to the “Text” editor from the “Visual” editor. If Gutenberg was offered I would do the same. More than 95% of what I write needs no fancy UI and Gutenberg is just that.
  • I am not a person who dramatically alters the look and feel of sites every now and then, and for most of what I do I am very comfortable using Suffusion or a child theme of TwentySixteen. I have used the Builder plugin if I wasn’t using Suffusion, and it gets the job done with minimal fuss. From experience it takes less than a day for me to sort out the site’s look and feel and it is mostly done just for the landing page (for every other post / page the regular content editor just works). Plugins such as Builder can be used for individual pages without being shoved down our throats for every type of page / post.

Bear in mind that the above is why it doesn’t make sense to me – several users might be accustomed to the “Visual” TinyMCE editor and they might find Gutenberg a step up. I on the other hand am a person who favoured using Emacs / Vim before discovering JetBrains and their wonderful IDEs (no, IBM and Eclipse didn’t do it for me). Even today I keep Vim around for quickly editing text files :).

As a WordPress developer on the other hand Gutenberg makes a world of sense to me:

  • It is a no-brainer to have a standardized way to code the equivalent of blocks etc. Having this built into core simply eliminates the need for each fancy theme coming to the table with its own take on what its premium features are (yes, I am talking about Suffusion too!). So themes can focus on pure look-and-feel aspects instead of putting forth their own variants of what they think a wheel should be. Of course, I can see each theme author now scrambling to offer two-dozen custom blocks for Gutenberg users, but that is a discussion for another day.
  • Regardless of any amount of work this might cause for me in Photonic, I am really happy that the mechanism to insert code (even shortcodes) is being standardized. Did I say how much I like getting things standardized?

In a nutshell, as a developer I like standardization and simplicity. I am not yet sure how simple the Gutenberg API is – I still haven’t started writing Photonic’s compatibility for it, and while some of WP’s APIs have been easy, some like the TinyMCE API have been messy. As a user I feel ambivalent or perhaps negative towards it – I don’t like that fact that it has taken away from a simple writing experience and unnecessarily prolonged it, but I can see visual thinkers warming up to it.

(Poor) Decisions not (Better) Options

WordPress has always maintained a philosophy of “Decisions not Options”. That is one of the reasons that option-rich themes are looked down upon, as the core philosophy of WordPress is having a theme for a single-purpose without cramming too much into it. This is a philosophy that has helped keep many things lean. Of course, concepts like Post Formats have things like “Status” or “Chat” which probably have about a 0.001% usage, so bloat has crept in here and there. But by and large they have been able to stick to this mantra.

That being said, for the amount of effort, time and money that the powers that be have invested in Gutenberg the end product or at least the product in its current state seems to be a letdown, much like how Windows Vista felt after years of delay. The presence of alternatives such as Builder and Elementor make this delay more embarrassing. What they have ended up building is a sub-par editor.

Is it a content editor? WordPress says yes and most testers say it does a pretty bad job of it. I used to feel TinyMCE was not good, and this takes that feeling further. It seems like one poor decision layered on top of another as far as the interface design is concerned.

Is it a design editor? WordPress says no and the testers think that if it was intended as a design editor it is very poorly made. It is certainly not a better option than the existing tools in the marketplace.

Is it an attempt to join the big CMS players’ league and be taken more seriously? You bet!

Is it an attempt to win back some of its lost customers from competitors? Of course it is!

Ultimately WP is going to land its “Decisions not Options” hammer and make this the standard in a few months’ time. The days of WP being one big happy community are long gone and in a bid to stay competitive the finished product of Gutenberg is likely to do one of two things – it might usher in a new era, or it might end up relegating WP to the irrelevant.