WordPress websites consist of a theme and plugins. And they rely on a database. That makes diagnosing slow page loads difficult. There are so many places to look.

What’s more, poor performance can appear out of the blue. A software update or a change by your web host could be the culprit. But how can you be sure?

We’re here to help! Here are a few tips for diagnosing a slow WordPress website. They’ll help you spot common (and not-so-common) performance issues.

Start With What You Can See

The first step is to assess what you see when your website loads. What you find could help you determine the next step.

Observe your website and think about the following:

Where Is the Slowness Occurring?

Poor performance can come in many forms. For example, it could be a sitewide issue. But it could be localized to a single page. Or maybe you’re only noticing sluggish behavior in the dashboard.

Make note of where you are (and aren’t) experiencing problems. This can help you narrow down potential causes.

Are There Any Obvious Signs?

Sometimes the problem is right in front of you. Elements such as image sliders or videos can slow down a page. Or you might notice that third-party content (like a social media widget) is loading slowly.

There are no guarantees. But you might gain insight into the slowdown. If not, there are still plenty of things you can do.

Use Some Helpful Tools

Several tools are available to help you diagnose a slow website. Performance scanners like Google’s PageSpeed Insights will provide a laundry list of potential issues.

But the reports can be a bit dense. Thus, finding key factors in poor performance isn’t straightforward.

Here, we’ll focus on a few other tools worth checking out:

Web Browser Developer Tools

Your web browser’s developer tools include powerful features. They’re the place to catch page load errors. And they can display critical information about what’s happening behind the scenes.

Modern browsers come packed with advanced developer tools. For our purposes, we’ll concentrate on the console and network panels.

Console

Let’s start with the browser console. This tool provides a real-time view of errors and warnings. It’s a handy listing of any issues impacting a page.

Perhaps the biggest telltale sign is a 404 Not Found error. That indicates a specific resource couldn’t be loaded. This could be a script, image, stylesheet, or font. The web server is wasting precious time looking for something that can’t be found.

The console will also fill you in on JavaScript errors and security notices. These can also get in the way of a faster page load.

Network

The network tool provides a listing of each request made. It provides context about what’s happening while the page loads.

For instance, you can see the amount of data transferred and the time it took. This helps you see which resources are weighing down a page.

In addition, HTTP response codes will point out blocked or missing resources.

Query Monitor

Performance issues directly related to WordPress can be difficult to diagnose. That’s where Query Monitor comes in. This free plugin provides a glimpse of how the CMS works in both the front and back ends.

Query Monitor shows you things that browser developer tools can’t. And it does so with a well-organized user interface. It adds a menu within the WordPress admin bar.

Among the information you’ll find:

• Database queries (with the ability to point out slow queries);
• PHP errors and warnings;
• A list of all enqueued scripts and styles;
• HTTP API requests;
• Server version information;

It’s a great tool for finding problematic PHP code and slow database queries. Query Monitor’s ability to point to specific items makes troubleshooting easier.

And the available add-on plugins allow you to dig even further. They can help with WooCommerce shops, BuddyPress/bbPress installs, and more.

Query Monitor can help you find the proverbial needle in a haystack.

You’ve Found the Culprit – Now What?

Hopefully, the tips above helped you identify the problem. What to do next?

Making performance tweaks is a topic of its own. Much depends on the source of your issue. However, there are a few universal steps to take.

First, be sure to repair any errors. Patch up any problematic PHP. Replace or remove references to missing resources. Remove third-party content that is taking too long to load. Consider this the low-hanging fruit in the process.

Next, look at how your theme and plugins are impacting performance. If you have outdated items installed, it may be time to replace them. The good news is that there are usually plenty of options within the WordPress ecosystem.

Finally, take a look at your web hosting arrangement. A slow file or database server is a drag on any website. Implementing tools like object caching or content delivery networks (CDN) can be difference-makers.

Be sure that your site has adequate storage, processing threads, and memory. A lack of resources is one of the most common performance issues you’ll face.

By addressing all three areas (code, theme/plugins, and server), you’ll be able to make significant performance gains.

Kick WordPress Performance up a Notch

There could be myriad reasons why your WordPress website isn’t performing well. Anything from a poorly-coded plugin to a buggy server could be to blame.

Sometimes you’ll get lucky and the root cause will be apparent. But you’ll more likely have to do some sleuthing to get to the bottom of it.

There are tools to help you pinpoint any problems. It starts with your browser’s developer tools. But you can also use WordPress-specific items like Query Monitor. Together, they’ll paint a clearer picture of what’s slowing down your site.

From there, you can take any necessary steps to boost speed. The process isn’t always easy. But it all starts with gathering the right information.

