That leaves WordPress to compete with commercial offerings. Platforms such as Shopify and Wix come to mind.

Again, these systems can’t match WordPress’ market share. But they do have an advantage in marketing muscle. They have the resources to create a seamless campaign. They can speak to their targeted audience with clarity.

WordPress tends to struggle with messaging. You can see it at both the macro and micro levels. It covers big things like defining what the platform does and who it’s for. And it also happens with individual features.

The result is confusion – even among seasoned users. It also makes things harder for those who teach others. There’s a lack of consistency. Not to mention frequent changes to the terminology we use.

How much does this impact WordPress? Could it harm the software’s long-term future? And what can be done to create a more user-friendly vocabulary? Let’s take a deeper look at the words that define WordPress.

Who Are We Speaking To?

WordPress is an incredibly flexible platform. We can use it in a variety of ways. Thus, it appeals to both technical and non-technical users.

This appeal is both a blessing and a curse. On the bright side, WordPress continues to thrive in part because it offers so many possibilities.

But the words we use to describe WordPress don’t apply universally. A conversation among developers is bound to be more technical. Some terms are likely to confuse everyday users.

Yet it seems like developer speak is the dominant language in WordPress. We use exclusionary terms that are difficult for others to understand. You see it in the core software and third-party themes and plugins.

Perhaps this stems from where WordPress and its ecosystem come from. Many developers are responsible for both building and promoting products. Most aren’t marketers by trade.

Product descriptions and documentation tend to be written by developers. As such, developer speak is likely to be used. The content isn’t as user-friendly as it could be.

An Ever-Changing WordPress Core

The past decade has brought significant change to WordPress. The advent of the Block and Site editors has impacted content creation and website design.

Each of these items has undergone a descriptive overhaul. The Block Editor was initially referred to as “Gutenberg,” for example. The name was derived from the Gutenberg project, which oversees this and other features.

As for the Site Editor, it’s also a part of the Gutenberg project. But the feature was initially called “Full Site Editing.”

The names were eventually changed. They now more accurately reflect what each feature does. These are positive and well-intentioned moves. But the cat was already out of the bag, so to speak.

We now see these terms used interchangeably. This may not impact veteran WordPress developers very much. But what about new users? Do they understand that the Site Editor is the same as Full Site Editing? And what to make of the differences between block themes and classic themes?

We’ve created an unnecessarily confusing situation. And there is plenty of blame to go around. For instance, writers like myself have added fuel to the fire.

How Do We Fix the WordPress Word Scramble?

Here comes the difficult part. How do we use terminology that everyone can understand?

I think it starts with the WordPress project. Feature names should be reflective of what they do. But they should be named and described in the simplest of terms.

Perhaps this sounds like no big deal. But WordPress contributors have a lot on their plates. There’s only so much time to argue about names.

We did see a lot of thought put into this recently, however. The Command Pallete feature that shipped with WordPress 6.3 underwent a name change. Project contributors debated the merits of the original name (Command Center). They realized that it might be taken out of context and addressed the issue.

The creation of user-friendly terms will trickle down to the community. Writers will use it in their tutorials. And product makers will use it in their marketing efforts.

The community also has a responsibility. We must speak to WordPress users in plain language. We must limit the use of developer terms.

A little guidance would also help. WordPress has a developer-focused glossary of terms and a user-focused Semantics page. We should study them.

But perhaps we can educate product makers on methods for creating user-friendly marketing and documentation materials. That’s not necessarily a responsibility of the WordPress project.

Still, it could help to make the platform easier to understand. And it’s a part of keeping WordPress on top for the long term.

A User-Friendly Experience Starts with Words

The words we use matter. They can be the difference between friendly advice and an insult. People use them to form opinions.

What people read about WordPress will impact their decision to use it. If the software sounds confusing, they may head elsewhere. They may never fire up a demo to see for themselves.

It behooves all of us to think about how we talk about WordPress. Are we keeping new users in mind? Or are we losing them with technical jargon?

The impact may not be immediate. But by simplifying our language, we can attract more users than we lose. That’s highly important for the future of the project and its ecosystem.

The post What’s in a Word? WordPress Terminology at a Crossroads appeared first on Speckyboy Design Magazine.

But before we get too far into the weeds, it’s worth noting that block themes are fundamentally different than the classic WordPress themes you’re used to. They’re specifically built to work with FSE and the Gutenberg block editor. Think of them as an entirely separate category of theme.

Now that we have those details out of the way, it’s time to start looking at themes! Block themes are a growing segment, and therefore, it will take time for their numbers to approach the massive quantity of classic themes on the market.

Still, there are plenty of compelling options. And the fact that these themes are fairly simple to customize means that you have a lot of flexibility. If a particular design element doesn’t fit your needs, you can always start from scratch.

To help get you started on your journey, here are ten free WordPress block themes that are worthy of your consideration.

The post 10 Free WordPress Block Themes That Utilize Full Site Editing appeared first on Speckyboy Design Magazine.

For me, it starts with opening my favorite design tools. From there, I experiment with color and typography. Complimentary images are chosen to enhance the look. Layouts are built and refined. The result is (hopefully) good enough to share with clients. After a few revisions, it’s time to build.

