Could you imagine a traditional line of work that relies so heavily on no-cost tools? The concept would likely be unfathomable to anyone from an accountant to a zoologist. Yet it’s something web designers have embraced and, to some extent – expect.

Whether it’s building a website with WordPress, crafting a layout with Bootstrap, or storing data via MySQL, it’s an everyday occurrence. And these tools are just a few examples. We have a multitude of free options – each helping us do our job more effectively.

This has been the case for years. And things have gone remarkably smoothly. Some tools come and go, but the underlying philosophy of open-source software has endured. But that seems to be changing.

Lately, there’s been talk of so-called “free riders” who benefit from such projects without necessarily giving back.

That begs the question of what our responsibility is when using free, open-source software for commercial purposes. What, if anything, do we owe?

What follows isn’t a definitive answer. Instead, it’s a collection of thoughts on how we might reach a better understanding of the issue, along with some simple actions we can take.

Take a Freelance Free Ride

Granted, the debate over free riders has largely been about corporate users. The everyday freelancer hasn’t been the primary subject of debate.

But the lines can get blurry. Consider that anyone with the desire and skill can extend open-source software. As such, they can also financially benefit from their efforts.

This has been encouraged within the WordPress community. Many a theme and plugin has found success through commercial or freemium offerings. Once a certain status has been attained, does that developer become part of the conversation?

Likewise, one could build a custom plugin that’s specific to a client project. With that, we’re not only making money from building a website. We’re also able to charge more for a custom solution designed around the core software.

The ability of a freelancer to repeat this process could lead to significant growth. In the eye of some observers, a threshold might be crossed as revenue grows.

The Uncomfortable Truth about Free and Open-Source Software

It seems like there’s so much gray area when it comes to giving back to some open-source projects. There are arbitrary standards about who should contribute and how they should do so. Etiquette is often insinuated but not clearly defined.

Plus, the mere fact that an app or framework is publicly released ensures that users will take advantage to various degrees. Some will use them in ways the author neither expected nor intended. Others will discover methods to profit from it.

This may make project stakeholders squeamish. Yet it’s also the reality of our world. Technology can be used for good, bad, and everything in between. It’s part of the risk you take when allowing anyone to access your creation.

If everyone from a solo entrepreneur to a large hosting company can freely use an app, it shouldn’t be a surprise that some will refuse to play nicely. In a competitive market, people are looking for an edge. Ethically speaking, sometimes their actions go against the grain.

What Should We Do?

Defining what counts as a contribution is open to interpretation. There are both official and unofficial ways to do so. With that, it’s up to each of us to think about what we want to give back to the projects we benefit from – or if we want to give back at all.

If your skills and schedule allow for an official role, then becoming a volunteer is a wonderful way to give thanks. Regardless of the software, there is almost always a need for human resources. Even a few hours a month can make a positive impact.

Not everyone has the time, resources, or expertise to dedicate to official contribution channels. However, unofficial efforts are also worthwhile.

If you fit into this category, there are still some valuable ways to pay it forward:

Respect Software Licensing

This kind of contribution doesn’t require any grand gestures or public declarations. By using an app, you’re agreeing to the terms of its license. From there, it’s up to you to follow through.

For example, there may be rules about redistribution or using companion software that follows a set of standards. Staying within those boundaries is good practice and a show of respect for those who put their precious time into the project.

This is the least we can do to help a project fulfill its promise.

Share Your Knowledge and Experience

If you’ve had experience with an app, take some time to share it with others. Pass along tips, tutorials, or opinions through social media or a blog. Tell your clients how their organization can benefit from the software.

This raises awareness, which is the lifeblood of many open-source offerings. It’s particularly important for small projects that don’t have widespread name recognition.

As an aside, it’s also worth letting the people behind the project know about your efforts. They’ll likely appreciate the recognition.

Support the Ecosystem

A healthy ecosystem is often part of a thriving open-source project. Think of WordPress as a prime example. If there were no third-party themes and plugins available, the core software would become less appealing. Extensibility means a great deal.

You can support the ecosystem by using and promoting your favorite items. Purchase commercial versions if they fit your needs. And you can contribute your own creations as well.

Recognize Other Contributors

A lot of work goes into making great tools. Countless hours spent in design, development, support, and other areas are required. But it doesn’t have to be a thankless job.

Taking the time to say “thank you” to contributors goes a long way. So often, we only see the negatives in the public sphere. Thus, a quick note of encouragement can make all the difference.

Again, it doesn’t have to be anything grand. Whether it’s a shout-out on Twitter or an email, make a point of spreading positivity. It’s something everyone needs to hear now and again.

Think about the Software We Use

In this age of powerful open-source software and nearly-instantaneous downloads, it’s easy to take what we have for granted. And no one can blame you if your focus tends to be on the task at hand. That’s a natural part of running a business or having a job.

At the same time, it’s important to take a step back and think about the software we use. Where does it come from? Who built it? How have their efforts impacted us?

Then consider what you’re able to give back. Perhaps not all contributions are equal. But they all matter nonetheless.