The post What’s Slowing Down Your WordPress Website? appeared first on Speckyboy Design Magazine.

Web designers spend hours perfecting a site’s layout, functionality, and content. However, we don’t always pay attention to the 404. Why is that?

It’s easy to take the 404 page for granted. It’s often hidden for one. We may not think of it until we stumble upon the page.

Content management systems (CMS) like WordPress make them even less visible. That’s because themes often come with preconfigured templates. We may not think to review what’s there.

That could be a missed opportunity. The 404 page is a place to help users navigate your website. They may look elsewhere if they can’t find what they need. And WordPress block themes open the door to customization. You can add features without touching code.

Let’s explore how the WordPress Site Editor can help you build a custom 404 page.

Start with a WordPress Block Theme

To start, you’ll need to install a copy of WordPress. You can use a local site or a web hosting account.

Next, it’s time to activate a block theme. However, a fresh install of WordPress will do this for you. The bundled default themes now work with the Site Editor.

We’ll use the Twenty Twenty-Three default theme for this demonstration. But you can use any block theme you like. The WordPress theme directory has several available for download.

Even better is that a basic 404 page doesn’t require plugins. WordPress includes enough blocks to build a functional page.

Edit Your 404 Template in the WordPress Site Editor

Now that we have a WordPress block theme, we can focus on our 404 page. Let’s start by navigating to Appearance > Editor inside the WordPress admin.

Next, we’ll click on the Templates link in the sidebar.

This screen displays all of the templates that come with your theme. The Twenty Twenty-Three default theme comes with a 404 template listed as Page: 404.

What if your theme doesn’t come with a 404 template? It’s possible to add a new theme template using the Site Editor. Just be sure to keep the WordPress template hierarchy in mind.

Assess the Template

Our 404 template is a bit sparse. It consists of a paragraph block and a search field. Both items are helpful. But we can do better, right?

A quality 404 page is there to guide users. Remember that they arrived here by mistake. The link they wanted to visit isn’t available.

What can we do to improve this page? We can think of a few additions that would make a positive impact.

Add Some Helpful WordPress Blocks

First, we’ll add a Page List block. This one provides a map of content for users to navigate. We love that the list shows parent and child relationships.

Maybe our visitor was looking for a blog post? Let’s add a Latest Posts block that shows six recent articles.

We can also include a button that links to the Blog page. Users can click it to gain instant access to our archive.

Let’s narrow things down a bit as well. Our blog has several categories and tags. We can use the Categories List and Tag Cloud blocks to add direct links to them. We’ll also use the Block Editor to create a multi-column layout.

What if our visitor still hasn’t found what they need? We’ll add a Cover block that encourages them to contact us.

It seems like we’ve covered all the bases. Our 404 page will serve as a launch point for users to find desired content.

Helping Users Find Their Way

We’ve taken a basic 404-page template and turned it into a hub. And we did so with native WordPress blocks. A few minutes was all it took to enhance the user experience.

There’s always room for more enhancements, though. You could add some third-party blocks to help users navigate. And a live search feature would improve the core WordPress function.

All told, the Site Editor simplified the template-building process. It didn’t require us to write code. And it offers plenty of layout options.

Don’t ignore your website’s 404 page. Improving it is worth the effort. And the WordPress Site Editor makes it easier than ever.

The post How to Build a 404 Page with the WordPress Site Editor appeared first on Speckyboy Design Magazine.

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.

However, the idea may seem overwhelming. Even technically-minded people might feel some trepidation. And non-developers might wonder if they have anything to offer.

I’ve had reservations about contributing. I know how to write code. But I’m not an expert. Plus, I was skeptical of what I could add to WordPress. There are a plethora of brilliant people already contributing.

Despite my uncertainty, I volunteered for Contributor Day at WordCamp US 2023. I figured it would be a good starting point. Besides, it’s only a day. Any disasters would be temporary!

Here are some thoughts and observations on what it’s like to participate. Is WordPress Contributor Day for you? Keep reading to find out.

There Are Myriad Ways to Contribute

There’s a perception that developers are the main contributors to WordPress. And sure, the project could use expert programmers. But coding is only part of the story.

As of this writing, there are 22 different contribution teams. Several have nothing to do with PHP, JavaScript, or CSS.

The Photos team is a prime example. Members are responsible for, among other things, moderating submissions to the WordPress Photo Directory.

Or you might help fellow WordPress users via the Support team. It includes answering questions on the project’s support forums. A working knowledge of WordPress will help. But you don’t have to know anything about code to pitch in.

There are also opportunities to help with marketing and community wrangling. These are great options if you’re a people person.

And we’re just scratching the surface. Your skills may translate to contributing more than you think.