However, technology is starting to blur the lines between designing and building. No-code tools like the WordPress Site Editor are throwing a wrench into the process. It’s now possible to handle design while building a website.

This method may be a boon for efficiency. But it may also lead to reduced originality in design. It might even discourage us from trying to level up our skills.

So, what does this mean for the future of web design? And where should we draw the line between convenience and originality? Let’s take a deeper look at how no-code tools are disrupting the design process.

The Good Parts of Browser-based Design

Designing a layout in a web browser isn’t new. Tools like Figma have brought this functionality into the mainstream. But there was still a separation between design and code.

No-code site builders have broken that barrier. And they offer some potential benefits.

Web design has often been theoretical. For example, you can create a beautiful mockup in Photoshop. But you won’t necessarily know how it will translate to a fully-functioning website.

Manipulating HTML and CSS to match the mockup isn’t always easy. Plus, adapting the design to mobile devices is a whole other process. The ability to accurately test while we design is a game changer.

Thus, a browser-based design eliminates some of the common issues we face. It’s a more direct way to work. That could mean launching a project faster. Revisions could also be easier to manage.

It’s Easy To Settle For ‘Good Enough’

The downside may be in how these tools change our mentality. For some, efficiency might become the primary focus. That could send the practice of detail-oriented design to the wayside.

We may be more inclined to stick with the default options. On the one hand, this makes perfect sense. It’s never a bad idea to go with components that work. But there’s also an argument that the finished product won’t reach its full potential.

To be fair, similar points have been raised about frameworks like Bootstrap. Because much of the hard work is done for us, it’s easy to settle for something good enough.

This is great for non-designers. They can create without investing in expensive tools. Nor do they need to understand code. At the same time, some finer touches may be missed. And that’s what tends to make a website stand out.

It’s not necessarily the tool’s fault, however. Ultimately, the decision to go all-in with great design is ours.

Combining Convenience and Great Design

The challenge, it seems, is in taking advantage of no-code tools without relying too heavily on their default styles. Maybe that requires us to keep those old-school techniques in the mix.

In practice, that means employing traditional design tools. After all, no one is forcing us to start from scratch in a web browser. It’s merely an option.

Thus, building prototypes with Figma, Photoshop, or whatever you’re comfortable with is still valid. This allows you to focus solely on the design. Plus, you won’t be limited by the constraints of most no-code tools.

That provides a solid launching point. When you enter your preferred no-code builder, you’ll already have a plan. This can guide you through the build process.

Working this way may require a period of adjustment. It can be difficult to create certain features with these tools. But in time, you can learn to adapt your prototypes to better fit the development environment.

Tools May Change, but They Don’t Have To Change You

The tools and techniques we use exist to help us achieve our goals. For web designers, it’s about building sites better and faster.

It’s easy to fall into a trap, though. You might, for instance, feel like you have to dive head-first into no-code tools. Or that you’ll need to abandon your previous workflow. That’s not the case.

These apps don’t have to completely change the way you design a website. Instead, they can be used to improve the process and create efficiencies.

For better or worse, these tools are disrupting the industry. But we can choose how much they disrupt us.

The post How No-Code Tools Disrupt the Design Process appeared first on Speckyboy Design Magazine.

WordPress 6.1 has brought about one of these hidden gems: the ability to use block template parts within a classic theme.

It takes the capabilities of block themes and ports them over to their classic counterparts. Classic themes still make up the overwhelming majority of the market. Therefore, it makes sense to bring them up to speed on the latest tools.

Let’s explore what this feature does and why you might want to use it. Then, we’ll demonstrate how you can implement it on your website.

What’s a Block Template Part?

WordPress 5.9 introduced Full Site Editing capabilities. When combined with a block theme, the feature allows users to edit various templates within the back end.

Block template parts represent any area of a website you’d like to manage within the WordPress Site Editor. Examples include the site’s header and footer. But they could also include niche areas as well.

Theoretically, a block template part can be as broad or narrow as you like. This allows web designers to define only the theme elements they want to make editable. At best, this offers convenience for site owners while protecting the layout from any major mishaps.

Unlike the custom templates that have long been used in classic themes, block template parts are saved as HTML files. They also consist of block markup, rather than PHP.

Classic themes have traditionally used the WordPress Customizer to make specific areas editable. The feature works well enough but lacks the advanced capabilities of the Site Editor. Now, there’s a way for these themes to move past those limitations.

Adding a Block Template Part to a Classic Theme

Adding a block template part to a classic WordPress theme is a relatively simple 4-step process. Here’s an example of how to set things up.

Step 1: Allow Block Template Parts in Your Theme

The first step involves allowing your theme to use block template parts. This can be accomplished by adding a code snippet to your theme’s functions.php file:

Code snippet courtesy of Learn WordPress.

Note that if your theme’s functions.php file already has a function that adds theme support for other items, you’d only need to paste add_theme_support( 'block-template-parts' ); within the existing function.

Step 2: Design Your Template in the Block Editor

Next, it’s time to fire up the WordPress Block Editor. The easiest way to go about this step is to create a new page – we’ll call ours “Test Block Part”. It can be deleted once we have our block template part up and running.