The post The Responsibilities of Making Money with Open Source Software appeared first on Speckyboy Design Magazine.

That’s why web designers need to evolve. It’s a key factor in long-term success. But making the transition to the “next big thing” isn’t easy.

There are challenges involved. For one, changing your workflow is disruptive. Not to mention the learning curve that comes with something new.

Motivation, or a lack thereof, can also play a role. For example, we may think that learning React would be beneficial. We may even put it on our to-do list. But what motivates us to start the process?

To put it mildly – it’s a complicated situation. But we’re here to help! Let’s look at a few motivating factors that can help push you in the right direction.

You’re Missing Out on Projects

Just as web design changes, so do project requirements. Clients take notice of both design and functionality trends. Thus, they have a higher level of expectation.

Consider the definition of a “basic” website. In the late 1990s or early 2000s, it was likely a static site. There was no content management component. And a contact form may have served as the most complex functionality included.

That’s no longer the case. Clients who want to make site edits will require a content management system (CMS) like WordPress. They may also want to accept payments and distribute members-only content.

Sure, the market for static HTML is still there – and use cases abound. But even those sites are built differently these days.

Keeping up with best practices should serve as a motivator. Otherwise, you risk missing out on interesting (and potentially lucrative) projects.

Your Workflow Is Cumbersome for a Colleague

Even solo freelancers collaborate with others. Therefore, the ability to share work is critical for success. If things don’t go smoothly, it could impact the final product.

How we work is important. For instance, you might have a process for managing tasks. But what if it’s not easily shared with others? That might leave your collaborators out of the loop.

The beauty of working alone is that you can do things your way. However, sharing a role with others changes the game. You may need to adjust to better facilitate working together.

In practice, it could mean using a project management platform. This would allow stakeholders to get on the same page. Efficiency will increase. And the outcome will likely be better.

That’s why it’s worth asking yourself if a particular workflow still makes sense. It’s easy to fall into the trap of continuing to do unproductive things. A reset here could be just what you need.

The Tools You Use Are Obsolete

Not all tools change with the times. And we’ll often use a tool simply because it is the best available option.

The right tool can empower us. But obsolete tools can hold us back. They can make it more difficult to follow best practices. Plus, they may also make us less efficient.

On the other hand, there’s also the benefit of comfort. And it’s often easier to stick with what we know – even if it’s no longer the most modern solution.

One example: using Adobe Photoshop to create website mockups. It still works well enough for this purpose. And the familiar UI makes it a favorite among veteran designers.

But modern prototyping has changed significantly. They account for multiple screen sizes and offer more web-focused features. Why, even Adobe has moved on with their XD app.

Age alone doesn’t mean you have to abandon a tool. But it doesn’t hurt to look around and try something new. Perhaps you’ll find a better fit for your needs.

You’re Stuck in a Creative Rut

Creativity can be a fragile thing. Some days we have it. Sometimes it disappears into the atmosphere. And although workflow isn’t the only cause for a creative rut, it can contribute to one.

This may also be the most difficult issue to diagnose. We can blame our daily routine for that. Many of us like routines because we don’t have to think about them. Therefore, we might not recognize habits that take away our creative edge.

So, how do you break away from things that hamper us? It starts with a little self-analysis.

Think about the times when you’re feeling most creative. What factors are involved? For instance, you might find that you’re “in the zone” at a certain time of day. Or maybe when you turn off the notifications on your phone. Or when you stick to one task at a time. The possibilities are endless.

The idea is to find what fuels your creativity. From there, you can adjust your workflow to match.

Bring Your Workflow Up To Speed

None of us has a perfect workflow. And it’s unlikely that any two web designers will do things in the same way. That’s a feature – not a bug.

Therefore, taking a closer look at how we work is healthy. Are the tools and technologies we use helping us reach our full potential? Or is there something getting in the way of success?

We don’t have to force a change. But there are so many options and life hacks out there. And we get to choose the ones that work best for us.

The answers will be different for each of us. That’s part of what makes web design unique.

The post Why You Should Consider Updating Your Web Design Workflow appeared first on Speckyboy Design Magazine.

The most common thread here is flexibility. WordPress is capable of powering virtually any type of website one imagines. Everything from a simple blog to an eCommerce shop and beyond are possible.

But, as with all technology, there is a certain level of responsibility that comes with using WordPress. It’s something to consider when choosing how you want to build a website. Because, while the CMS is capable of great things, there are scenarios where it may not be the right option.

Let’s take a closer look at some times when it may be wise to steer clear of WordPress – or any CMS, for that matter.

When There’s No One to Maintain the Website

As a designer who has inherited a number of WordPress websites, I’ve seen it before: a website was built several years ago and hasn’t been touched since. A client knows their website needs some work, but doesn’t realize the depth of the underlying problems.

There can be a myriad of issues involved. For one, severely outdated versions of WordPress core, themes and plugins. This is a potential nightmare in terms of security. And it’s not uncommon to find that a site in this situation has been compromised.

Upgrading the software isn’t always so straightforward, either. Some items may have been abandoned, or have to be updated a version at a time to avoid complications.