Team Leaders Are There to Help You

I spent Contributor Day working with the Support and Documentation teams. I figured these teams were a good fit, given my background.

But there were challenges. Part of my task was to update the block editor documentation. Some articles were outdated and needed to be refreshed.

It sounds straightforward, right? Not quite. There are processes to follow that were foreign to me. I spent a few minutes staring blankly at my screen.

Thankfully there were some terrific team leaders on hand. In my case, Milana Cap was incredibly kind and patient. She walked me through each step and was always happy to answer questions. Oh, I had a lot of questions.

The point is that you’re not flying blind. Experienced team members are there to guide you. Therefore, it’s OK if you don’t know everything. No one expects you to be perfect.

For my part, progress was slow. I submitted a handful of edits to an article. Were they good enough to be published? Time will tell!

You’ll Feel a Sense of Community

Contributor Days are held at WordCamps worldwide. Therefore, attendance can vary based on the size of the event. In the case of WordCamp US, several hundred people were there.

There was a real sense of community among the attendees. Even a grumpy introvert like myself couldn’t help but notice.

I spoke with people I knew from previous WordCamps. But I also met contributors from far and wide. And many were first-time participants.

And the biggest surprise was that I wasn’t the only neophyte. The Documentation team table I sat at had several newbies. We all faced similar challenges in getting up to speed.

That was comforting. One of my biggest fears was being behind the curve. I didn’t want to slow everyone else down.

Refreshingly, the new contributor orientation said to expect things to move slowly. That statement did wonders for my stress levels. From there, I was able to relax and learn.

https://twitter.com/WordCampUS/status/1694816958791766190

Other Things Worth Noting

I couldn’t be everywhere at once. However, I did make a few general observations about WordPress Contributor Day. I hope that they help you get a sense of the overall experience.

There Are No Sales Pitches

I was grateful that Contributor Day didn’t turn into a sales pitch. You know, the kind where you’re prodded into making a long-term commitment.

My experience was nothing like that. Attendees were free to move from team to team. And the teams I worked with were all about helping and having fun.

I felt no pressure to do anything I wasn’t comfortable with. That’s a rarity in the world we live in.

There Are Some Very Dedicated Contributors

How has WordPress thrived for over 20 years? Its many contributors are a big reason why.

I witnessed some incredibly passionate people at their best. They knew how to get things done. Yet they were still welcoming of newcomers.

Some contributors are paid to be there. But I didn’t notice anyone treating their work as just another job. I saw enthusiasm everywhere I went.

WordPress Contributor Day Is Worth Your Time

If you’re attending a WordCamp that includes a Contributor Day, consider giving it a try. There are learning opportunities everywhere. Not to mention the chance to meet some great people.

I found the experience to be a positive one. And I gained a different perspective on how contribution works.

It takes a lot of coordination and dedication to keep WordPress going strong. There are a lot of unsung heroes who help make it happen.

Most importantly, know that your skills are valued. There’s a place for you to contribute – regardless of your expertise.

This was my first WordPress Contributor Day. But it won’t be my last.

The post What It’s Like to Participate in a WordPress Contributor Day appeared first on Speckyboy Design Magazine.

That’s where side projects come in handy. They provide the perfect environment for trying new things. There’s little risk and plenty of creative freedom.

And there’s no better playground than WordPress. The content management system (CMS) is infinitely extensible. It’s also well-documented and easy to customize. Best of all, it will help get your project off to a quick start.

With that in mind, here are five ideas for WordPress side projects. Each will help you level up your design and development game. Here we go!

Build a WordPress Block Theme

Compared to their classic counterparts, block themes are a different animal. They have a unique structure. And they aren’t as dependent on PHP.

They also haven’t been widely adopted yet. However, the WordPress Site Editor is constantly improving. Thus, it’s only a matter of time before block themes have a breakthrough.

If you haven’t paid much attention to block themes, now is a great time to start. Building a basic theme will allow you to see their inner workings. And you can get your feet wet with advanced features like theme.json and global style variations.

What sort of theme should you build? Think about how a block theme could benefit a typical client. Keep their needs in mind and add features to suit them. You may be able to use it as a starting point for future projects.

Resources

• A Deep Introduction to WordPress Block Themes by Ganesh Dahal
• Create Block Theme plugin by WordPress.org
• Creating WordPress block themes by Carolina Nymark
• Intro to the Site Editor and Template Editor by Wes Theron
• WordPress Theme Handbook: Block Themes by WordPress.org

Create a WordPress Plugin

Don’t let the title scare you. Creating a WordPress plugin doesn’t have to be overly complex. Much depends on the plugin’s purpose.