Within this page, we’ve created a simple two-column layout. It includes our fictional client’s contact information and links to their social media profiles. Everything here uses standard blocks included with WordPress core.

The idea is to allow our client to make edits to this information as needed – but without having to touch the rest of the site’s layout.

Step 3: Copy and Paste Block Markup into an HTML File

Now that we have our layout built, it’s time to copy and paste the block markup into an HTML file.

There are a couple of options for copying the block markup:

1. Select the blocks you’d like to copy within the Block Editor and enter CTRL + C (or COMMAND + C on a Mac) to copy the markup, OR;
2. Enter the WordPress Code Editor for your page by clicking on the Options button within the Block Editor, then copy the relevant markup;

Next, open the code or text editing app of your choice and paste the block markup into a new file. Our markup looks like this:

Save the file as an HTML document into the /parts directory of your theme (create the folder if it doesn’t already exist). Note that you don’t need anything else in the file besides the block markup.

For our example, we’ll call our file footer-contact-info.html. Make note of the file’s name, as we’ll need it in the final step.

Step 4: Add the Block Part Template to Your Theme

Now that we have our block part template created, we’ll need to add it to a PHP template in our classic theme.

WordPress has a built-in function called block_template_part() that we can use to call our block template part into the theme. It uses the HTML file’s name (minus the “.html” extension) to locate the template. Here’s what our code looks like:

We can add this function wherever we’d like the block template part to display. In this case, we’ll add it to our footer.php template.

All that’s left is to upload our updated theme files to the server. Once that’s complete, we’ll refresh the page and find our block template part proudly displaying at the bottom of the site.

Edit Your Block Template Part Anytime

Whenever we need to make a change, our custom block template part is only a few clicks away. To find the template, visit Appearance > Template Parts, then click on the template’s name (footer-contact-info).

Edits can be made via the Block Editor – just like any WordPress page or post. Save your changes and they’ll appear on the front end of the website.

*Note: Some early implementations of this feature contained a bug that caused a block template part to be uneditable within WordPress. Adding a theme.json file to the theme temporarily fixes the issue.

Bringing Classic WordPress Themes into the Block Era

The ability to use block template parts in a classic WordPress theme is a step forward. Theme developers can stick with the power and flexibility offered by PHP-based themes while adding block template support where needed.

It’s also a way to open specific elements up to back-end editing without having to switch to a block theme. The process is easy to implement and much less labor-intensive than starting from scratch. The result is savings in both time and money.

In addition, it offers us a way to move beyond the Customizer. That feature will likely be phased out over time, so the ability to switch to block template parts helps us get a head start on migration.

Best of all, there are tons of potential use cases for this functionality. It may be just the thing you need to add a layer of convenience to your next WordPress project.

The post How to Use Block Template Parts in a Classic WordPress Theme appeared first on Speckyboy Design Magazine.

Signs of that evolution are everywhere. The block editor means we no longer need a page builder plugin to craft custom layouts. And thanks to the site editor and block themes, an entire website can be built without writing a line of code.

Virtually every major component of building and maintaining a website has changed. And there’s every reason to believe that the innovation process will continue. What WordPress is today is only laying the foundation for tomorrow.

But how will WordPress change? While we don’t have a crystal ball, we can see plenty of areas that are ripe for improvement. Some may be solved by updates to WordPress core, while the plugin and theme ecosystem could tackle others.

With that, let’s try and predict the next opportunities for innovation in WordPress. They may not qualify as sexy, but they’re important nonetheless.

Making Website Data Easier to Access

Data storage and retrieval have long been a challenge for WordPress developers. Sure, everything is stored in a singular database. But things can get exceedingly complicated in a hurry.

Standard posts and pages are easy enough to import or export. But when you move into the realm of data generated by plugins, it’s a different story.

That’s because plugin authors have numerous options for writing to the database. On the surface, this freedom seems like a positive. It allows developers to store and retrieve data in a way that makes the most sense for their needs.

But for the rest of us, it can be a nightmare. Each plugin we install manages data in its own way. Thus, piecing together a coherent report is nearly impossible – unless you’re proficient with PHP.

For example, let’s imagine an eCommerce website that also has members-only content. We might install WooCommerce to power the online store, while a separate membership plugin restricts access to content.

If we just want to export data related to one of these site functions, it’s easy enough. But what if we combine each aspect into a single report? Not so easy. Data can be stored in different database tables and different formats. Even with the help of plugins designed to export data, it often takes custom code to make this work.

The obstacles to accessing data are large and complex. But there’s an opportunity for either WordPress core or a brilliant plugin developer to put it within reach of site owners.

Creating a Must-Have Block Theme

The idea behind the WordPress Site Editor (aka Full Site Editing) is simple: to empower anyone to build a custom website within a code-free environment.

The feature officially became a part of WordPress core in version 5.9. Since then, a steady stream of newfangled block themes has been released. Meanwhile, the feature’s functionality and user experience continue to be refined.

Progress aside, we’ve yet to see a rush of users migrate to this new way of building websites. The theme market continues to be saturated with Classic Themes. Plus, developers may still be wary of allowing key layout elements open to editing.

What’s missing is a compelling reason to switch. Part of that may be a matter of increasing what the Site Editor is capable of. But perhaps a transformative product (or 100) is also needed to attract user interest.