Unfortunately for the client, there could be a significant cost in cleaning this up. All because their website wasn’t properly maintained in the first place.

The trouble is, most website owners aren’t going to know about the importance of WordPress maintenance unless a designer informs them. Too often, designers simply hand over the keys without a whole lot of instruction. But even when they do, clients may either ignore the advice or forget about it.

The truth is that WordPress does need to be regularly maintained. For the sake of both security and functionality, updates need to be applied in a timely manner.

Therefore, if an organization doesn’t have anyone (or are unwilling to pay someone) to maintain their website, it may be better off not utilizing WordPress. In these situations, a static HTML website or even a managed proprietary CMS could be more sustainable options.

And yes, WordPress can be auto-updated. However, it’s still important to have someone knowledgeable regularly checking in on the site. Otherwise, something could break and be left that way indefinitely.

Your Project Doesn’t Need Content Management Functionality

Having new and ever-changing content is a great way to keep users engaged. Yet not every organization is going to make that commitment. Sometimes there’s no budget for original content, other times there simply may not be enough time to create it.

Of course, one of the key selling points of WordPress is the ability to create and organize content with ease. Whether that’s building a slick page layout in the Gutenberg block editor or adding an ongoing archive of recipes, this is what a CMS is built for.

But what if your project doesn’t require any of this? The traditional “brochure-style” website is still alive and well. Their purpose is to supply users with the information they need and way to get in touch. Beyond that, there may not be much call for the kinds of functionality a CMS provides.

In this case, implementing WordPress may be overkill. First, there’s the potential for higher startup costs – especially if a custom-built theme is involved. Then there are also the aforementioned maintenance requirements.

If there’s not much content and it’s not likely to change, a CMS is completely optional.

You (or Your Client) Have No Desire to Learn the Inner Workings of a CMS

Over its many releases, WordPress has made big strides in usability. It has had a keen focus on newcomers. But for some users the dashboard still offers a lot of clutter.

Even a website that looks simple enough on the front end can be complex behind the scenes. Users have to know where different types of content reside. Beyond pages and posts, there could be any number of custom post types implemented. Then there are plugins like photo galleries, sliders and shopping carts to navigate.

For a non-designer to manage content effectively within WordPress, it often takes some training. In most cases, I’ve found clients to be very receptive to learning. But there are also a few that have very little desire to dig in.

These folks may benefit more from a system that is dead-simple and more limited in scope. One that offers front-end content editing by default and has few settings to tweak.

WordPress offers users the world. However, it’s important to remember that some people prefer to stay within their own backyard.

With a Great CMS Comes Great Responsibility

In some ways, I feel a bit silly in discussing reasons not to use WordPress. After all, it’s a tool I use almost exclusively.

But I also think it’s healthy to talk about the responsibilities that come along with using it. While the software is free of charge, it does require a few things from us:

• Regular maintenance;
• A willingness to learn how to use it;

That may not seem like an awful lot. But in reality, it is a bridge too far for some people. And there are also times when the functionality WordPress offers just isn’t necessary. In those cases, there’s nothing wrong with adopting the simplest solution.

The ability to meet these minimum user requirements is a key to whether or not WordPress is right for your project. If they can’t be met, then you might want to look elsewhere.

The post Scenarios Where WordPress May Not Be the Best Option appeared first on Speckyboy Design Magazine.

Being the top dog has plenty of benefits. WordPress enjoys an extensive plugin and theme ecosystem, a dedicated community, and a good bit of influence on the web as well. Try as they might, competitors can barely make a dent in what WordPress has going for it.

That doesn’t mean it’s all roses, however. As a market leader, WordPress faces a unique set of challenges. Some of it is due to the sheer number of users and use cases. But the fact that it’s a free, open-source application that relies on volunteers also plays a role.

Put these factors together, and it seems like WordPress holds a position unlike any we’ve seen on the web. To be all of these things while continually improving and pushing the web forward is a monumental task.

As such, let’s take a look at the biggest challenges facing WordPress (as I see them), along with how its size impacts the efforts to tackle them.

Moving Forward without Breaking Legacy Sites

When you think of the competition in the CMS space, there are both open-source and proprietary players. The proprietary apps have more control over how their product is used. In theory, this makes it easier for them to launch new features and drag users along with them.

WordPress has no such luxury. For instance, a Squarespace or Wix site is hosted on a single platform. WordPress sites can be hosted virtually anywhere. Therefore, it has to work in many different environments. This also impacts performance, with some potential tweaks being based on factors such as a server’s operating system and allotted resources.

And then there’s backward compatibility. There are undoubtedly WordPress websites still around from the 2000s and 2010s – with older themes and plugins in tow. Changes have to be developed and rolled out in a way that minimizes the potential for breakage.

While there have been proposals to do things like automatically convert uploaded JPG images to the smaller WebP format, there has been pushback from the community due in part to hosting variables. And even the advent of the Gutenberg block editor and Full Site Editing (FSE) have had to be rolled out in a way that respects existing sites.