You might be thinking about successful products like WooCommerce or Gravity Forms. They have a lot of code underneath the hood. And they have teams of developers maintaining them. You don’t have to go that far.

There is an easier path to getting started with plugin development. For example, try a small custom plugin that has niche functionality. One that may only be relevant to a specific website. It might consist of just a few lines of code.

And you may already have some foundational knowledge. Are you familiar with adding code snippets to your theme’s functions.php file? If so, the jump to a custom plugin isn’t very difficult. The same code can be copied to a plugin with a few adjustments.

Plugin development is a great way to sharpen your PHP skills. Plus, it’s a better approach than using theme-specific code. This experience will serve you well on future projects.

Resources

• Plugin Basics by WordPress.org
• WordPress plugin boilerplate generator by Tom McFarlin & Devin Vinson
• Writing a WordPress Plugin From Scratch: A Step-by-Step Tutorial by Fred Meyer

Optimize a Website for Peak Performance

Everyone wants a fast website. But it’s not always easy to accomplish.

That’s particularly true when using WordPress. Themes, plugins, and third-party resources can bring your site to a crawl. And web hosting also plays a key role in load times.

Install a copy of WordPress on a server and experiment. Add lots of content and images. Try using different site configurations. See how switching themes impacts your site. Add various plugins that you use in your client projects.

This is also a great time to brush up on how caching works. There are several types to explore, including server and plugin-based options.

From there, use tools like Google Page Speed or a plugin like Query Monitor to gauge performance. This way, you can determine the impact of each item.

You’ll learn some valuable lessons along the way. And it may lead to a change in how you approach building a website.

Resources

• 6 WordPress Plugins to Optimize & Speed Up Your Website by Eric Karkovack
• How to Speed Up Your WordPress Site by Kinsta
• Improving Site Performance: An overview by Hari Shanker

Build a Custom Block

The Block Editor is rapidly evolving. New features are regularly added, and bugs are being squashed. The user experience (UX) has improved. As such, more users are choosing it over the Classic Editor.

And the ability to build custom blocks is powerful. Developers can bring a variety of features to their projects. Adding custom content, design, and functionality are among the possibilities here.

Blocks also offer portability. They can be used throughout your website. And you can package them into a plugin to use on multiple projects.

Plus, there are multiple ways to build custom WordPress blocks. Native blocks are built with React. However, there are alternatives available.

Plugins like Advanced Custom Fields Pro and Genesis Custom Blocks can also be used. They allow developers to create custom blocks via PHP. They’re efficient and make custom blocks accessible to more people.

Building custom blocks can be extremely useful. And it’s a great way to boost your revenue, as well.

Resources

• ACF Blocks by Advanced Custom Fields
• Create Block NPM Package by WordPress
• Getting Started With WordPress Block Development by Arjun Singh
• Introduction to Block Development: Build your first custom block by Learn WordPress

Integrate Third-Party Apps and Services

WordPress and its plugin ecosystem are very capable. But there are also times when you’ll need to integrate with third-party tools. They play an important role in areas like marketing and eCommerce.

There are a wide range of use cases. For instance, you might want to build a headless website using Gatsby or another static site generator. You can create content within WordPress while reaping the performance benefits of static HTML.

Automation is growing in popularity as well. And there are so many ways to integrate it into your workflow. A new form entry on your WordPress site could trigger, say, adding a new contact to your mailing list.

But that’s just the tip of the iceberg. There are also ways to integrate with payment gateways, customer relationship management (CRM) tools, and multi-channel eCommerce providers.

There may be a cost involved with some integrations. However, there are several free options to choose from. Find a few that are relevant to your business and get to work!

Resources

• AutomatorWP Plugin
• How to Incorporate External APIs in Your WordPress Theme or Plugin by Karen Pogosyan
• Sourcing from WordPress by Gatsby
• Uncanny Automator Plugin
• Zapier WordPress Integrations

Improve Your WordPress Skills

WordPress is a rapidly changing CMS. Keeping up with new developments is a key to professional growth. This is particularly so when it comes to blocks. They’re the present and future of the software.

Try to integrate one or more of the above items into a side project. You’ll gain a better understanding of how WordPress works.

Even better is that you won’t have to deal with the pressures of client work. And you can decide whether to release your project to the public. It might be a nice way to contribute to the community. But there’s also value in spinning up a local install and experimenting.

Either way, the skills you learn will serve you well into the future. So, take the first steps toward learning and see where it takes you!

The post 5 WordPress Side Projects To Help You Learn & Grow appeared first on Speckyboy Design Magazine.

