The tone of this year’s WordCamp U.S. was certainly different from previous years due to the controversy around the release of WordPress 5.0. But, there were definitely bright spots and super takeaways too.
Get the skinny on what I gleaned from the sessions to empower DIY site owners and webmasters and prepare us for what’s coming next.
Virtual Attendance
This year, due to financial constraints with a recent home purchase, I chose to attend WordCamp U.S. via livestreams.
I am grateful to the sponsors of WordCamp U.S. that made it possible for me to have a free livestream ticket to all sessions.
But, due to what I heard in the sessions this year, I’d like to plant the seed for WordPress to consider charging for livestream tickets to help offset the cost, and so we are not beholding to the corporate sponsors so much. Perhaps consider allowing more of the community to directly support the WordPress Foundation efforts with those livestream tickets.
Sessions I Attended
While major WordCamps have historically been a gathering of developers, and overwhelmingly male, I’m delighted to report that WordPress has continued to be proactive with outreach to invite women and non-developer speakers. And there was a nice diversification of session topics as well.
Below are the sessions I attended, followed by my takeaways from the ones I found most impactful and interesting, which are marked with an * in the title.
- * Content Security Policies: List Your Trusted Sources and Prevent Attacks by Miriam Schwab
- The Future of WordPress is Gutenberg by Gary Pendergast
- * Curating Content to Serve Your Community by Kelly McCausey
- The Proper Care, Growth and Feeding of Your WordPress Website in 2019 by Adam Silver
- * Moving the Web Forward with WordPress by Morten Rand-Hendriksen
- * Thrive for the Future: The Business of Open Source by Joost de Valk and Marieke van de Rakt
- * Secrets to Being a Great Marketer by Tina Wells
- * Nobody Wants a Website. They Want Results! by Dwayne McDaniel
- The Evolution ad Future of Publishing by Alexis Lloyd
- * State of the Work by Matt Mullenweg
Content Security Policies
CSPs have been a much overlooked area of cyber security. But with the recent edict from Google that all sites should be converted to HTTPS, more attention is finally being paid to the security headers that should accompany use of that secure transport layer.
Proper CSPs are something I teach in Level 3 of my Webmaster Training course. So, I was particularly interested in this session.
Miriam Schwab has been involved with WordPress since 2007 and certainly knows a thing or two about CSPs.
First, I was delighted that her session confirmed that my research on CSPs was spot on.
In other words, what I teach webmasters, and how I do HTTPS conversions for clients is WAY ahead of the curve on this front. We are already years ahead of what will become future requirements for better cyber security.
Miriam spoke in detail about the growing OWASP attacks, especially the most common security issues plaguing plugins, which is XSS, or Cross Site Scripting.
And this is exactly why I’ve been advocating for site owners to get on the Pro Cloudflare plan. Their recent additions to OWASP security, under the WAF protection, help us bridge those XSS vulnerabilities until plugin devs can release a patch.
Miriam also confirmed that up-to-date information about CSPs is hard to come by. No kidding!!! And, website adoption rates of CSPs are still pretty low, but that is changing.
I was keenly interested in the new dynamic CSP method being created by Google. It most definitely offers better security, but due to the dynamic nature on every page load, it doesn’t play well with caching. And that impacts page load speed. But it is definitely something I’ll be keeping my eye on for the future as CSPs continue to evolve.
And, you better believe I’ll be reaching out to Miriam on this topic in the future.
Curating Content to Serve Your Community
Kelly McCausey lead a super fun and inspiring session about how she became THE resource for her community by simply curating content on her site.
She highlighted the common mistake of only sharing your interesting finds on social media.
By placing those resources on your blog or podcast, YOU become the resource and the one who folks want to follow.
I do much the same with my weekly Tips Tuesday post, podcast, and livestream. It’s full of the site success tips and news that DIY site owners need.
I picked up some new ideas for curation from Kelly’s session that will help me in my new woodworking venture too.
Moving the Web Forward with WordPress
Morten Rand-Hendriksen is quickly becoming my hero in the WordPress community. I totally vibe with his take and vision on the internet and for WordPress in particular.
If you don’t know Morten, he’s been using and teaching WordPress since around the time ground broke on it and he’s the senior staff author at the teaching hub, Lynda.com, which is now owned by LinkedIn.
But Morten also works outside of WordPress with several other site development platforms. He has a broader view, and in my opinion, a much clearer one, of the entire WordPress ecosystem.
I was keen to hear his session, especially in the wake of the abrupt release of WordPress 5.0 earlier this week, and his vehement disagreements with Matt Mullenweg on how WP should be run.
The session was not disappointing.
Instead of complaining again about the leadership structure of WordPress, or lack thereof, Morten has done something about it.
First, he gave us the historical perspective for his end point, which was that WordPress has grown into an entity that sets standards for the entire Web. Yet, it doesn’t have a representative at the table when major organizations like Google and W3C gather to make decisions about the Web.
His point is that WP needs a new organizational structure that includes leadership and a cabinet with a position akin to Secretary of State to represent WordPress at these global meetings.
And instead of him telling us what other cabinet positions need help in the areas of Accessibility, Privacy, and Open Governance, he brought onto the stage the folks who have been working diligently in those areas to speak to the support they need to get the job done, and more importantly, what’s at stake in those areas.
Morten also spoke about the guiding principles of WordPress, and that a primary objective is to democratize publishing.
Morten went beyond that to say we need to democratize the organization of WordPress – nearly to the point of electing its leaders, and definitely to the point of more transparency and a hierarchal structure of communication for all the decisions being made and who makes them.
Basically, what Morten is saying is that WordPress must become an organization with a defined top-down structure and a clear set of goals and agenda so that it can properly take its place as a leader in creating what the future Web will become.
He suggests following the models already created by other organizations for open governance. WordPress doesn’t have to reinvent the wheel on this. It also doesn’t mean developing in isolation or inventing isolating ways to do things, much like Google so often does.
Morten’s solution – the WordPress Governance Project.
And we can all participate!
They have a special Google form where you can sign up to stay informed when the project kicks off in January 2019.
But, this wasn’t the end of Morten’s discussion on the matter, and we’ll get to that later in Matt’s State of the Word address.
Thrive for the Future: The Business of Open Source
Joost de Valk (of Yoast SEO) and his business partner Marieke van de Rakt gave a presentation that was a nice follow up to Morten’s session.
The first part of the presentation was about the history of Joost starting his business in the attic of his home with a free plugin and how it has turned into a $10M/yr company using a freemium model. He highlighted multiple other companies who have achieved the same.
But their talk, and especially the questions afterward, evolved into a discussion about open governance and the extreme need for better communication from the WordPress leadership.
That communication should include a publicly published roadmap and a new layer of leadership where all teams report in and decisions are made with everyone knowing what everyone else is doing.
Joost also cited how much it cost his business to not have that roadmap. Essentially, they had to throw out half of the new coding they did for plugin upgrades because they didn’t hear about Gutenberg until 4-5 months after development had already started.
He specifically stated that the layer above the lead developers was the problem.
Their presentation also focused on giving back to the WordPress community at large at a rate of 5%. For them, that includes sponsoring developers to work exclusively on the WordPress code.
In other words, Team Yoast pays the developer’s salary, yet they work on WordPress, not Yoast products.
More on this corporate sponsorship in the State of the Word notes.
Another person asked about the 5% giving and that she had donated way more than that as a volunteer for WCUS.
Joost’s reply was that WordPress should, at the very least, give her a backlink to her site as a thank you.
In other words, she gave her time instead of money and yet had no representation like the big money sponsors. All she got was a generic group thank you to the 200+ volunteers during Matt’s keynote.
Secrets to Being a Great Marketer
Tina Wells, of Buzz Marketing Group was a breath of fresh air from the usual WP dev presentations.
Her session was fun and full of energy and it made me want to hire her. And I think that just drives home the points that she made during the presentation. People buy feelings, not products. They buy relationships, not services.
She also highlighted why it is so vitally important to follow emerging trends. She gave examples of the companies that failed to do so and are no longer with us – like Blockbuster missing the opportunity to become a Netflix service. And those who ignored the needs of Millennials back when they became a consumer group, and especially now, as they become new business owners. I can personally attest to how eye opening, and profitable it has been for me to market directly to that demographic!!
I looked up her site and was inspired by her blog. She is most definitely not on a blogging hamster wheel to get clients for her service based business. And you better believe I started following her to get inspired for marketing BlogAid better!!!
Nobody Wants a Website. They Want Results!
All webmasters and designers should get to know Dwayne McDaniel from Pantheon.
His session was all about the intake funnel for new clients.
If you don’t know what KPI is, look it up. This is his guiding principle with new clients.
He also had a list of questions to ask right up front that helps everyone set realistic expectations and avoid scope creep.
State of the Word
I’m sure Matt Mullenweg is used to a lot of applause during his keynote addresses. There sure wasn’t much during this one.
He started by stating the guiding principles of WordPress, including what democratization means. He chose to define that as everyone can use WordPress regardless of “language, device, physical ability, income, location, or technical proficiency.”
He completely skirted democratization in leadership.
In fact, he skirted so many key issues in both his address and the questions that followed that I think he should seriously consider running for Congress.
He then showed a series of user testing of the classic WordPress editor that has been with us for a decade. Afterward he flew through doing the same type of posting in Gutenberg.
What I wish to heck he would have shown is new user testing of Gutenberg!!!
No way will someone seeing it for the first time figure it out without training.
That was followed by some of the cool Blocks the community developers have created. And they are truly cool!!!
Another cool feature is the ability to copy/paste directly from a 3rd party writing platform like Google docs, including all the fancy formatting you can throw at it. I’m especially looking forward to using that one myself!
Matt also revealed that publishing in WordPress via mobile with Gutenberg is the next major project they will begin tackling in 2019.
And he later gave a preview of Gutenberg Phase 2 that will include bringing Blocks to widgets.
That will open the door for Gutenberg Phases 3 and 4 when WordPress will likely be dubbed a full theme builder.
Historically, another feature of Matt’s keynotes at WCUS is an overview of how much good the WordPress Foundation is putting into the world. Via the do_action project, 12 charitable organizations had an online presence created for them for free this past year.
The Foundation was also able to donate $30k to organizations such as Internet Archive, Girl Develop It, and Black Girls Code.
But, he followed that by saying donations are way down to $3k and they will not be able to make that level of donation next year.
To me, this speaks volumes about the lack of communication from WordPress to the wider community – beyond devs.
There are literally millions of WP site owners. Where is the mass appeal to them to give even $1 to the WordPress Foundation? These site owners never attend WordCamps. Most don’t even know if they have a WordPress MeetUp in their city.
Why isn’t WordPress making better efforts to engage end users?
There were only a few moments of applause during the address. Those came when Matt thanked all of the volunteers who help developed WordPress 5.0 and for the corporate sponsorship.
There was no applause for the 8k+ commits they worked on.
But there was applause for raising the minimum PHP requirement from 5.6 to 7.0.
Are you kidding me?
Support for PHP 7.0 will drop on Dec 31, 2018. Is Matt so out of touch that he doesn’t know that and to raise the minimum to at least something that is supported?
Matt also mentioned that during the early development of Gutenberg, some folks chose to use the star rating system on the plugin to voice their opinion by giving a one star rating.
He also complained that folks left long opinions in the dev chat. (Some of the devs complained about that too.)
After the address, there was a question about where folks should voice their opinions.
Matt skillfully skirted the question by suggesting that maybe we need to bring something like BuddyPress back. In other words, not anywhere that the team leads or devs have to deal with daily.
There were also questions about the future of themes. Nobody point blank asked about current theme builders by name. All Matt said was that they would have a way for current themes to opt into using Blocks for everything.
He also said that he didn’t see the need for there to be 10k-20k themes in the future, like we have now.
Read that again.
- What the heck does Matt think is about to happen to the current theme ecosystem over this?
- Where is the clear roadmap for those designers and developers?
- What exactly should they prepare for now to ensure that their business doesn’t take the same financial hit that Yoast did with having to essentially throw out 4 months of coding because they didn’t know what was coming down the pike?
Another question was asked concerning the transparency of the release of WP 5.0 and how they should do better communication going forward. The major concern was the fact that Automattic’s employees did the release posts.
Matt’s response was that they had a large team of release leads for 5.0, which was something different from previous releases. And that it was appropriate for the paid Automattic staff to do those publications. Matt did the final target date release post himself, so he could take full responsibility for it.
Okay, fine. But I don’t think he really answered the question, or addressed the intent of having to ask such a thing.
Keep in mind that all of these folks were chosen by Matt, not the community.
And then the big question – it came from Morten Hendriksen – who point blank asked Matt who the “we” was that he referenced all the time – as if a group of people made decisions on behalf of the community in a transparent way, and in a way that represented the needs and opinions of the community.
Again, Matt skirted the question like a seasoned politician.
But the one fact that he could not escape about the WP 5.0 release was that the discussion and the decisions were made by the release leads he chose, and in a closed door session.
That is not democratization of the community.
That is top down leadership like a corporation.
Don’t get me wrong.
I don’t have an issue with the way the decision was made.
I have an issue with the illusion that Open Source software is developed and released in an open community, led by that community.
Here’s another case in point of how community-disengaged WordPress has become and how it is more like the government.
Another private developer asked how she could get involved without being sponsored by a corporation. She is a solopreneur and cannot afford to devote the coding time to WordPress without some type of sponsorship.
Matt’s answer was that WordPress depends on that corporate sponsorship. If WordPress had to hire those developers then they would have to pay for HR and insurance and all the things that come with having employees.
WordPress is as bought and paid for as a Congressman is by lobbyist.
Bottom line – there is no place for an independent developer at the table.
What Democratization Means to Me
The inclusiveness of community via democratization of WordPress was certainly a leading theme at WCUS 2018.
And yet I couldn’t help thinking about who was completely left out of the conversation by everyone.
There is zero representation of WordPress end users.
Sure, WordPress powers 32.5% of the Web.
That does not represent the millions upon millions of site owners who are not in the top 10% of Alexa rankings.
Who is speaking on their behalf?
I’m talking about folks like me and my clients.
I’m a solopreneur.
My clients are mostly craft/food/lifestyle bloggers and other small business owners and solopreneurs.
We’re all trying to scratch out a modest living using WordPress because it is simply the best platform for our needs, as far as the SEO and ads and integrations with optins and such.
We didn’t choose WordPress because it’s easy to use or cheap to maintain.
And nothing about Gutenberg is going to change that for us.
We, the end users, are at the mercy of corporate sponsored leadership that is completely out of touch with the majority of the people it serves.
Yeah, I can hear folks say – well, MaAnna, why don’t you get involved and come up with a solution?
I tried that.
At last year’s WCUS there was an invitation to join a “committee” devoted to outreach for women in tech.
After attending a few sessions it was perfectly clear that it would take 10 sessions to even decide what they were going to have as a specific goal.
Who has time for that? Decision by committee with no clear leadership and trying to please everyone often goes nowhere fast.
I volunteered for every size of organization you can imagine for 25+ years straight. I know when one is not a good fit for me, or will likely never make it out of Phase 1. I left.
And I haven’t heard a thing about it since.
If they ever reached a decision on that goal, it certainly wasn’t widely publicized.
And I have given way more than 5% of my billable hour time to help get my peeps through this WP 5.0 update and Gutenberg. I honestly can’t afford to donate more.
WordPress also issues surveys. Have you ever seen one? Most site owners haven’t.
And it’s super clear that WordPress is well aware of that in the questions they ask in those surveys, as they are clearly geared toward developers and enterprise level site owners.
I truly get the distinct impression that WordPress is by and for devs, not the end users unless they are corporations. That’s where the money is. The money is also in corporate sponsorship. They make their big bucks off those same little end users. Just take a look at the Diamond sponsors of the WCUS event. Most are hosts.
I hope Morten’s project helps democratize the WordPress leadership.
I hope the bad taste in everyone’s mouth about how WP 5.0 was rammed through and released in an untimely manner helps reshape the leadership structure.
But I have no hope that you and I and the millions of other solopreneurs and small business owners will ever have our voices heard nor issues addressed by the WordPress leadership.
My online business is based on helping you be successful with your online business no matter what comes down the pike with WordPress or anything attached to it.
All this means that I’m going to start looking at WordPress the way I look at other corporations like Microsoft and Apple.
I don’t feel like I’m part of their community. I need what they produce, but I have no say in what that is. I’m just an end user and I take it as it comes and make the most of it.
My community is you – the end user, the site owner. And I am listening to you and addressing your needs directly.
This book could save you hundreds of dollars and months of frustration. Get it free with your subscription to
Yep- you nailed it!
It was actually embarrassing in spots and I cringed just watching
It was hard to watch the keynote Andrew. The audience reactions were muted, at best, most of the time. Definitely not a rally this time.
Thanks MaAnna…so good to know what’s going on ‘behind the scenes’.
You’re welcome, Lynn. I think we’re all past weary of WP drama and I hope that the folks who have stepped up to do something about it succeed. The marketing sessions were super!! I’m glad they allow speakers that broaden beyond the code of the site and into areas that all site owners have to consider.
Hi,
Great summary – I have been following and commenting on Twitter myself and WordPress is fast becoming a dictatorship so I really hope Morten’s project can bring democracy back to governing WordPress.
I have signed up for the notification list and will try and be involved.
We are building our community on WordPress and BuddyPress and want to have a say in the future of the projects.
Dale.
I signed up for Morten’s project as well Dale. I want to see where the community takes this thing.
Fantastic report. We need to enshrine (“curate”) your ideas somewhere. Thank you for your ideas.
Hope you don’t have too much snow out there in paradise😁
I’m going to be doing a LOT of curating on my new woodworking venture. That will also include sharing content from those who have been inspired by what I do and teach there. I think it’s a great way to build a tribe too.
MaAnna, you wrote, “My community is you – the end user, the site owner. And I am listening to you and addressing your needs directly.”
Yes, we “happy site owners and “hubbers ” are definitely a community. That is why we follow you and love what you do for us. I feel I have friends in the Blogaid “village”, and feel supported and secure, not alone.
Thank you for this summary. I am at the very bottom of the WordPress pyramid, like millions of others. My tiny site, non-profit, not business, is relatively insignificant in the WordPress landscape. But I’m so glad to have found you, MaAnna, and value your help very much. Whatever stormy waters lie ahead, I trust you to lead us through calmly, as you have been doing.
So happy to help and I love our village too!!!!!
First, THANKS for sharing such a great recap and including me! I’m blessed!
Second, WOW… you’re an amazeballs example of someone curating really well by sharing the golden nuggets and adding your own perspectives ❤
I look forward to following you!
Thanks so much for dropping by Kelly!!! I’m sorry I could not attend WCUS live. I sure would have sought you out!!!
Nicely said, but I do think that a large chunk of the community may end up moving over to the ClassicPress.net fork of WordPress and that may be where the theme devs have to go.
John Overall WP Plugins A to Z
I don’t know, John. Such a tiny sliver of folks have even heard about the fork. And since we can run WP sans Gutenberg, I think most folks will just turn it off for now.
Ahh but since WCUS the number of people finding out is growing. I only caught wind of it in the past week heard a rumor but did not see it until recently. And I think it wont be long until Gutenberg is completely forced onto everyone who goes past 5.0.
The drive for making WordPress a sitebuilder seems to be strong.
I had posted about it in Tips Tuesday when it first started and have been following the progress.
I think it’s a good idea for WP to become a full site builder.
With Classic Editor being supported through at least 2021, I don’t see that Gute will be forced on anyone. What I do see is that the greater WP community of devs will keep moving forward with Gute, and that folks who don’t make plans to go that direction in the next year or so will just get left behind, as that’s where the focus of development will be, not on what’s going to eventually be old school web.
To me, the fork is more of a reaction to the current leadership of WP more than a real need to split the dev community or not to endorse Gutenberg in the long run.
The fork may have been initially a reaction to lack of communication and the ramming it though too fast, but I do not think so any longer. There is looking to be a split in the community, I would guess up to 30% or more by the time the dust settles. I will probably have to be in both camps for a while, since I have enterprise clients with no easy way we can move their sites to Gutenberg, as the editor looks to be making a mess of things, and I have smaller ones who will fare just fine under Gutenberg.
This was not an advancement for everyone using WordPress but an advancement focused at the users who needed more simplicity. The ones Automatic was loosing market share to Wix, Sqaurespace ect. on the WordPress.com platform.
But so be it after all WordPress was born out of frustration of B2/cafelog software and is was a few years until people discovered it, the same may happen with the ClassicPress fork. Although this could move faster as they are already listing up the plugins that will continue to work with it. I’ll be adding it to my show WPPlugins A to Z in the coming weeks.
I only see the bigger WP dev company’s completely staying with Gutenberg as their fortunes are tied into the WP community in it current form, the smaller ones or up and coming ones may look at the opportunity to service the newly developing community at CllassicPress.
As for being left behind I do not think so, as new opportunities are opening up so the new path may prove more beneficial. It does not look to be old school web if they get this off the ground as they are looking to fix many of the problems with the core that WordPress had not been dealing with.
The classic editor may be supported though the end of 2021 but that is only 3 short years away. Then what? By then if ClassicPress takes off it will have begun to evolve in its own direction.
I believe we are in for some interesting times.. As Matt saw at his state of the Word and the lack of audience approval the community is not happy right now and unhappy people begin to look for ways to change it.
Change has happened before in opensource communities it can happen again.
Years ago, during the launch of Calypso, I called for a split of WP – one for WP.com users and one for WP.org users.
Thank God Calypso didn’t get forced on .org users!!!!!!!!!!!!!!
I believe this is finally that split.
But, as I stated in my article, me and my clients did not choose WP because it was easy to use or cheap to maintain. We have a need for what else it offers that platforms like Wix and such don’t.
There is nothing about ClassicPress that will change those two things no matter how many issues they address that have been overlooked.
And, I predict that keeping that base way of doing things for enterprise level sites will lead to the same situation that many corporations faced with having to stay with an old version if IE for their intranet use. All they did was postpone the inevitable of a costly rebuild.
I do believe that there are millions upon millions more site owners who will be good with what Gutenberg promises to become down the road. I base that on my own clients and the popularity of theme builders. I also base that on emerging tech like VR and other platform design that will meet the needs of the future web.
I have also never felt okay about the split CP has caused in the community and almost forcing devs to choose sides in a way. I’m much more on board with the vision that Morten, Yoast, and others have expressed about working from within on a change in leadership structure.
I also agree with Morten’s assessment of WP having enough users to flip a switch and change the web. That is where the influence will stay. It’s also where my clients will stay. So, that’s where I’m staying for now. I honestly don’t need to concern myself with what enterprise level site owners need. That’s not who I serve.
After watching the State Of Word address I was glad we are waiting to use Gutenberg. This release was defined for content areas only. And adding mobile, widgets and menus will be coming later. I never considered this would be divided this way.
Thanks MaAnna for your clear wrapup of the sessions. As end users this little tribe is everything to me!
I think it has been widely publicized that this Phase 1 of Gutenberg was only going to be a content editor.
Matt did speak about Phase 2 briefly on his blog, or an interview, I don’t remember. But few folks got wind of what it included. And nobody knew about Phases 3 and 4.
All of this speaks to the lack of communication and road map going on right now, and is what the dev community is so upset about.
Maybe it is time to leave WordPress altogether and move to its fork ClassicPress, especially if you run a business (as opposed to being mainly a blogger or publisher) and need some certainty around the platform you run your business on…
https://www.classicpress.net/democracy/
Thanks for the link to ClassicPress, Michael.
I’ve been following the progress for it and had reported on it in an earlier Tips Tuesday, but probably time to touch on it again.
To be honest, I’m in favor of WP returning to a roadmap that everyone has more input on. But not sure I’m ready to endorse a complete split right now. I’m sure folks who have an enterprise level site may see this differently.
Wow, thanks for your honest and detailed report. It’s a real eye-opener!
Fascinating post. Maybe I should have stayed on old Blogspot after all ! I’d read about Classicpress and thought, this is truly Life of Brian Pythonesque – the Judean Peoples Front splitting from the People Front of Judea. I imagine the new WP theme builder direction will suit millions of folk at the user end – eventually. I certainly feel let down by my current iThemes developer who dumped thousands of users on the garbage pile. It would be nice to have a theme that is always supported and growing and plugins that are always maintained. But this WP shift could nuke the whole open source development model which helped made WP so special in the first place. Has Matt been taken over by the ghost of Steve Jobs?? Classicpress will have a place in web land either way.
Interesting perspective Stevie!! And maybe a lot of folks are wonder if WP has become Apple and turning their back on it’s Steve Job who brought us here.
Lots of theme devs are having trouble staying profitable with all the change in the last couple of years. But what’s in store next will be make or break, I think.
Fascinating and sad all at the same time. Glad to be part of your community MaAnna!
I am so glad you’re part of the rich village on BlogAid, Tipper!!!
I would **love** to see you actively participate at forums.classicpress.net ! Voices like yours (and other’s here — of course, of course!!) are not only welcomed there but considered important and are heard. There are, most certainly, people who are excited about Gutenberg page design, as it will be, and who do not mind that WordPress truly isn’t an open-source community. Anyone watching knows that Matt’s for-profit company is using WP.org as it’s “freemium” and building on the backs of unpaid developers, contributors. That’s fine. He can do as he sees fit. But so can other humans. What is the way forward that you and others would like to see for WordPress without Gutenberg? What kind of a community do you want? How should it be supported so it’s healthy and grows?
Personally, I have always loved the Drupal approach of enabling scaling, extensibility through modules that are tools rather than plug-in’s that are solutions to specific problems. I learned how to use a “hammer” to build something of my own liking without having to learn the higher levels of javascript and React libraries. Yes, I know Javascript, PhP… but only what I have needed to know. To stay in WP and dev custom sites, I need to now dig back into JS, React, ec but have so little time to do that.
If there was a way to be given hammers, nails, saws, eg. the Drupal-way, within a WPress environment that also encourages ease, that, imho, would be the melding of the best of two worlds without the need to move into block components on the admin ui. Or maybe it should have all?
There’s also a need for a far better ecommerce solution. WooCommerce is familiar but surely we can satisfy user needs even better. I read the wishful comments and wonder..
ClassicPress is a fork without Gutenberg, yes. But the community, imho, has been given an amazing opportunity via ClassicPress to get into a truly democratic world and together stimulate ideas to become bigger ideas that give us the world we will oh-so-happy to be working in — together.
Yes, you can stay on the corporate path. Or you can join a crowd where everyone’s ideas are really wanted and help. Either way is fine. It’s your choice. And having choice is a good thing!!
Disclaimer: No, I’m not a member of CP founding group. I’ve been interacting with CP forum for awhile, tested ClassicPress, and have grown excited. I’m not only peace that I do not need to feel any angst over block growth but excited to have found a place where people really matter. I’m excited to grow CP into an amazing CMS. There will be bumps, I’m sure. Life guarantees that! But a hive full of buzzing bees where every bee is needed — dang, that just feels good!
I appreciate your enthusiasm, Sunni!!
While being heard is important, I can already see that 100% of my client base is going to embrace Gutenberg. So, I’m embracing it and helping them become empowered site owners who stay ahead of the curves that come.
Like I said, I changed my mindset to not being part of the dev community or the WP political drama any more. I just take it as it comes and make the very most of all the opportunities given.
Good for you! That’s the way! Decisions bring clarity so I support your choice, for what that’s worth. :-) My clients felt completely the opposite, despite my urgings to try it out. I actually am phasing out of providing web site development service to clients given what I see as the future. My company will only build its own online real estate/assets. But, that aside, I am going to stay abreast of what happens in WP as I anticipate two impacts. The first will be the value of web site development work once everyone can build their own and the second is what price point Automattic will eventually set for WP when it becomes SAAS. There’s no doubt in my mind that wordpress.org and wordpress.com will merge. The latter, I hope, will counter the devaluation that will be caused by the first. I know of no situation, ever, where high value has ever been the result of unlimited anything.
With real estate sites, I don’t blame you at all for getting out of the WP hoohaa!!!!! Those can be a bear on a good day with IDX integration and all.
And I’m in agreement with you about not doing WP for e-comm either.
I think both of those are better served by either a 3rd party platform or custom build.
I don’t have real estate sites?? Building online real estate simply means building sites on the land on the internet. :-)
I was one of the first businesses to build a site online way way way back when.. vanilla editors.. and the world ws so much fun. Not sure why I’m telling you that but it’s such a great memory for me of the days when we, as businesses, felt like we were settling a new frontier. And I still remember the first time my biz connected with a distant computer of a client’s.. typing cryptic commands on a screen. Ahhh those days! Such sweet memories of wonderfully collaborative times.