Imagine a block theme that is both powerful and versatile. One that offers a wide range of style variations to fit a multitude of use cases. And its author will hopefully have learned from the past mistakes of the third-party theme market.

A theme that is lean, performant, and easy to customize could be just the thing to entice users. Luckily, the market is wide open. That means there is plenty of room for competition in this space.

Bringing Top-Notch Performance to WordPress

Website performance is complicated. It starts with a high-powered server that is optimized for speed. Then there’s the website, where code and assets must be used efficiently. Add databases and calls to third-party APIs into the mix, and there are plenty of potential bottlenecks.

The WordPress Core Performance team has been established to help bring the CMS up to speed. And they’ve already made significant progress in the area of query caching.

Still, the WordPress ecosystem further complicates the process. Themes and plugins can vary greatly in terms of resource requirements. Some make multiple database calls, while others make extensive use of scripts and styles. And even items that perform well enough on small sites could struggle at scale.

There are a variety of caching plugins available to get the most performance out of a website. But neither they nor WordPress core can account for a bloated theme or plugin.

With that, some developers have decided to (mostly) bypass the ecosystem by running headless installations. With a WordPress back-end that handles content creation, a static front-end removes database calls from the equation. This can result in blazing-fast page loads, with the caveat that some plugin functionality won’t carry over.

Tools that simplify the process of building headless WordPress websites would be welcomed. And bonus points for those that can keep plugin functionality (shopping carts, forms, etc.) going on the static side or via a hybrid approach. Much progress is being made, and it will be exciting to see what breakthroughs come next.

That doesn’t mean WordPress core shouldn’t focus on speed, though. For most users, keeping a traditional install that uses a database is still the reality. Every step towards higher performance counts.

Looking for the Next Big Thing in WordPress

The predictions above represent opportunities that already exist. One or more people can take on these challenges and create a solution that makes WordPress better/easier/faster. But they’re far from the only ones out there.

The great thing about an open-source CMS is that developers are only limited by their imaginations. Thus, we could see innovations that haven’t even been considered yet.

As WordPress matures, the need to create a powerful and seamless experience increases. A community full of creative minds is hard at work, plotting the next big thing. We can’t wait to see what they come up with.

The post Predicting the Next Opportunities for WordPress Innovation appeared first on Speckyboy Design Magazine.

But power can be a double-edged sword. On the flip side, WordPress does have a learning curve. This makes it difficult for a first-time user to build a website – particularly those who aren’t already familiar with code.

WordPress has made efforts to simplify site-building. Block themes and Full Site Editing (FSE) are prime examples. Together, they are an attempt to empower non-designers.

And while those new tools are a step forward, they aren’t necessarily enough to pry a user away from DIY platforms such as Squarespace or Wix. There are still extra layers of complexity to WordPress, and not everyone is interested in learning them.

Yes, WordPress would love to capture the do-it-yourself (DIY) market – but how? Here are a few ideas on how the world’s biggest CMS can become even friendlier to newbies.

Modernize the Onboarding Experience

A new user can be forgiven for feeling overwhelmed the first time they log into the WordPress dashboard. While a fresh installation does provide an introductory widget, there are still a lot of visuals to take in. For some, it may feel like being dumped in the middle of an alien planet.

Where to even begin? Without reading through a tutorial (or 10), what comes after installing WordPress could seem like a mystery to the inexperienced eye. How do I install a theme? Where are all of these great plugins I’ve heard about?

This is where a modern onboarding experience could be a big help. Imagine an (easily dismissible) interface that greets new users and takes them on a tour of WordPress. It might show, among other things:

• Where to find themes;
• Where to find plugins;
• How to set a custom home page;
• How to create a menu;
• Links to official WordPress tutorials;

That initial onboarding could provide a gateway to more related guides. Navigating to the Settings > General screen, for example, could provide a quick overview of important options such as setting a time zone and site title.

While it’s possible to go a bit too far with onboarding, it has the potential to make a positive impact on users.

A Carefully Curated View of the Ecosystem

If the WordPress admin can be overwhelming, what to make of the massive theme and plugin ecosystem? It’s another area where users (experienced or not) can become lost.

Quantity is an issue – but so is quality. Some themes and plugins are simply better than others when it comes to functionality, stability, and support. Making the wrong choices here could be enough to drive a user away from the platform altogether.

One possible solution is curation. When new, non-technical users have access to a shortlist of the best (or most viable, at least) options for a given need, they’ll have a better chance of succeeding.

The biggest question is who would be responsible for curating theme and plugin lists. Any bias towards specific items by the WordPress project would likely be frowned upon. Thus, it seems more reasonable for third parties to take on the task.

Managed WordPress hosting providers might be the most natural fit. Many are acquiring plugins and themes, anyway. And they would have the ability to create a UI that combines their “best-of” lists within the dashboard.

Realistically speaking, no list will be perfect. And there will always be questions of bias. But if the idea is to guide DIY users, curation could serve as a solid starting point. At the very least, it would steer people away from products that are known to be of poor quality or are no longer being maintained.

A More Uniform Admin UI