Each website within that network can have its own users, themes, and plugins. As a super admin, you have a wide range of control over what is and isn’t allowed for those sites. For example, you can set things up so that sites can only choose from a limited selection of pre-installed themes or plugins that you deem acceptable.

That makes multisite perfect for grouping together any number of sites within an organization. Large companies, educational institutions, or like-minded communities can leverage this tool to bring several related factions under one big umbrella.

Naturally, the WordPress developer community has been on board with multisite for several years. As a result, there is a large selection of handy multisite-specific and compatible plugins to add all kinds of different functionality. Today, we’ll introduce you to some selections that we think are among the most essential.

Multisite Enhancements

Multisite Enhancements offers several helpful features for administrators. For starters, it will show you which sites are using a particular plugin – which can be incredibly difficult to discern on large networks.

In addition, it will serve up each site’s ID, current memory usage, and whether or not a site is using SSL. There are plenty of little tweaks that make for more efficient network management.

Broadcast

While it doesn’t have a large userbase, Broadcast is one of those plugins that offers something really useful: The ability to share content across multiple sites on the same network.

This is perfect, say, for a retail store that has a site for each one of its physical locations. Plus, there are a ton of commercial add-ons that offer compatibility with popular plugins, along with other desirable functionality.

WP Security Audit Log

WP Security Audit Log works for all sites but could be of particular interest to multisite admins. The plugin provides an easy way to keep track of all changes made to sites throughout your network.

What’s more, super admins can delegate access to event logs and settings across other user roles – or block everyone else out. Either way, you’ll stay on top of who’s doing what.

User Switching

Attempting to troubleshoot user-related issues on a busy multisite network is difficult.

With User Switching, admins and super admins can easily switch between any user account. This allows you to see things as individual users do and will help track down problems more quickly.

Disable Comments

Not everyone needs comments. And trying to manage them on a large network of sites is a bit like herding cats. Disable Comments lets you shut down comments (even the mere mention of them) on both the front and back end of your install. Alternately, you can block only specific post types if you wish.

NS Cloner

If you need to quickly replicate an existing site in your network, NS Cloner will do the trick. The plugin will copy virtually everything from the target site, including theme settings, plugin configurations and content. In the right situation, this could be a huge timesaver.

Inactive Logout

Inactive Logout can be very useful if your network has many users who need to access the back end. Invariably, someone is always leaving themselves logged in for hours at a time – even when they’re not at their computer.

The plugin can be set to log out inactive users after a specific period of time, helping to mitigate an unnecessary security risk.

Classic Editor

Maybe the Classic Editor is far from a multisite specialist. But it does offer some key features for super admins. First, it offers the ability to turn off the block editor (a.k.a. Gutenberg) network-wide.

Alternately, you can leave things up to individual site admins. This option allows each site in the network to use the content editor they feel most comfortable with.

Multiple Possibilities

There are several real advantages to opting for a multisite network rather than using separate WordPress installs. The biggest may be that administration is much more efficient, as everything you need can be accessed from one place.

And with the added boost provided by the plugins above, you can tweak a network to match your workflow better.

The post 8 Essential Free Plugins for WordPress Multisite appeared first on Speckyboy Design Magazine.

High-end functionality is at our fingertips. We see it with content management systems (CMS), code frameworks, and other advancements. They have raised the bar on what we can achieve. And client expectations are higher than ever.

This evolution has brought a lot of positives. But it has also made website maintenance more difficult. It’s the price of using the “latest and great” technologies.

Here are five of the most painful maintenance-related issues that web designers face.

1. API Changes That Break Features

Many websites depend on third-party APIs. They enable us to connect with mapping services, email list managers, and social media networks.

Each API is different. They all have quirks. And some are prone to sudden changes.

Improvements are always welcome. But there are downsides, too. Sometimes a change requires us to refactor our implementations. Failure to do so can lead to a broken feature.

Look no further than Twitter to see the impact. The decision to put their API behind a paywall left a lot of users out in the cold. And continued changes have brought chaos to web designers.

It can be a pain to keep up with these changes – even for one website. But the situation is worse for those who manage multiple sites.

2. Dealing With Abandoned WordPress Plugins

A thriving plugin ecosystem is key for an open-source CMS. It provides users with helpful tools. And it’s a business opportunity for developers.

But there’s no guarantee of quality or longevity. Anyone can publish a plugin. That means we live with a lot of uncertainty. Not all plugins evolve along with their platform.

This can lead to headaches for web designers. If a plugin we’ve chosen is buggy, no longer maintained by its author, or both, a replacement must be found.

The more complex the plugin, the more painful it is to replace. It’s about more than finding a new plugin, however. Any customizations made around the previous one will have to be refactored.

The whole process could become expensive and time-consuming.

3. Web Hosting Nightmares