Regardless of how useful one finds a particular feature, there is certainly a bigger hill for WordPress to climb compared to other CMS.

Prioritizing Features and Bug Fixes

Shiny new features tend to get all of the publicity. And in recent years, WordPress has focused on building new tools to make rich content creation and design easier. The goal is to help the CMS compete with DIY site builders and sport a more modern interface.

While that’s a noble cause, it’s also a massive undertaking that has come at a cost. Browse through the WordPress Trac system, and you’ll find a multitude of bugs and improvements waiting to be resolved – including some that have been there for years.

The heavy focus on the block editor and FSE has taken finite resources away from other areas of the software. The volunteer force of contributors is doing fantastic work, but they are stretched thin. So, despite a slick (and constantly improving) editing experience, other concerns are being left out of the party.

The result is that potential usability improvements and small bug fixes languish. Over time, these things build up and frustrate users.

You can see it in the reactions when WordPress suffered a drop in market share. Whether these issues ultimately were related to the small plunge, the news certainly got people talking about their pet peeves.

Achieving a balance here has been challenging. While WordPress must meet modern expectations, the smaller details can’t be ignored. More volunteers may help, but so would a greater focus on screens outside of the editor.

Trying to Be All Things to All People

Is WordPress a DIY site builder or a tool focused on custom development? That may depend on who you ask.

Traditionally, the CMS has catered to those looking for flexibility. The ability to build themes and plugins, use off-the-shelf products, or a combination of those solutions attracted droves of web designers to the platform.

This approach helped to propel WordPress to the top of the market. An entire economy was built around the concept of making the software what you want it to be.

At the same time, the project is moving towards a no-code future. And developers have had to adapt to building products that fit in with this methodology.

It seems as though we’re currently stuck between two worlds. Somehow, WordPress has to continue to maintain that do-anything flexibility without scaring away non-technical users.

It’s an awkward mix and makes for some difficult decisions. The big question is if it’s possible to keep these very different groups relatively satisfied – let alone happy.

The Growing Pains of Market Leadership

WordPress has reached a level of popularity that no other CMS can match. While not quite as ubiquitous as Windows on the desktop or Android on mobile, it has become the software of choice to power much of the web.

When you consider its humble beginnings as a blogging platform, the journey to market leadership is even more impressive. But now that its position has been established for several years, challenges must be met head-on.

How WordPress deals with these growing pains will have a lot to say about its future success. The software must become friendlier to new users without losing its street cred for customization. And innovations have to extend beyond just content and site editing.

Most of all, it has to pay attention to what’s happening within its ecosystem. This is what truly separates WordPress from all others. Therefore, finding new ways to engage and empower theme and plugin developers is crucial.

To some degree, all popular software faces challenges and comes to a crossroads at some point. And the bigger an app is, the more difficult the path forward.

The good news is that WordPress has made it this far. Here’s hoping it will evolve in a way that keeps it on top.

The post The Challenges of WordPress’ Massive Market Share appeared first on Speckyboy Design Magazine.

But while the technology is in place, a streamlined experience for clients isn’t guaranteed. Depending on what types of content they’ll need to add or edit, the process can become overly complex. The result could be anything from a broken layout to desperate calls (or emails) asking for help.

Therefore, web designers must carefully consider how we implement certain features. It’s one thing to build a UI that a seasoned developer can manage. Crafting something easy for a non-coder to work with is quite another.

The answer is in making things as simple and intuitive as possible. Here are a few things to keep in mind when setting your clients up for content management success.

Consider What Could Go Wrong

A little planning now can save a lot of pain in the future. Especially when it comes to the portions of a website that will be maintained by your client.

Much can change between the time a website launches and when a client needs to make a change. Needs may have evolved. And clients may not be aware of the limitations of what you’ve built.

That’s why it’s important to think ahead. Not only should you consider the expected usage of a feature, but also how it will react to the unexpected.

Think of an area that is comprised of text. What happens if your client decides to add an image to the mix? How will that impact the integrity of the layout? Will it continue to work across mobile and desktop devices?

While you might not be able to prepare for every scenario, you can build a great deal of resiliency into a site’s design. This will keep things looking good – even when a client goes rogue with content. Plus, your clients won’t have to face the trauma associated with a broken website.

Don’t Assume Clients Are Tech Savvy

In situations where you’re implementing a UI, simple is always better. And it’s crucial to remember your intended audience.

Sometimes, it’s difficult to place ourselves in the shoes of a user. Not everyone lives and breathes code or high-tech tools. Thus, don’t make assumptions as to how tech-savvy the person using your creation is. If anything, start from ground zero.

Language is a prime example. Use terminology that anyone can understand. Avoid buzzwords and complex explanations. Instead, opt for content that is short, succinct, and easy to read.

Visual indicators can also be of help. The use of icons, animations, and quick tutorial videos makes for a more intuitive onboarding experience. And they can also serve as a handy reference if a client isn’t sure of how to perform a task.

By designing the simplest UI possible, you’ll empower clients while saving yourself future support requests.

Take Complex Processes Out of a User’s Hands

