This article gives an excellent walk-through of the current Guttenberg editor. It could almost be a help doc. It also has an insightful summary of pros and cons.
The current WordPress visual editor hasn’t had many changes over the years and for the most part, has stayed pretty much the same. While this isn’t a bad thing, many think it is time for a change. Other platforms such as Medium or Ghost provide a really unique and refreshing experience for writers, so why can’t WordPress? Well, many contributors and volunteers have been working on the new Gutenberg WordPress editor behind the scenes for the past 6+ months. Their goal? To make adding rich content to WordPress simple and enjoyable. Today we will dive into the new editor and discuss some pros and cons. What is Gutenberg?
Gutenberg is a take on a new editor for WordPress. It is named after Johannes Gutenberg, who invented a printing press with movable type more than 500 years ago. The current visual editor requires a lot of us to utilize shortcodes and HTML to make things work. Their goal is to make this easier, especially for those just starting with WordPress. They are embracing “little blocks” and hope to add more advanced layout options. You can check out the official example.
To be fair to the developers and the team working on this, it is important to
The current version of Gutenberg breaks thousands of themes and plugins (e.g. meta boxes). While this hopefully will be adjusted, it's still surprising that it was not priority in first place. Does core development have users in mind or may WordPress even have a marketing problem?
Is the Gutenberg editor what WordPress wants to be in the future? As you probably have noticed, a lot is going on at the moment and it seems WordPress is slowly trying to reinvent itself. While this is great and surely necessary to make it future proof, it also raises some questions and concerns. Does WordPress development go into the right direction? Is it clear what WordPress wants to be? Or does WordPress even have a marketing problem?
The Gutenberg approach and what users really need
The most exciting WordPress news in 2017 is Gutenberg – the brand-new editor which probably will ship with WordPress 5.0 and which currently is available as a plugin. It’s great to see that the editor in WordPress will be updated after all those years. However, the Gutenberg approach also raises lots of concerns amongst developers and confusion about what WordPress wants to be – to say the least.
There recently have been lots of posts on WP Tavern about Gutenberg and this seems to be the hottest topic in the WordPress community at the moment. While most people agree that WordPress needs to evolve, there also are disagreements of how this should be done. Today I stumbled upon a comment
Everyone is now writing about their experiences w/ Gutenberg. Chris's take is a good read: he missed the goal of this thing
I checked out the Gutenberg plugin and new writing experience for WordPress – via an early plugin version. It’s clear I missed the goal of this thing. I tried the new Gutenberg writing experience for WordPress today!
Having read all the early reviews of the new Gutenberg plugin (which is still a very early release), and then reading the interview that Matt Mullenweg did with Torque at WordCamp Europe, I was excited to try it out.
What I read from Matt’s interview, which matched his WordCamp US talk last December, was that this focus on the editor experience would let us leapfrog the experiences that newbies were enjoying with Wix, Weebly & Squarespace.
Of course, there’s always mention of the nice writing experience of Medium that is always mentioned, but the target, that I thought I heard, was the other players. The folks that were spending gobs of marketing money on ads and were taking market share from the WordPress ecosystem.
It’s clear I’ve misunderstood something, but first…
Before I tell you about my experience, let me set the record straight on several things.
I believe that the number of volunteers working on this have done a great
With over 50,000 plugins on the repository, you are bound to run into a bad update or conflict now or then. Check out these different ways to quickly grab an old version for testing purposes.
There comes a time when every WordPress site owner will run into an issue with a plugin update or conflict. In this scenario, one of the easiest ways to debug the problem and confirm it is the update is to download the previous or older version and test it on your site. Check out these three simple ways below on how to download older versions of WordPress plugins. How to Download Older Versions of WordPress Plugins
When it comes to things that can break your WordPress site, plugins are one of the most common. Seeing the white screen of death (WSOD)? It is probably due to a plugin. Why? Well, there are over 50,000 plugins available on the WordPress repository, not to mention the thousands of premium plugins from 3rd-party providers. Developers try as best they can, but it is almost impossible for them to test every scenario and conflict. This is when having a few options to download older versions for testing comes in handy. A lot of times this allows you to fix your site, notify the developer, and wait for the next patch. Remember to always test on staging first!
Option 1 – Download Older Versions of WordPress Plugin From the Repository
The first way to download an older version
Joshua Strebel -- the CEO of Pagely -- shares his view of the current state of the WordPress economy, and why he is confident in both its strength and future.
Joshua Strebel — the CEO of Pagely — shares his view of the current state of the WordPress economy, and why he is confident in both its strength and future. Editor’s Note: This is a guest post by Joshua Strebel, the CEO and co-founder of Pagely. Pagely was one of the first managed WordPress hosts and continues to be a market leader. Josh had some thoughts about the WordPress economy, which I asked him if he would share here for the Post Status audience. He’s been around for a while, and I think he’s got a pretty good hold on the state of things. I hope you enjoy his commentary. And if you like this post, you’ll also enjoy Post Status Publish.
There’s been some recent speculation on whether or not the WordPress economy is beginning to slump. I would answer ‘yes’ and ‘no’; it is clearly evolving, and some areas are contracting while others are growing. I believe we are feeling the effects of market maturity.
Are downmarket “one stop shop” alternatives and in house teams the best solution for the future of WordPress? No, because hosting providers, developers, and agencies who specialize in this space are where
Important observation from Amanda Rush: "I can type a post title, but I have to add a block just to start typing text." Seems to go against the "type type type" stated philosophy of Gutenberg.
Last weekend, during WordCamp Europe, Matt Mullenweg announced that Gutenberg, (the upcoming WordPress editor that will replace TinyMCE as well as become integrated into the WordPress customization experience), is now available for downloading and testing. So of course people have started playing with it, and Aaron Jorbin issued the following challenge on Twitter today. I broke my own cardinal rule and installed this on a live site, because I need content to play with. I'll start with the good first. I appear to be able to add blocks and move them around using the visual editor part and a screen reader. Now for the not so good.
I can type a post title, but I have to add a block just to start typing text. I can see myself switching to text when this goes live, because writing a post like this is turning out to be incredibly inefficient, cumbersome even, and I'm not sure if that's because I'm just used to writing HTML and can do that in my sleep and so I don't use WYSIWYG editors, or if it's because of the software, or both. I'm also not sure if paragraphs are supposed to be in their own separate blocks although I suppose if you're going to be moving them around, they probably should
I'm not sure what is meant by "managing" plugins and themes, and this article doesn't expand on it, but I'm glad to see that 4.9 will fix the problem with the new text widget stripping out code.
Matt Mullenweg, the overall product lead for core releases in 2017, has published an overview for what users can expect in WordPress versions 4.9 and 5.0. After the success of 4.8 and the initial release of Gutenberg last week, Mullenweg is aiming to see the plugin installed on 100K+ sites during the next few months before merging it into core. He also suggested that WordPress could put a promo for the plugin in the upcoming 4.8.1 release. “In the meantime I think we can do another user-focused 4.9 release with the theme of editing code and managing plugins and themes, doing v2s and polishing some features we brought into WP last year,” Mullenweg said. “Weston and Mel already have some good ideas there, and we can start to discuss and brainstorm at the Dev chat next week. This will also allow the Gutenberg-driven release to be 5.0, which is a nice-to-have but not the primary driver of this decision.”
Mullenweg elaborated on changes to the release process in a post on his personal blog. The original idea was for releases to be driven by improvements to the three focus areas (the editor, customizer, and REST API), but the radical changes that Gutenberg introduces
Gutenberg will be a game changer for WordPress. These are just my initial thoughts on it's beta development to date. There's LOTS of potential here.
Gutenberg is the future of content in WordPress. It will deliver the elegance of Medium but with far more power and flexibility of layouts and content types At WordCamp US 2016, Matt Mullenweg announced that new point releases of WordPress would have specific foci around features of WordPress. In the same breath he also announced that he wanted WordPress to have a renewed focus on the post writing experience. He acknowledged how content editing has changed and evolved a lot over the years while the WordPress editor has changed relatively little. I listened to that whole announcement with baited breath because I’ve been longing for a totally revamped way to write content for a long time.
First I took a stab at showing highly styled content directly in the editor
I emphasized how the except can (and should) be used as content in posts
Then I collaborated with Kevin Hoffman on displayed theme-based dynamic styles directly in TinyMCE
All these things were for me tiny efforts to make the backend editing experience more closely emulate the front-end results.
So when the first announcement came out about Gutenberg being about “little blocks” I was excited. This sounded like
In this tutorial, you'll find several ways on how to make a plugin extensible. There are also code examples for each approach.
Creating a WordPress plugin can be really fun but you might create a plugin that other developers can’t extend. There will be clients that need something slightly different that you have made. Create extensible plugins so that other developers can jump in and add their own features. In this article, we will go through five ways which you can use today to make your plugin extensible. 1. Using Theme Support Feature
What is a theme support feature? When you create a theme, you must define that your theme supports a feature. This feature can be the featured image. Adding theme support is done by the theme and you can read more about that function add_theme_support here.
But how to use that within a plugin?
Have you ever had a project where you just wanted to remove some of the styles from a plugin? And for some reason, that was not possible, right? Well, you can make that possible within your plugin!
We can decide to enqueue our style only if the current theme does not support our plugin styles. If the theme was made with our plugin in made and has the necessary styles defined, the theme could have something like this in their code:
But this won’t do any good if we don’t
Ionut Neagu's transparency report for May is extremely interesting. ThemeIsle is experimenting with being a marketplace for 3rd party theme authors and it will be a transition worth watching. Also, he dug into and reports his observations regarding some of the teams, the theme repository, and leadership of WordPress.org.
Welcome to the 28th edition of the monthly transparency report (for May 2017). This is a series where I do my best to discuss all the current goings on that were at the center of our attention last month, plus everything else that’s interesting from a business-ish point of view. Click here to see the previous reports. Something I shared in one of the previous reports was how we were planning to invite third-party authors to offer some of their themes through our directory at ThemeIsle.com. Well, it’s happening!
But this month’s report is not only about that. There’s been a lot more going on, actually, and I hope to get to all that further down in this report. Feel free to jump around, though:
Third-party themes in the ThemeIsle directory | Is there room for a Jetpack alternative? | Community and the Theme Review team (TRT) | Listen less, care less, but do more
Third-party themes in the ThemeIsle directory
Here’s the current state of events with our theme partnership program (you could call it like that, I guess):
We’ve just had our soft launch of the whole initiative on June 20th this year, which was, if you look at the calendar, just two days before
This was a really great discussion of Gutenberg with Weston Ruter -- a WP Core Contributor and Gutenberg Contributor as well. Well worth a watch.
On this episode: Show Notes:
This week on WPwatercooler we’re looking into the future with the new post editor, Gutenberg. It looks like Gutenberg is more than just a post editor, they are calling it a block editor since it does much more than just text editing for a post.
In this post we mainly focus on some innovative new plugins and solutions we discovered during WordCamp Europe 2017
We've just gotten back from WordCamp Europe 2017, held in Paris, and boy was it awesome! Our entire team found the experience insightful and important. In just two concentrated days, we got to meet top WordPress figures, previously only communicated via email or Skype.
We also met various members of the WordPress community from all over the world, all earning a living through WordPress in one way or the other. We listened to a handful of riveting talks, including the inspiring closing interview with Matt Mullenweg.
Oh, and we visited Eiffel, obviously!
You can't write about WordCamp without addressing the generous swag handed by the contributing sponsored. This WC's notable merch included BlueHost spinners (thanks Nick), Yoast Lego minifigures and WPEngine Smartphone holders (which were handed with a guarantee it will change my life forever).
Another memorable part of WCEU were the parties. We couldn't attend all of them, but we did get to partake in Freemius & WPEngine's Friday party, held in a cozy underground cellar, which included free wine and free food. It provided the perfect surrounding to converse with other plugin developers and get to know them better.
Also worth a mention
Great article about the recent increase of renewal pricing for WooCommerce and the business opportunities this opens up for new companies.
There was a general sense that many of the most profitable avenues peaked a few years ago, with much discussion about just how screwed the theme market is. The plugin market is even harder to crack, unless you have a particularly useful new idea, but it seems that almost anything that can be done has been done, and now the fight is down to who can market most skillfully and assemble the most financial firepower.
Read why we are dumping $36,000 USD in yearly revenue and stop selling WordPress themes on WordPress.com. And what you can learn from it...
For those of you who don’t know, WordPress.com is a WordPress hosting company operated by Automattic, the company of WordPress co-founder Matt Mullenweg. WordPress.com is the entry level for many users who start building their websites with WordPress, as it doesn’t involve hosting your own website. In the past our flagship theme, MH Magazine, was available on WordPress.com as well, but we decided to stop selling themes on WordPress.com. Why? Let’s start at the beginning… As you may know, MH Themes was founded in 2012 and we launched our MH Magazine theme in February 2013. The theme quickly became popular and our business started to grow rapidly. In January 2014 Philip Authur Moore (a very nice guy who worked at Automattic) reached out to us and asked if we would like to become a premium theme partner of Automattic and launch WordPress themes on WordPress.com. As you probably can imagine, that was very exciting news for us.
Since this was an interesting business opportunity, opening up a whole new market for us, we were thrilled to sign the contract with Automattic. A few days later the theme review process started and it quickly became clear that WordPress.com
WooCommerce recently dropped the 50% renewal discount for premium add-ons. There was not an announcement and some people are upset about a significant increase in cost. People with auto-renewal might not realize the change in policy.
Customers who purchased extensions from WooCommerce.com are discovering that the renewal discount of 50% has been removed. Instead, they are now paying full-price. The WooCommerce blog and the official Twitter account do not mention anything about the price increase.
We contacted Automattic and asked if the discount was removed and if customers received prior notice of the price increase. Todd Wilkens, head of WooCommerce, provided the Tavern with the following statement:
All customers receive notification of their upcoming renewal 7 or 15 days before a charge. If anyone received an incorrect price, please contact us immediately and we will make it right. As always, we are committed to making sure WooCommerce is affordable to the widest range of people while maintaining our high level of service and support.
A customer upset by the change contacted WooCommerce’s support desk and inquired about the price increase. The support representative confirmed that the discount was removed and that customers will need to pay full-price to renew.
The customer service rep also explained that the change is due to WooCommerce moving to a straight renewal process, similar to other SaaS products.
This is a reflection on WordCamp Europe 2017, highlighting our experience as a product team that attended, with a special emphasis for WordPress product / business people.
WordCamp Europe 2017 has just ended, taking place in Paris this year (next year at Belgrade, Serbia, in case you haven’t heard yet). While last year, at Vienna, only Stanley Macha and I were able to attend – this year, most of the Freemius team was there! Now that everyone’s safely back home, I thought I’d take the time to look back at the event and reflect our experience as a product team who went, using the event as “an excuse” to unite our team and meet everyone face 2 face while also meeting other folks and teams.
I will not be covering topics such as the event location, contributors day and not even the talks, as those topics are well covered on other great recaps of WC EU 2017.
At the beginning of this post, I would like to mention an unfortunate issue, which is the reason I can only write that most of the Freemius team attended WordCamp Europe 2017. Due to technical issues, our team member, and lead developer, Leo Fajardo, was unable to attend WC EU 2017. More specifically, the French government refused to issue him a visa.
Leo was not the only one who suffered the consequences of visa policy in France, as it seems that many
WPHierarchy.com is a WordPress resource created by Rami Abraham in 2013. The site is an interactive version of Michelle Schulp's colorful diagram of WordPress' template hierarchy. Each template is linked to documentation that explains its function.
Developers! Tom has created an autoloader you can drop into a WordPress plugin and begin using it automagically.
Earlier this year, I gave a talk at WordCamp Atlanta about Namespaces and Autoloading. These are two topics that, even though we can’t often use some of the native features of PHP7+ in our work, I think that many of us should be using in our plugin development.
Sometimes though, I think the problem is that developers lack the time, resources, or experience to know where to start understanding autoloaders let alone write their own.
And I want to fix that.
For some time now, I’ve been using a very simple autoloader in my projects. It’s served me well, but I think it could it be more powerful and I think it’s something that others could easily use in their projects, too.
So I’ve started a repository that offers a simple autoloader for WordPress. No, it’s not for WordPress core nor is it meant to be used with themes, but it’s for those who want to begin using autoloading in their WordPress plugins and similar projects.
Simple Autoloader for WordPress
You can read all of the details in the project’s repository, but here are the basics:
TL;DR: An autoloader you can drop into a WordPress plugin and begin using it automagically.
I have a very
"Support net neutrality legislation. I cannot stress how important this is. Spread the word about the dangers of a closed web. Vote with your dollars and your support. Use open platforms like WordPress and encourage others to do the same."
The internet is no longer a toy. It is no longer used only for fun or even simply for research. It is now an integral part of people’s lives, of businesses, and even entire economies. Comedian and science advocate, Bill Nye, was recently speaking about his new show Bill Nye Saves the World. Asked why he thought it was so important, he said: I want clean water for everyone on Earth; renewably-produced, reliable electricity for everyone on Earth; access to the internet, or whatever the future of electronic information is, so that everybody in the world can participate in taking care of the planet.
Water, electricity, and internet. It may sound crazy, but I would argue that the science guy is right. The internet is vitally important to the future of humanity. It needs to be protected, secured, and available. This cannot happen unless it is open.
The internet as we know it started around 1991. Tim Berners Lee, working with CERN, developed HTTP, HTML, and the first ever web browser. The internet was much more academic at that time and looked a lot like the pages of a research paper.
Around the same time, the Commercial Internet eXchange was trying to do something ground breaking.
Nice analogy. Both the short version and the longer explanation helps clarify the situation.
Explain to me in two paragraphs or less the delineation between https://t.co/shm7MBBfUi, Jetpack, and https://t.co/w3VOMjx5s9. — Ryan D. Sullivan (@ryandonsullivan) June 21, 2017
Ryan Sullivan posed a challenge/trick question that got me interested because I like trying to come up with compact plain language explanations. So here’s mine:
Restaurant vs. meal kit vs. grocery shopping. https://t.co/RkKp2ooK07
— Helen 侯-Sandí (@helenhousandi) June 21, 2017
This is, of course, not a complete analogy for all aspects of all of the above. It’s all of seven words, come on. It also assumes cultural knowledge of these methods of having a meal, which seems fairly likely for people looking for this delineation. But I think it’s a solid way to start understanding what these three entities are and what they aim to provide you. It does not explain where your stuff lives or how you pay for it (people use rent vs. buy sometimes for this), and I don’t intend for it to do so. Analogies are helpful in providing understanding where knowledge is still considered specialized. They also center references in ways a given person might understand – this analogy
Great article. Kind of begs the question for centralized way to do it.
We’re sure that when you read the title of this post you’ll think it’s sensationalist. The good folks at WeFoster HQ are going for the BuzzFeed titles now?! All performance related tips and tricks must be covered by now.. And if it really was such a big issue there must be hundreds of articles on the web about this.. Nope.
Below is a breakdown of the symptoms, causes and cure for a serious WordPress condition we call:
Third Party Plugin Update Check Syndrome (TPPUCS™)
How do I know if my beloved WordPress Install is suffering from TPPUCS?!
Thanks for asking! To answer this question we brought in WeFoster CTO and WordPress Doctor, Bowe Frankema. He’s here to answer your burning questions about TPPUCS.
What is TPPUCS?
Third Party (Premium) Plugin Update Checks
The risk of a slow WP admin due to severe performance issues related to the (unnecessary) checking for updates of your (premium) third party plugins and themes.
Should I be worried, Dr. Bowe?
Let me explain who should be worried about this..
If you are running one or multiple Premium plugins or themes.
If you are occasionally dealing with SLOOOOOOOOOOW WordPress Admin page loads (Stage 1)
If you are
Some interesting thoughts on Gutenberg and it's current state. These are all comments on the usage of the app - and I'm sure many of the concerns will be addressed. I think there's a lot of potential in Gutenberg but they need to make sure it at least matches the current editor in terms of functionality.
Gutenberg is being developed as the next generation WordPress editor. I made my first contribution earlier today. Nothing big, but something that will hopefully help people test it. The contribution process was , but for end users, that’s not the important thing. What is important is the actual editor. I’ve seen talk that Gutenberg is in “Open Beta” now, but I think calling this beta software is still premature. I think there is plenty that will change between now and any possible inclusion in WordPress core for Gutenberg. Here are my random thoughts and my first reactions to using Gutenberg.
It’s pretty. And Fast. I never thought of the post editor as being slow, but there is something about Gutenberg that makes it feel fast.
There are a lot of rough edges. It’s hard to know what is a bug, what is intentional, what just hasn’t been done yet, and what hasn’t been thought of.
There is an option for “Drop Cap” that doesn’t seem to do anything on the front end yet.
I’ve also never intentionally been able to highlight multiple blocks at once, but I’ve sure done it on accident a lot.
I can’t seem to delete
#WCEU The new WP plugin for Gutenberg editor is here. It's only v0.1 right now. Try it out!
Description The goal of the block editor is to make adding rich content to WordPress simple and enjoyable.
Warning: This is beta software, do not run on production sites!
The new post and page building experience will make writing rich posts effortless, making it easy to do what today might take shortcodes, custom HTML, or “mystery meat” embed discovery.
WordPress already supports a large amount of “blocks”, but doesn’t surface them very well, nor does it give them much in the way of layout options. By embracing the blocky nature of rich post content, we will surface the blocks that already exist, as well as provide more advanced layout options for each of them. This will allow you to easily compose beautiful posts like this example.
This plugin is being actively developed by many contributors. You can follow along on github.com/WordPress/gutenberg and on the #editor tag on the make.wordpress.org blog.
Contributors & Developers
I didn't like the end of the story. It felt incomplete. But it held my interest for a bit. :)
In January of 1848, James W. Marshall discovered a shiny piece of metal in his Sacramento lumber mill. He showed the metal to his boss John Sutter, and the two discovered that it was gold. Sutter tried to keep the discovery a secret in order to avoid endangering his agriculture business. He failed.
In the coming years about 300,000 forty niners came to California with high hopes of finding gold in the American River. One of the places they came was a small settlement called San Francisco, which at the time had less than 1,000 residents. Within 2 years it would have 25 times that.
Fast forward 150 years or so, and that small settlement now has over 830,000 residents. One of those residents is named Matt Mullenweg.
In 2003, this San Francisco resident, along with Mike Little, forked a piece of software called b2. In doing so, they created their own little nugget of gold that would be called WordPress. Little did they know they were laying the foundations for another gold rush, a digital, open-source kind of gold rush.
When WordPress first started gaining traction, the only people making money from it were in consulting work. Custom websites, and general web related services.