We depend so much on web hosts. How much? Think of it this way: even a well-built website can’t overcome substandard hosting.

Hosting providers sometimes fall flat. The situation can get out of hand in a hurry. Frequent outages, security holes, or lackluster support make our jobs harder. Web designers are often caught in the middle of these situations.

We’re the ones who are typically the go-between for our client and the hosting provider. It could mean lots of time waiting for answers in a chat or (even worse) on the phone.

Meanwhile, the website in question may or may not be available. Not fun at all.

4. Dealing with Old Websites

Old projects are like a recurring nightmare. And veteran web designers might have dozens of them. Some clients are on a budget or just don’t see the need for a redesign.

An older site isn’t always problematic. But the way it was built could be. Designers and developers learn through experience. The techniques we used five years ago are likely miles away from our current approach.

Thus, maintenance can mean facing previous mistakes. It can make us kick ourselves for not predicting the future.

There is a bright side, however. Digging through old code can make you appreciate how far you’ve come.

5. The Mysteries of an Inherited Site

An inherited website is full of surprises. You didn’t build it. Therefore, you never know what’s lurking in the shadows.

Sometimes you can identify problems right away. But even a website that looks fine can cause trouble. Issues aren’t always visible to the naked eye.

But incompatibilities, malware, and buggy code can rear their heads at any time. You may not find out about them until it’s too late.

It takes a bit of bravery and a lot of patience to work on these projects. That’s why it’s important to charge accordingly. You don’t want to lose money on the venture. Losing your sanity is bad enough.

How Pain Can Lead to Growth

The above “pains” all have a few things in common. First, they are simply a part of our job. Websites often work with third-party apps and services. And no website is immune to hosting foibles.

In addition, each of these items provides an opportunity for web designers to learn and grow. The experiences we have can be helpful. We’ll better understand how to deal with similar issues in the future.

That’s a good thing. The web’s complexities aren’t going away anytime soon.

The post The 5 Biggest Pains in Website Maintenance appeared first on Speckyboy Design Magazine.

WordPress is the clear market leader. It’s my go-to app for building websites. But I have also worked with other systems. My experiences have been uneven.

I don’t have in-depth knowledge of every app. But I can identify a good system. They offer ease of use and adhere to best practices. These systems have improved significantly. Still, they each have drawbacks. With that in mind, here are five things that no CMS should do.

Generate Code That Doesn’t Follow Best Practices

The web has a lot of standards and best practices. Markup must be structured semantically. Content needs to be accessible. And CSS should be used for styling elements such as typography.

Yet I still see content editors that are frozen in time. For example, there’s a propriety CMS I’ve worked with. Its content editor still utilizes tables for multi-column layouts. And, incredibly, it styles text using HTML font tags. Um, 1995 called. They want their markup back!

There’s a difference between slight deviations from standards and an outright disregard for them. That any app would use such outdated techniques is bewildering. It’s also irresponsible. The worst part? Service providers expect people to pay for their antiquated products.

Content creators rely on their CMS to employ best practices. We need an app to convert text and images into clean, accessible code. It doesn’t have to be perfect. But it should never hinder anyone’s ability to consume it.

Allow for Unregulated Clutter in the Dashboard

Working at a cluttered desk is frustrating. It’s hard to be creative – or even concentrate – with various junk lying around. A CMS dashboard is much the same.

Dashboards should be minimal and easily customized. The WordPress Dashboard starts off this way. But it quickly becomes a mess as you install more themes and plugins.

Dashboard widgets can be turned off. But the many nagging notification messages shown throughout the back end aren’t easy to jettison.

WordPress is an open-source system. Thus, it doesn’t have much control over how notifications are displayed. There have been efforts to make notifications more user-friendly, though.

This is an area where proprietary systems have an advantage. Especially those that don’t allow third-party plugins. They have complete control over the UI.

There’s also a need to distinguish between system-related notices and cheesy upsells. Understandably, software developers need to make money. But being bombarded with ads crosses a line. As does being forced to dismiss notifications repeatedly. There should be strict guidelines regarding this type of behavior.

Restrict Content Portability

Your website may have been built using a particular CMS. But it may not stay that way. You might eventually outgrow the platform or want to try something new. Switching platforms isn’t easy.

Proprietary systems are often the worst offenders. Content and design can’t be exported. In some instances, you can’t even export a copy of your site for staging purposes.

Thus, you’re left searching for a third-party tool to do the job. Otherwise, you might have to copy and paste each page.

It’s reasonable that some functionality may not be exported. Shopping carts are a prime example. But your content should be portable. Is that too much to ask?

Prioritize Features Instead of Stability