The more tasks we ask a user to complete, the more opportunities there are for mistakes to be made. This rule of thumb applies just as much on the back end as it does on the front.

For example, consider a feature that allows a client to swap out an image. Perhaps that image needs to be cropped to a specific size to keep the layout intact. Or it might need to be in a particular format to maintain a transparent background.

That’s fine – as long as the client is adept at using a photo editor such as Photoshop. And they also need to remember to crop and save the image to match the website’s requirements.

Still, there’s always a chance they’ll forget one or more of these steps. It’s also possible that a new team member isn’t aware of the process you have put into place. This could produce undesired results.

This type of scenario might be avoided by employing the help of some tools. In the case of WordPress, the software is capable of automatically cropping an uploaded image to a predetermined size. And using a plugin such as Advanced Custom Fields allows us to limit what types of files are uploaded to a particular feature.

By automating these processes, we’re removing multiple layers of complexity. As such, our client won’t need to remember these steps. Instead, they’re taken care of in the background. And if the client does make a mistake, we can build in a failsafe to check and remind them of what needs to be done.

If a Task Is Too Complex, Tell Your Client

Despite our best efforts, some tasks may require a high level of technical knowledge. This might be a tricky design feature your client insisted on or a bit of custom code that powers crucial functionality.

This introduces some additional risks in terms of maintenance. As we noted above, multistep processes leave more room for user error. And anything left out in the open is fair game for breakage.

Rather than leaving a gaping hole in your client-proofing efforts, discuss the situation with your client. Explain the risks involved and offer ways to avoid issues. And if a feature is simply too difficult, perhaps it’s best left in your capable hands.

Regardless of how you manage the task, having an open dialogue is the best place to start. When clients understand the limitations, they’re more likely to help you arrive at the best solution.

Show Clients the Best Side of Technology

There are plenty of reasons why a client would want to manage their website updates. And web designers have a variety of ways to provide the required functionality. But, as they say, the devil is in the details.

The challenge is in making the process accessible to all users with basic skills. That means building intuitive features that can withstand unexpected usage. Users can also greatly benefit from automating complicated tasks when possible. And if a task can’t be simplified, it may be worth managing yourself.

It all starts with creating a plan. Think about how things should work and what might go wrong. Communicate with your clients and help them set up a workflow that eases their burden.

Yes, it’s a lot of work. But the end goal is helping clients to help themselves. When they can do their work efficiently and without problems, that benefits everyone – including you!

The post Keeping Barriers Low for Clients Who Update Their Website appeared first on Speckyboy Design Magazine.

Thus, convincing a client to invest in a custom website can be difficult. They may see the low-cost options as being just as good. Or they simply may not understand the difference.

It’s up to us to educate prospective clients about what we have to offer. We must demonstrate the advantages of a custom website and its long-term value. Here are some tips for making your case.

Explain the Differences

If you offer custom design and development, it’s getting more difficult to compete based on price. Popular services like Wix and Squarespace offer business owners an easy and cheap way to build a website.

As such, designers will lose out when the decision is based on initial cost. But prospective clients don’t always look at the fine print. It’s often the details that show the true value of a service.

Let’s look at a few key factors worth pointing out:

Limited Functionality vs. Custom Functionality

DIY services may offer functionality that a site owner is looking for…or not. They’re good at including features that users have come to expect. But they don’t offer everything. If what they have on hand doesn’t match your needs, you’re out of luck.

A custom website doesn’t necessarily run into these issues. If, for example, a WordPress plugin doesn’t exist for a desired feature, it’s possible to build one. You’ll pay more, but you’re also getting exactly what you want.

Nowhere is this more evident than in eCommerce. It seems that no matter how “simple” an online shop is supposed to be, there are always quirks. This often requires writing code or adding a niche plugin. That’s what puts the “custom” in a custom website.

Readymade vs. Original Design

Design should be an area where web professionals have the upper hand. A custom website is built around your business and the message you want to convey.

This differs from squeezing your logo into a readymade theme. The ability to have something unique that matches your specifications is also important.

There will always be those who are willing to sacrifice a unique look in exchange for a lower price. In that case, there are other worthy arguments to make.

Locked In vs. Freedom to Move

When buying into a DIY service, you’re usually working within the confines of a walled garden. You can’t take your website with you since the platform is proprietary. Closed systems do have some advantages, but they’re also a one-way street.

A custom site using an open-source CMS won’t lock you in. You’re free to host it just about anywhere. And there are usually tools available to help you switch to a different platform.

Web Designers Offer Experience and Expertise

A great website requires several ingredients. There needs to be a strategy behind its look, functionality, and content. Without such goals, it’s easy for a website to become inconsistent and aimless.

This is especially the case for small businesses. They may not have a team of experts on hand. It’s also an area where an experienced web designer can be an asset.

There is great value for clients in hiring someone who knows what they’re doing. A designer can pick up on those little details that would otherwise be missed.

An organization’s website is too important to be trusted by anyone less than an expert.

Building Successful Long-Term Relationships