Clicking around within the WordPress dashboard can result in vastly different visual experiences. The block editor is sleek and modern. Core settings screens are minimal. Meanwhile, some plugins and theme screens offer unique looks.

Even the once-ubiquitous left sidebar menu takes a back seat now and again. It’s hidden by default in the block and site editors, and some plugins do the same. The result is that getting from place to place has become harder.

For longtime WordPress users, this might be a slight inconvenience. But those just getting their feet wet with the CMS could become confused by both the differences in UI and the sheer number of available options.

Exercising control of what plugin and theme authors can or can’t do in terms of UI may not be realistic for an open-source project. But a more uniform core admin experience may make WordPress a bit less intimidating.

And, as WordPress has done with other features, a streamlined admin could be purely optional. This would allow those who are comfortable with the current setup to stay where they are, while everyone else gets a fresh new look.

A native WordPress settings screen (left), alongside the custom UI from the Slider Revolution plugin (right).

Outreach That Shows What WordPress Can Do

Reaching new users is a challenge for any software. But, unlike those corporate DIY platforms, WordPress doesn’t have a marketing machine to do its bidding – nor does it have the budget to build one.

However, it does have something that its competitors don’t: a large and passionate community. These dedicated designers, developers, and users could play a key role in attracting the DIY crowd.

There is a myriad of ways that the WordPress community can help. For example, tutorials that demonstrate how to put a basic website together with a block theme. Or with products designed to make the task super simple for non-technical users.

On a more personal level, WordCamps can serve as a wonderful introduction to the CMS. Sessions aimed at beginners and non-coders have great potential. And the one-on-one connections of an in-person event are invaluable for everyone involved.

When you think about it, these experiences are what brought a lot of us to WordPress in the first place. But as the software and community have evolved, content for newbies hasn’t always kept pace. This is something everyone can help to change.

Making WordPress the Top Choice for DIY

There has been a lot of effort to make WordPress a DIY-friendly tool. The software has undergone some major transformations when it comes to building themes and content. And it will continue in this direction for the foreseeable future.

The ideas above aren’t perfect. There may be challenges and consequences I didn’t consider. But their goal is to keep things going in that direction and spark conversation within the community.

Because, as the web creates more seamless experiences, it’s important to consider how WordPress can join in the fun. How can we best ensure that anyone can create a basic website within a couple of hours?

That’s not to say we shouldn’t still have the ability to build larger, more complex sites. This capability is as important as ever. But if WordPress wants to continue in its goal of democratizing publishing, it has to keep the software accessible to people of every skill level.

The post What Can WordPress Do to Appeal to the DIY Market? appeared first on Speckyboy Design Magazine.

It was also decided during this time to refer to non-block-based themes as “classic.” In essence, a classic theme is based on PHP and does not include block markup. This term could apply to products going back to the original Kubrick (Default) theme through to today’s offerings.

But despite all of the hype regarding block themes, their classic counterparts continue to dominate the market. As of this writing, there are over 10,000 listings in the official WordPress theme repository. By my count, block themes make up approximately 1% of the total. And they haven’t exactly set the commercial marketplaces ablaze, either.

And while there are some interesting use cases for block themes/FSE, it’s safe to say that any shift in this direction has been slow. Meanwhile, classic themes are still receiving some love from WordPress core.

It looks like any sort of block theme revolution will have to wait. Classic WordPress themes aren’t going away – and here’s why.

Code Brings Power and Flexibility to WordPress

A no-code workflow adds a layer of convenience to web development. Not every task should require in-depth knowledge of CSS, HTML, or PHP. But this approach can only get you so far.

Code is still the primary solution for building advanced websites. Whether it’s some custom functionality or a non-standard layout, code is how we bring these ideas to life.

No readymade plugin or theme (block or classic) can account for every possible need. And the ability to make little tweaks or create something entirely new has long been a strength of WordPress. It’s a big reason why the content management system (CMS) has become so widely used.

This power and flexibility are what sets classic themes apart. Modern websites are rarely one-size-fits-all. Thus, they often require us to build to suit a specific need. A custom-made classic theme can do that. Block themes aren’t there quite yet.

Classic Themes Continue to Evolve

Block themes have received a lot of attention recently – and rightfully so. But that doesn’t mean classic themes have been banished to the dustbin. New features continue to be added – including some that bring the latest functionality.

Among the more exciting additions is the ability to use FSE within a classic theme. That’s right, block-based template parts will be supported in a future version. This will allow developers to open up specific portions of the theme for tweaking from within WordPress.

It’s a big step forward. We can continue to build client-proof websites while enabling no-code access where it makes sense. And it provides a path for moving away from the Customizer API that is likely to disappear someday.

And those who want fine-grain control over the block editor can also leverage the theme.json file. It lets us define block styles and other related functionality. Content creators can then focus on writing rather than having to worry about how the design will look.

These additions will ensure that classic themes remain a viable option. Using them won’t prevent you from taking advantage of new features in WordPress core.

There’s Not Much Reason to Change

Not everyone is ready to make major changes to their workflow. And for all of the benefits of block themes, they offer a decidedly different experience for developers. Building and interacting with them requires an adjustment.