All software should evolve. Bugs are squashed, security holes are filled, and new features are added. A CMS is no exception.

However, it shouldn’t come at the cost of stability. This is vital for website owners. Websites must continue to work – regardless of how software changes.

Big changes can throw a wrench into the works. If all the “what-ifs” are not accounted for, a change can have dire consequences. Specific features, or even an entire website, could break after a change is implemented.

New features are still important. They help attract new users and make life easier for existing ones. But they need to be carefully implemented to minimize any negative impacts.

An app with a reputation for breaking websites won’t survive.

Fail to Communicate with Users

Communication is as important as code. A system may have compelling features. But users will need to know about them to take advantage.

Likewise, CMS developers need to know what their users want and need. That information is key for prioritizing features and bug fixes.

But communication is a big job. It encompasses documentation, user support, and building community. This requires a lot of effort.

Even large companies struggle with communication. For smaller providers, it may stretch finite human resources to the max.

Still, it’s worth the effort. A failure to keep an open dialogue with users will erode relationships. And it may cause a mass exodus from the platform.

A CMS Must Focus on Users

A CMS will ultimately be judged on whether it fulfills the needs of its users. None are perfect in this area. But some are far ahead of their competitors.

The best systems allow us to create content in an accessible manner. They develop features that maintain stability and provide backward compatibility. In addition, these systems respect a user’s right to move their content and facilitate portability.

Above all, a good CMS will keep an open line of communication with users. This dialogue will benefit everyone. It helps to ensure a bright and productive future.

And what about apps that fail in these areas? They’ll most likely cease to exist over the long term.

It’s something to consider when choosing a CMS for your next project.

The post Why Modern CMS Shouldn’t Do Everything appeared first on Speckyboy Design Magazine.

One recent debate involves the WordPress Site Editor. The feature allows us to design and build an entire website within the browser.

Some find this to be a great leap forward. But others are concerned that it gives site owners too much control. They worry that there aren’t enough protections to keep a client from accidentally breaking the layout. I believe that there are valid points on each side.

But this discussion also got me thinking about how we train clients. Is the Site Editor (or any tool, for that matter) relevant to them? Do they need to know every aspect of how their website works? And where do we draw the line about what’s important?

Let’s explore the challenges in educating clients about their websites. Along the way, I’ll share my thoughts on why knowing it all isn’t all that great.

The Risk of Overwhelming Your Clients

Modern websites are becoming more complex. And it’s not just the high-end enterprise variety. Even an old-school “brochure” site can have several moving parts.

We can thank the proliferation of content management systems (CMS) for that. These apps allow for greater flexibility. But that also means more code. Themes, plugins, and custom creations each add another layer to the mix.

This makes educating clients more challenging. Limited time and resources may force us to leave out certain items. Thus, we can’t easily provide a complete explanation of every feature.

Perhaps this sounds like bad news. But that’s not necessarily the case. By focusing on the essentials, we’re helping clients understand what’s most relevant.

Take automobiles, for example. Cars come with all manner of complex systems. But do we know how each one works? To do so, we might have to spend weeks (or months) in a specialized course. And our heads would likely be swimming in superfluous facts and figures.

If the goal is to empower clients to perform specific tasks, it’s OK to skip past the things that don’t impact them.

What’s Important? Look at a Client’s Workflow

The areas of focus for client training aren’t always obvious. Some tasks, like logging in, are universal. But there will also be unique aspects as well.

Much depends on what your client wants to accomplish. Maybe they will be publishing articles or regularly adding events to a calendar. They might focus on processing eCommerce orders.

This information is vital. It helps guide us in how to effectively implement features. And it also gives us an idea of a client’s workflow. From there, we can design a training program that fits their needs.

It starts with the initial conversations you have with them. As you learn the project’s details, you’ll be able to ask questions about how they plan to interact with their site.

In addition, you’ll also have an idea of what can safely be left out. For instance, consider a client who won’t need to touch their home page layout. There’s no reason to spend precious time demonstrating a feature they won’t use.

Are Some Features Better Left Hidden?

Hiding or choosing to ignore certain features can sound suspicious. Some may see it as trickery. But that’s not the goal here.

To expand on that idea, let’s revisit the WordPress Site Editor. It’s a design tool intended to make for easier template changes. Thus, it’s not likely to be part of a client’s day-to-day workflow.

You might still mention that the feature exists. And you could even give a quick summary of its purpose. In that case, a friendly warning about the potential dangers should also be offered. But a deep dive into how it works is probably not necessary.

In my experience, clients tend to be focused on their to-do lists. Website tasks are often only a part of their responsibilities. Therefore, the more efficient we can be in training, the better it is for all parties.