Web designers often build long-term relationships with clients. And we are there to provide expertise, support, and advice. Those things can’t be easily replicated or replaced.

It’s an important distinction and a key selling point. The ability to easily communicate with a designer is vital. It’s also an advantage over large conglomerates. It sure beats waiting on hold for a support representative (who may or may not be able to answer your question).

Plus, the personal relationships we develop with clients mean that we are invested in their success. They’re not just another number. They’re a person who can rely on you to provide great service.

A dependable partner is worth their weight in gold. It’s one less thing for a business owner to worry about.

An Investment in Growth

When speaking with a potential client, note that building a custom website is a long-term investment. It’s something that can evolve and grow along with their business. While budget is an understandable constraint, you get what you pay for.

Many of the low-cost site builders provide a respectable product and have a legitimate place in the market. But in general, they’re for those with either extremely low budgets or a real DIY spirit.

Frankly, most organizations don’t have the time to put things together themselves. Nor do they have the design or marketing expertise to create something impactful. Depending on the tool they use, some end up frustrated by the process and decide to hire a professional.

Business owners tasked with doing it all themselves on a limited platform may be wasting time. It also takes them away from their true strength – running their business. That can stall growth and negate any initial cost savings. That’s kind of a big deal.

Custom Websites Are Usually the Best Option

Indeed, freelancers and small agencies aren’t the only game in town when it comes to web design. But we still provide a level of service and expertise that isn’t easily matched.

Those who need a website are hearing mixed messages about which path to choose. Some site builder tools can afford huge ad campaigns to tout their services. The rest of us must rely on the quality of our portfolios and communication skills.

Thankfully, that more personal approach provides us with the opportunity to show our true value.

The post How To Convince Clients To Invest in a Custom Website 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.

We discuss some of its built-in features. And how it makes starting a blog easier. Oh, and we can’t forget that it’s free and open-source.

It sounds pretty good, right? That is until I tell you that it will still be around 20 years from now. That’s when you politely excuse yourself and grab a seat at the other end of the café.

“He’s delusional.”, you think. And I wouldn’t blame you for assuming as much.

After all, there are very few things on the web that last for 20 years. And even fewer that continue to grow and thrive. Yet, WordPress has beaten the odds. It celebrates the big 2-0 on May 27, 2023.

With that, I thought it would be appropriate to look at how WordPress has made it this far. What are the secrets of its success? Here are a few factors that have led the software to incredible heights and longevity.

A Focus on Ease of Use

The first wave of content management systems (CMS) was often frustrating to work with. The installation process was a pain. And creating content was clumsy, to say the least.

WordPress and its famous 5-minute install process were refreshing. Yes, it required some technical knowledge. But it felt like a cakewalk when compared to its contemporaries.

That focus on ease of use carried through to the dashboard. Even today, a core installation of WordPress is relatively simple to navigate. It’s only after you start adding themes and plugins that the UI becomes muddled. But I digress…

Plus, content could be easily created and organized. That allowed bloggers to focus on writing, rather than overcoming technical hurdles.

Perhaps this doesn’t sound like a big deal. But it was a game changer in the early 2000s. Once I tried WordPress, I could no longer recommend popular competitors like PHP-Nuke or Typepad. I suspect many users felt the same.

What’s more, the software has had further advances in UX. The Site and Block editors have come a long way in recent years. And many web hosts now provide one-click installations.

Is WordPress the easiest CMS to use? That’s debatable. But it still provides a path for getting started with minimal effort.

Built With Customization in Mind

WordPress also excels when it comes to customization. It’s been built to accommodate all manner of tweaks and enhancements.

The most obvious example is the massive theme and plugin ecosystem. Developers can hook into and extend the core software. That made it possible to go beyond blogs. Users can leverage WordPress to run virtually any type of website.

But you don’t have to rely on third-party code. It’s also possible to build themes and one-off custom plugins. This enables us to create site-specific looks and functionality.

Customization also extends to site content. The advent of custom post types and taxonomies has given us fine-grain control over organizing posts. And custom fields have brought the same capabilities to every part of the CMS.

In my opinion, this still separates WordPress from much of the CMS market. Many DIY build tools limit your options. Thus, if you want to go fully custom, WordPress continues to be a great choice.

At the same time, you also have access to tens of thousands of themes and plugins. This allows you to choose between readymade and bespoke solutions.

The Embrace of an Open-source Ethos

The tandem Mike Little and Matt Mullenweg co-founded WordPress as a fork of b2/cafelog. The software has remained free and open-source. And it has received contributions from people all over the world.

But what if WordPress had been commercial software? If Little and Mullenweg had charged, say $100.00 per install, would the CMS still be around?

It’s certainly possible for a commercial product to survive 20 years. But there’s no telling how it would have impacted the software’s direction. And perhaps the size and strength of the ecosystem wouldn’t be on the same level as it is today.

Adopting an open-source ethos and GPL licensing may have been risky in 2003. Projects on the scale of WordPress weren’t common. Not to mention the stigma that free software faced from the corporate world.