Meanwhile, classic themes have been a staple of WordPress development for years. The community has comfort and familiarity with how things work. They’re well documented. And if they continue to do the job effectively, what’s the impetus for change?

The features that are unique to block themes aren’t necessarily a fit for every project. Meanwhile, the aforementioned flexibility keeps us coming back to classic themes.

In a few years, this could be a different story. By then, block themes may have improved so much that they’re considered a must-use technology.

That’s not currently the case, though. Until there is a significant advantage to switching theme types, many developers will likely stick with what they know.

Don’t Let the Name ‘Classic’ Fool You

The term “classic” is thrown around quite a bit within the WordPress ecosystem. We often associate it with the Classic Editor – which was replaced by the Gutenberg block editor years ago. On some level, it makes sense that themes would also adopt this moniker.

But names can be interpreted in different ways. For some, “classic” may read as an antiquated tool that’s no longer useful. That’s a shame because nothing could be further from reality when it comes to classic themes.

If anything, they’re the tried-and-true path for building a custom website. And that’s likely to continue for years to come.

The post Why Classic WordPress Themes Aren’t Going Away appeared first on Speckyboy Design Magazine.

While that represents progress relative to the old Classic Editor, you’ll still need a bit of help if you want to do anything more than edit colors or font sizes. As of version 6.0, advanced styling for individual blocks isn’t readily available in a default installation of WordPress.

There are some fairly simple workarounds, however. Today, we’ll introduce you to three ways to enhance your custom layouts with the WordPress block editor. They’ll help you turn something basic into a highly-customized setup.

Option #1: Write Custom CSS

If you’re comfortable writing code, you can customize pretty much every aspect of your block editor layout via CSS. It’s perfect for those who are already building custom WordPress themes and want to client-proof their work.

How you go about the process depends on how widespread you want the styles to be implemented. In this example, we’re looking for a one-off solution. Therefore, the easiest method is to add a custom CSS class to a block.

The block editor’s settings panel has an area just for this purpose:

1. Click on the block you want to style;
2. Click the Advanced panel in the settings area to the right;
3. Add your custom CSS class name to the Additional CSS class(es) field;
4. Save your work;

Here, we’ve added the custom class rounded-corners to an image block.

Next, we’ll add that class to our theme’s CSS and define some styles. If your theme uses the WordPress Customizer, code can also be placed into its Additional CSS panel.

.rounded-corners {
     border-radius: 10px;
}

Note that you’ll also want to add this code to your theme’s editor-style.css file (if it exists) to see your custom styles reflected within the block editor.

Looking at the front end, our image now sports some beautifully rounded corners!

Option #2: Set Default Styles via Theme.json

Among the early drawbacks of the block editor was the difficulty in applying consistent styling. You had to target several CSS classes that were defined in the core software.

The advent of the theme.json file greatly simplifies the process. Instead of searching around for all of the relevant CSS, you can define block styles directly within a single file. And you have the flexibility to target blocks as broadly or narrowly as you’d like.

Layout and design aspects such as custom color palettes, typography, and spacing can be defined via theme.json. Best of all, this feature is compatible with all WordPress themes.

If you’re already using a newfangled block theme on your website, you can edit the theme.json file within the theme’s root folder (keep a backup of the original – just in case). WordPress provides some documentation with examples to guide you.

For those using classic themes or building from scratch, tools such as ThemeGen allow you to visually build a theme.json file. Select your styles, export the theme.json file and drop it into your theme’s root folder. WordPress will recognize the file and apply the styles. It even writes the CSS for you!

Option #3: Use the Editor Plus Plugin

Looking for a no-code solution and don’t want to deal with theme.json? The Editor Plus plugin has you covered. It allows for advanced styling of block layouts directly from within the editor.

Activate the plugin, and the default block editor settings area will gain a variety of new panels. From there, you can set custom padding, margins, borders, sizing, and a whole lot more. If you want visual control over every aspect of your site’s layout, Editor Plus offers a straightforward solution.

The plugin also adds a handy selection of custom blocks as well. Features such as accordion UIs, icons, and progress bars offer a bit more style and content flexibility.

Going this route does require a long-term commitment, however. Disabling the plugin will result in a loss of any custom styles you’ve created. Therefore, it’s worth considering the benefits and drawbacks before making a decision.

Take Your WordPress Page Layouts to the Next Level

In some ways, it makes sense to think of the block editor as a starting point. With it, we can create all manner of custom layouts. But until there are more configuration options added to WordPress core, it requires some extra effort to fully customize styling.

The three options above provide a path to leveling up your block layout styles. Whether you’re looking to enhance a single element or site-wide features, there’s a method for doing so.

All things considered, theme.json may be the best long-term solution. It’s baked into WordPress core, and everything’s contained within a single file. From a maintenance perspective, this is preferable to the other options.

However, there are plenty of reasons to choose custom CSS or even a plugin. In the end, it’s about finding the best fit for your needs and workflow.

The good news is that you don’t have to settle for the default block editor styles. Use your favorite tool and start building!

The post 3 Ways to Enhance Custom Layouts with the WordPress Block Editor appeared first on Speckyboy Design Magazine.

Its massive theme and plugin ecosystem have also seen its share of changes. We’ve witnessed solo entrepreneurs launching products, nurturing their growth, and eventually selling off to larger companies.