And this doesn’t preclude us from exploring features later. As a client evolves, there could be an opportunity to dig into something you previously ignored. But initially, the features covered should be based on need.

Clients Don’t Need To Know It All

When you think about it, most of us buy products without understanding their every facet. Cars, mobile devices, and all manner of appliances come to mind.

The ability to operate these items is what matters. Do we need to know exactly how our microwave oven heats a meal? It may make for great party conversation. However, knowing how to use it is probably more important.

Websites are no different. We build them to suit our client’s needs. And we help them learn what they need to know to achieve their goals.

The most relevant information, therefore, is the best use of everyone’s time. Everything else is secondary.

The post Do Clients Need To Know How Their Website Works? appeared first on Speckyboy Design Magazine.

But much of the user and developer experiences are based on our choices. Do we go with a battle-tested classic theme or opt for a newfangled block theme? Do we embrace the Block Editor or stick with the trusty Classic flavor?

These are defining decisions. They chart a path for how we work with the content management system (CMS). And they influence everything from how we build a website to how content is created.

You might even say they’re distinctly different experiences. Here’s why I hope it stays that way.

Flexibility To Fit Any Type of Project

Flexibility has long been a strength of WordPress. Its open-source code and extensibility make for nearly endless customization.

Developers can tweak the front and back ends to match project needs. If the default functionality isn’t enough, you can build your own. And we can’t forget about the massive theme and plugin ecosystem.

This means that building virtually any type of website is possible. Single-page portfolios, enterprise-level multisite installations, and everything in between are within reach.

Still, the advent of the Block Editor (WordPress 5.0) and Site Editor (WordPress 5.9) raised a big question. How would these additions impact flexibility?

If anything, they add more avenues for customization. The Block Editor will work with any type of theme. And in some cases, it may eliminate the need for page builder plugins or hard-coded custom templates.

The Site Editor, meanwhile, allows us to build an entire website with blocks. Block themes can serve as solid no-code solutions. They may be the perfect fit for specific types of sites.

And if that weren’t enough, you can also combine the best of classic and block themes. Features like block template parts let theme developers create their preferred mix of tools.

Yes, WordPress is still flexible. Although one could make the case that choosing the right path may be harder than ever.

Concerns About the Present & Future

It’s great to have choices. But there are a few concerns with having two distinct ways of building with WordPress. Perhaps the biggest is how it impacts the future.

If you choose a classic theme, will it still be viable within a couple of years? Or will these themes have been phased out by then? That could conceivably leave you with a mess when it’s time for a redesign.

On the other hand, some rightly wonder if block themes are capable enough. The Site Editor is still relatively young. And blocks can’t account for every possible use case. Plus, block themes continue to make up a relatively small segment of the market.

As such, some will prefer the tried-and-true method of writing PHP and CSS. All the talk these days is about blocks. But it may be that classic themes are still the best fit for highly customized websites.

Taken together, it seems like developers are caught between worlds. After all, no one wants to go in the wrong direction. But is there a bad choice here?

You Can Still Build to Suit With WordPress

There has been some compelling debate about the current state of WordPress development.

Chris Coyier wrote a fantastic piece about the uneasy transition to blocks-for-everything. He wondered if perhaps PHP-based themes have met their demise. Ben Word, meanwhile, spoke of how you can use PHP to get the best of both worlds.

Look around social media, and I’m sure you’ll find others who align with one stance or the other. For my part, I can identify with both points of view.

Each approach has its strengths. With that, maybe the decision should come down to what’s best for your project.

As a developer, there is great power in being able to build according to need. Since both classic and block themes are supported, there’s no reason we can’t use what works best for us.

If you feel like PHP-based themes aren’t where it’s at, why shouldn’t you use a block theme? And if block themes don’t provide enough flexibility, classic themes make perfect sense.

This is what separates WordPress from other platforms. You aren’t stuck with a single way to do things. Sometimes this can create extra layers of complexity. But it’s arguably better than being limited in how or what you can build.

The Beauty of More Options & Possibilities

Maybe WordPress isn’t always the best option for a given project. For instance, it may be overkill for a simple one-page site with no dynamic content. Thankfully, each of us can decide if that’s the case.

But I love that I can use WordPress to build that type of site. Or any other type of website. And I can choose a path to building that aligns with my needs.

Sure, there are drawbacks. And there are also areas of the CMS that are languishing. But by and large, WordPress works as advertised.

I understand that some may see the existence of block and classic themes as an unnecessary complication. But I choose to look at it as having two legitimate options to build a website. And I hope that continues to be the case.

The post WordPress Offers Two Very Different Paths: That’s a Good Thing appeared first on Speckyboy Design Magazine.