There were no guarantees that this structure would work. And yet it has continued to thrive. The mission to “democratize publishing” has held strong.

Anyone can download a copy of WordPress and share their message. Web designers can use it to make a living. The decision to remain an open-source project has helped make this possible.

A Community Dedicated To Sharing

The above ingredients are vital to fostering a community. They have helped WordPress build a cult-like devotion that is rarely seen in the software industry.

Community members contribute to WordPress in many ways. Some work directly on the core software or various official teams. Others are keen to interact and share what they’ve learned.

People of every background and skill level take part. There’s a robust online community. And in-person events such as WordCamps have come back post-pandemic. Indeed, WordPress meets us where we are.

Like any community, there are positives and negatives. But the continued participation of WordPress fans worldwide keeps the software relevant.

Unlike commercial competitors, WordPress does not have a huge marketing budget. They can’t hire celebrity spokespeople.

Instead, they rely on users, agencies, and freelancers to spread the word. In other words: we’re the ones powering WordPress and nurturing its growth. No other CMS can make this claim – at least not on such a large scale.

I’m convinced that, no matter how amazing the product, WordPress needs a strong community to thrive. Maintaining and improving that synergy is key to making it another 20 years and beyond.

Happy Birthday, WordPress!

It’s not often that you can say that software changed your life – or the trajectory of your career. But WordPress has done both for me. And I know many others feel the same.

So, let’s take a moment to think about the people that have contributed to the project. Their work often happens behind the scenes. We owe them a debt of gratitude.

Happy birthday, WordPress! It’s been quite a ride so far. I can’t wait to see what’s next.

The post WordPress Turns 20: Its Secrets of Success appeared first on Speckyboy Design Magazine.

The industry seems to be going against the grain on that last one. New tools are continually being introduced – which is great. However, with them comes an expectation that designers will race ahead and dive in headfirst.

Or, at least it feels that way. It seems like we’re being pressured from all sides to adopt the “next big thing”, lest we be left in the dust.

In my thoroughly unscientific observation, many web designers appear to be frustrated with the state of things. Today, we’ll talk about why that is and how taking a step back could be the solution.

Trusted Apps Are Switching Gears

Nowhere is the seismic shift more visible than with WordPress. The massively popular content management system has undergone significant changes in the past few years. The Gutenberg block editor and its related features make for an entirely different experience.

Virtually every aspect of building websites and creating content has shifted. Depending on who you ask, these changes are either infuriating or the dawn of a new era. Regardless, there has been a great amount of pressure for web designers to adapt.

Whether it’s the editor itself or the introduction of block-based themes/Full Site Editing (FSE), there appears to be a good bit of sentiment that these changes are being forced upon web professionals.

That being said, there are alternative ways to use and build with WordPress. The Classic Editor is still supported, and the traditional methods of theme creation will continue to work. No one can fully predict the future, but it seems reasonable that they’ll be around for a while.

So, why would anyone feel forced into using something they aren’t very excited about? I think a lot of it has to do with how these new features are presented.

In the case of WordPress, Gutenberg became the default editor. It was front and center, whether you wanted it or not. And if you want to go back to the old way, you’re required to install a plugin.

Intended or not, this type of action establishes a narrative for users. It says, “The new way is here, and we want you to start using it immediately.”

Outside Pressure from Big Tech

Pressure doesn’t just come from software makers. It even goes beyond our peers and clients (as if that weren’t enough). Sometimes it can come from outside parties that have a vested interest in what happens on the web.

Take, for example, the various initiatives that Google has implemented over the years. Whether it’s a tweak to their search algorithm, the demands of its Core Web Vitals metrics, or the push for publishers to adopt Accelerated Mobile Pages (AMP) – the company holds a lot of sway when it comes to how we build websites.

It’s easy to see how web designers might feel at the mercy of this and other tech-heavyweights. We naturally want our websites to perform well and be easily found in search engines. Thus, it’s on us to integrate their recommendations and preferences into our work.

And it makes sense that we’d gravitate towards the companion products and services these companies offer. If we’re trying to satisfy a particular requirement, it’s logical to use tools that live within that ecosystem. They give us the best chance to succeed, even if we’re not thrilled at the prospect of using them.

Again, there’s a feeling of being forced into this type of arrangement. It’s especially relevant in client work, where your job is to provide the best path for achieving their goals. Sure, there are alternatives. But there is also risk in going a different route.

The Impact on Web Designers

What does this all mean for web designers? For one, it can lead to frustration. Among the root causes could be the great investment we make in these tools and technologies. A lot of effort goes into learning them, only to feel as though the rug is being pulled out from underneath.

There can also be a bit of uncertainty. When it comes to new features, things tend to evolve quickly. What counts as a best practice today might be very different tomorrow. The result is that designers are left wondering about the right time to make a move.

In addition, the disruptive nature of such changes tends to throw a monkey-wrench into the daily workflow. Whether it’s a new editing experience or a different coding language, it can be a struggle to get up to speed.

For some, the change is all too much. I’ve seen several instances of designers and developers leaving behind both tools and communities that they’ve contributed to.