In between, there have been numerous success stories. Some products that were born in the days of the Classic Editor have happily adapted to the Gutenberg block editor. But that doesn’t mean it was an easy transition.

With that, I put out a call for WordPress product founders. I wanted to ask them about the changes they’ve seen over their time in the community. And, if they were launching their product today, what they might do differently.

I received quite a few responses! What follows is a sampling of what these entrepreneurs had to say. Note that some responses have been lightly edited for clarity/brevity.

A Sampling of Responses

Cameron Jones

Brand/Product: Mongoose Marketplace
Launched: 2018

What’s changed in WordPress: The biggest change in the ecosystem without a doubt has been the introduction of the block editor.

What I’d do differently: If I was just starting out today, I would approach most of my plugins with a blocks-first mentality. By way of being more of a PHP developer, I tend to build classic widgets and shortcodes before I consider building a block, whereas if I was starting out now I would start by building a block only and only consider adding a shortcode and/or classic widget if there became sufficient demand for it.

Derek Ashauer

Brand/Product: Sunshine Photo Cart
Launched: 2013

What’s changed in WordPress: The biggest change that has had an impact on Sunshine Photo Cart has been the consolidation of plugin companies. Instead of small developers who are time and resource-restricted competing, suddenly one gets backing by a larger company with marketing experience and resources and they can then really run. For me, that is what has happened as NextGen is a main competitor and they now have major resource backing where I am still just one person doing it as a side gig.

What I’d do differently: If I started again, I would definitely partner with at least one other developer and ideally a marketing person. All the larger plugins that have become companies (that I am aware of) were founded by multiple people. It’s just too hard to do everything on your own even if you know it all and grow.

I would also start smaller in scope for a first project. I should have made smaller plugins first before going all out on an e-commerce plugin first.

Kathy Darling

Brand/Product: WooCommerce Name Your Price
Launched: 2012

What’s changed in WordPress: I think the WordPress ecosystem has gotten bigger, more mature, and more competitive. I was one of the first to build this feature for WooCommerce. I’ve therefore benefitted from their growth. And now I also benefit from having been around and having built a solid reputation within my niche.

What I’d do differently: But now there are multiple options for almost any feature you can think of so you have to find ways to make yourself stand out. If I were launching today, I think I would have to spend more time on marketing and really talking to potential customers about what their pain points are. If you can address those pain points with really good interfaces and back it up with solid customer service I think there are still niche markets that need addressing.

Jack Arturo

Brand/Product: WP Fusion
Launched: 2015

What’s changed in WordPress: The move to JavaScript frameworks in the admin has probably been the biggest change. React + Gutenberg of course, but also many companies choose to go with Vue or Angular instead. It’s made the kinds of integrations we do with other plugins much more difficult.

What I’d do differently: If I was launching something now, I’d probably start SaaS-first, and then build a helper plugin to connect to the SaaS. That’d give us better reliability (since we manage the servers), and probably cut down on plugin conflicts. Plus, then we’d have an easier time moving to other platforms (Shopify, Squarespace, etc.). I really like how Weglot has managed to build something that works on every platform.

Gareth Harris

Brand/Product: Plugin Republic
Launched: 2018

What’s changed in WordPress: The biggest changes in that time in the ecosystem are:

The move towards consolidation – even just a few years ago there seemed to be a lot more shops being run by a single developer.

The move away from marketplaces – it seems to me that CodeCanyon et al are no longer the first places for people to look for plugins (this is probably a good thing).

What I’d do differently: If I was launching today, I’d spend a lot more time on marketing. I spent way too much time adding great features to plugins that nobody knew existed.

Mark Westguard

Brand/Product: WS Form
Launched: 2018

What’s changed in WordPress: I think the biggest change we have seen since launching WS Form has been the progression with Gutenberg (now Block Editor). It was released days after we launched WS Form and we made sure we had a block ready from day one. I remember speaking with Matt Mullenweg at WordCamp Nashville in December 2018 and his first question was “Are you Gutenberg ready”, which I was pleased to say we were! Gutenberg has evolved significantly since then and continues to do so which is something we, as plugin developers, have to keep up with. We’ve re-written our Gutenberg block twice.

What I’d do differently: Marketing WS Form would have certainly have been done differently. I’ve learned that the WordPress community, as well as being awesome, is fragmented into many small interest groups and there is no single channel you can go to promote your product. It is about taking part in that community and offering true value, not only in the topic of your product, that helps get your brand name out there. We try to contribute to the WordPress ecosystem as much as we can both in sponsorships and also with our time.

A Changing WordPress Landscape Requires Adaptation

For those who launched a WordPress-related product or service even a few years ago, one thing is certain: the ecosystem has changed. That’s a result of both the evolution of WordPress core and the ensuing string of product acquisitions.

Taken together, the landscape is indeed different these days. And entrepreneurs have had to adapt to new ways of building websites and increased competition. It’s not only end-users who have been impacted.

Ultimately, whether or not a product survives will depend on how it evolves along with WordPress. In addition, it will have to identify and reach a very niche audience.

Thanks to all of the entrepreneurs who took the time to respond to my questions! Their stories reflect the current state of WordPress, and I sense that many others will relate to them.

The post WordPress Product Founders on What They’d Do Differently appeared first on Speckyboy Design Magazine.

The software saw quite a few ups and downs along the way. It started as a challenger to Netscape and didn’t take long to become a market leader. But there was also a lack of support for standards, a push for proprietary code, and a monopolistic scandal.

For web designers, IE was the thing we loved to hate. If you tried to build a cross-browser-compliant website during its heyday, you likely ran into some trouble when testing in Microsoft’s browser.

Layouts could be messy, as support for newer techniques like CSS Grid and Flexbox were lacking. And it seemed like there was always that one client or customer who used IE – meaning you had to provide a fallback.

While no longer having to support IE is a reason to celebrate, its demise does bring about a bittersweet feeling. What will we do without our favorite nemesis? Who or what could replace it?

It just so happens that the modern web has several potential candidates. Here are a few who could take the throne.

Tech Companies with Outsized Influence

For a time, Microsoft had a stranglehold on the browser market. And IE could be considered a means for the corporate giant to put its mark on how the web would evolve. But as the browser stumbled, the company’s influence shrunk along with it.

These days there are a handful of companies that have a huge say in what happens on the web. A decree from any one of them can send web designers scrambling to account for whatever change they’ve decided to implement. Among them:

Google

It seems like everything Google does has an impact on our industry. For example, a change to its search algorithm means having to tweak SEO to stay relevant.

But it goes well beyond their search product. As the current top dog in the browser battle, Chrome is in a position to adopt standards and push technologies that potentially benefit Google. Competitors such as Firefox are struggling to survive, let alone take a bigger piece of the pie.

Core Web Vitals now dictates what performance metrics we need to adopt. And its AMP project compelled publishers to participate – even if it wasn’t in their best interest.

Microsoft may have dreamed of such influence, but Google achieved it.

Facebook

With billions of users, Facebook controls mountains of data. And how they decide to use it affects both everyday people and businesses.

If you use the service, consider the typical items you see in your feed. Facebook has decided what’s relevant to you. It’s possible to see updates from friends and family, but you’ll also get a mix of posts from other sources – whether you’ve subscribed to them or not.

For businesses and non-profits, reaching your audience (even the ones who “like” your page) can be incredibly difficult. That is unless you pay to promote your content.

More directly of concern to web designers, implementing Facebook’s API into your projects means giving up some level of control when it comes to performance and privacy.

Like Google, Facebook’s services are often seen as necessary and unavoidable. As such, web designers have to deal with them – like it or not.

No-Code Tools

I know, we’re all supposed to embrace the no-code revolution. And there’s something to be said for tools that do some of the dirty work for us. Why craft a CSS Grid layout when a page builder can do it for us?

Many of these products do their job pretty well. The WordPress Gutenberg block editor, for example, has vastly improved since its initial release. There’s a learning curve. But once you get accustomed to how this and other no-code tools work, you can achieve some solid results.

But they can also be quite frustrating to work with. For example, if you want to implement a particular feature that one of these tools doesn’t offer, it can require an uncomfortable (and possibly unsustainable) workaround.

Performance can also suffer. Some tools add lots of overhead in the form of JavaScript or CSS. And, even if the code works, it can still conflict with other parts of your website.

While the right tool adds a layer of convenience, it may also require us to accept some serious tradeoffs. That could draw the ire of many a web designer.

Malware and Malicious Actors

Perhaps there’s never been a more dangerous time to manage a website. Malware is all around us and tends to rear its ugly head at the most inconvenient of moments.

And the people who create and spread this malicious code aren’t being effectively deterred. If anything, the market for bad actors is continually growing. Not to mention the increased sophistication of their attacks.

It has become a recurring nightmare for web designers. Cleaning up SEO spam, restoring infected databases, and attempting to harden code – only for it to happen again and again. It’s a real-life game of Whack-a-Mole.

Even worse is that solutions don’t appear to be on the horizon. Both web hosts and software developers are trying to level up, but key breakthroughs seem hard to come by. And now insurance companies are starting to take web security into account when selling policies. That’s not going to help.

The burden of securing the websites we manage is enough to make any web designer question their career choices.

The New Multi-Pronged Nemesis

When Internet Explorer debuted, the web was still a relatively new phenomenon. People were excited by the prospect of a truly global community and the information superhighway.

Save for Google and a few other services, IE was one of the last remaining relics of that era. And unlike those that are still around, it never quite evolved to the point of staying relevant. It may be that IE’s only claim to fame in the past 15-20 years was that it made web design harder.

This made it stand out in a way that Microsoft couldn’t have imagined back in the 1990s. It’s likely the reason they released IE’s successor, Edge. IE was simply too tainted to continue.

Today, there is no singular bogeyman. The web is multitudes the size and complexity of what it was back in the day. And, as referenced above, there are several companies, products, and maladies that impact us. You could theoretically pick a new one to curse each day.

IE was alone in its time and an easy target. In some ways, that almost seems quaint compared to the environment web designers face today.

A single nemesis that tries to ruin our good time? If only.

The post After Internet Explorer, Who Will Be the Web’s Next Nemesis? appeared first on Speckyboy Design Magazine.