One can make the argument that there will always be some level of attrition. And while that’s true, it’s also a negative when longtime contributors become disillusioned to the point of walking away.

That’s not to say everyone will come to this conclusion. However, it does speak to the issue.

Taking a Holistic View

The way we work isn’t just a professional concern. For many of us, it’s personal. We get attached to not only the tools we use but also to the routines we form along the way.

As such, some changes can be especially challenging. Add to that the prominent way new features or standards are thrust upon us and it’s no wonder there’s a sense of being forced to comply.

Yet it’s also worth taking a step back and looking at the situation holistically. Quite often, there are still options within the CMS, framework, or service provider you’re working with. They may require some additional action on your part, but they’re available nonetheless.

Unless there is a major security or functionality concern, it’s usually fine to stick with your current workflow. That “amazing” new way of doing things will still be there (or not) whenever you’re ready.

And that’s the great thing about being a web designer. No matter what changes, you have a say in how you work. That’s worth remembering as the web keeps on evolving.

The post How Web Designers Are Adapting to Industry Changes appeared first on Speckyboy Design Magazine.

The argument made sense on some levels. Facebook Pages were free – websites not so much. Why pay for a potentially complex marketing vehicle when there was a simple, no-cost option? This seemed like a particularly good path for small businesses.

As you might have guessed, that optimism faded rather quickly. Facebook started charging for the ability to reach your entire audience. It also became increasingly difficult to stand out in a user’s chaotic social feed.

Now, let’s fast-forward to today. Elon Musk’s purchase of Twitter (and subsequent headline-grabbing actions) has caused concern among users. Content moderation has taken a backseat to the billionaire’s vision of what the platform should be. It’s fair to wonder how this will impact the ability to reach and engage with people.

With that in mind, it seems like a good time to reinforce the important role websites play. Here are some reasons why they’re still the best bet for anyone that has a message to share.

A Permanent Home for Your Content

Social media still offers a great way to promote your content. But your content shouldn’t live on Facebook or Twitter. Rather, social postings should point readers toward your website.

Housing exclusive content on social media is a risk. Changes in platform ownership or policies could negatively impact what you’ve built. And if you decide to leave a particular service, how are you going to take everything with you?

Websites serve as a repository for content. That’s precisely what content management systems (CMS) such as WordPress are meant to do.

News, blog posts, and multimedia can be added, edited, or removed at any time. Most social networks don’t make these processes easy. Finding a particular tweet that you failed to bookmark, for example, is like finding a virtual needle in a haystack.

Most importantly, you’ll maintain ownership of your content. This means that you’re not subject to the whims of a third-party service provider. And you can keep it as long as you want.

The Focus Is on You

Users have a notoriously short attention span. Add to that the sheer number of posts in a typical user’s timeline and the popularity of doomscrolling. This makes social media a difficult place to make an impact. All but your most loyal followers will struggle to see your message.

At the very least, a well-made website will take those last two items out of the equation. Getting users to care is still a challenge. But you’ll stand a fighting chance when compared to the algorithm-enhanced free-for-all on the likes of Facebook.

A website can provide visitors with a clear path to action. It gives them space and time to explore content. And it serves as a reference that can be easily accessed later.

You’re not limited by character counts, nor forced to compete with thousands (or hundreds of thousands) of other posts on a feed. For one shining moment, the focus is on you with zero distractions.

It’s an opportunity that most social media platforms can’t offer. Plus, you’re in complete control of the user experience.

Websites Can Live Anywhere

Companies can come and go without a moment’s notice. Others may simply fall out of favor (I see you, MySpace). It’s something that can impact both social media and website providers.

The big difference is that a website offers options. Even if your DIY website tool were to go belly up, you could still rebuild elsewhere. And an open-source CMS gives you the flexibility to host anywhere.

If your social media network of choice went away, you’d likely be left in the cold. Your data may or may not be accessible. And what use would you have for it, anyway? It’s not like you can import your tweets into LinkedIn and keep moving forward.

Plus, if you’re not satisfied with your current site, you can make changes. Hosting, CMS, look, content, and underlying technologies are all fair game. If you have enough budget, virtually every part can be customized to match your needs.

Keep the Roles of Social Media and Websites in Mind

For a brief moment in history, the lines between social media and websites may have become blurred. Some saw the potential of the former to be a primary messaging tool. But as social media has experienced both growth and controversy, the division between the two has become clear.

Sure, many web designers may have understood this concept from the start. But clients aren’t always aware of what makes a website necessary and unique.

They may have been swayed by the thrill of posting content wherever they’ll get the most “likes” and comments. As such, they may not have thought about what happens when a platform goes away or is no longer an attractive option.

If you help clients with their marketing and content strategy, it may be worth having this conversation. Help them to understand what role social media can play in their success. But also look at the associated limitations and risks.

Conversely, there are benefits to using your website as a driver of content. This is a solution that can withstand the test of time – no matter what happens on social media.

The post How Social Media Uncertainty Reinforces the Importance of Websites appeared first on Speckyboy Design Magazine.