It’s time for my annual look at the year ahead. This satirical report is chock-full of useless facts and mindless predictions. That makes it just as good as any year-ahead article on the internet.

How do I do it? Like most internet companies, I use a proprietary algorithm. I prefer to keep it a secret. But it involves looking at the past and employing an overactive imagination. It can be yours for a small fee, by the way.

So, what does 2024 have in store for us? Here are some things that absolutely will (or probably won’t) happen.

WordPress.com to Offer Tweet Rebuttals

2023 was an eventful year for WordPress – and not all of it was positive. Then again, a little #WPDrama is a fine spectator sport.

The divide between co-founder Matt Mullenweg’s commercial venture (Automattic) and the open-source project once again raised some eyebrows. The (supposed) problem? Automattic’s WordPress.com replicated plugin listings from the WordPress.org repository on its site.

Plugin developers expressed concern that the commercial site’s listings showed up first in search results. Mullenweg was personally called out regarding the issue. The criticism was harsh and accusatory.

He responded aggressively – even banning a member of the open-source project’s marketing team on Twitter/X.

Right or wrong, these events got the WordPress community talking. The level of discourse was palpable.

It also got my predictive senses tingling. There must be a way to capitalize on this phenomenon – right?

Mullenweg responded to many critics – but certainly not all. Were you left out? Don’t worry! You’ll have a chance to get in on the action.

WordPress.com will soon unveil its “I Beg Your Pardon?” service. For a $20 fee, Mullenweg will personally respond to a critical tweet of your choice.

No worries if you’re short on cash. A free version from WordPress.org will get you an automated response from a bot.

Happy to take your listing down and redirect to another plugin page, which do you recommend as a good alternative?

— Matt Mullenweg (@photomatt) September 13, 2023

Apple Will Thrill Fans with AI

Rumors abound that Apple is working on an artificial intelligence platform. How might it work? What are its capabilities? I have a few predictions.

A Stiff Barrier to Entry

Apple loves to sell us premium products. And they also enjoy exercising tight control of them. Don’t expect their AI offering to be any different.

Thus, their platform will only be available to those using Apple devices. But that’s not all. Adding Apple’s AI to your workflow will also require a proprietary cable. No, not the one you already have.

We’re talking about a completely new connector type. The good news is that it’s currently hidden on your device. It will reveal itself upon sensing the cable’s presence.

The bad news? The dongle costs $500. And customers will have to wait at least six months for delivery. As usual, a large number of preorders will be the culprit.

An AI Powered Website Testing Suite

Web designers will be thrilled to see Apple’s AI testing suite. Enter your URL and watch the magic happen.

The tool emulates multiple devices. For example, you can troubleshoot your client’s buggy site on their 8-year-old Android phone. Or figure out why your responsive styles aren’t working on a brand of tablet no one has heard of.

You can also test your sites on classic Apple devices. How would an Apple IIe render your home page? What about a Newton handheld? You’re a dongle away from finding out.

It Will Be a Roller-Coaster Year for Elon Musk

Perhaps you don’t need a crystal ball to predict some things. Elon Musk and chaos are the perfect couple (sorry, Grimes). It’s the gift that keeps on giving.

I believe Mr. Musk will have a busy year. Seriously, there will be something wild happening every day. Here are just a few examples:

• Musk will reveal (unprompted) that he ingested dozens of “E.T. The Extra-Terrestrial” cartridges. You know, the ones that Atari buried back in the 1980s. He may still have a stash in his basement.
• Musk will invent an implantable microchip that allows chickens to speak. Ironically, he’ll call it “Twitter“.
• What about the service formerly known as Twitter? Musk hasn’t forgotten about it. He’ll continue to reinstate banned accounts. Next up: Napolean. Watch out for a rant hundreds of years in the making.
• We hear the Tesla Cybertruck will finally start deliveries in 2024. What’s the catch? It only includes models that come equipped with a Musk-approved flamethrower.
• Tesla’s Autopilot feature is having issues. Musk will replace it with an “Autonag” option. A virtual Elon will criticize your driving skills and shout them through the car’s audio system. Transport will never be the same.

Best Wishes for 2024!

Yes, the predictions above are silly. But they underscore that we’re in a time of change. AI is disrupting our industry. The tools we use are evolving. Somehow, we’ll need to adapt. For instance, I may have ChatGPT write this article for me next year.

None of this will be easy. Web designers have weathered plenty of shifts, though. I’m still here – and so are you!

So, take a deep breath. Find something to laugh about. And do your best to make 2024 a great year.

The post The Grumpy Designer’s Guide to 2024 appeared first on Speckyboy Design Magazine.

If you look closely, you’ll find decades-old technology. And it’s not limited to outdated websites. The fingerprints of the past are all over cutting-edge sites as well.

Sure, many of these technologies have evolved. Others have faded into the background. But we still rely on them. Perhaps more than we think.

With that, here’s a look at the old-school tech that continues to shape the web development industry.

Apache HTTP Server

Apache is no longer the top dog in web servers. However, the platform still holds a significant market share. W3Techs reports that it runs on over 30% of servers. That’s a close second to competitor Nginx.

Equally impressive is Apache’s longevity. Its initial release came way back in 1995.

The web was a much different place in those days. Most websites of that era consisted of static HTML. Let’s not forget about the low-powered hardware and limited bandwidth as well.

Apache has managed to keep up with the times. It’s a highly scalable platform that can handle large amounts of traffic. It also supports next-gen tech like HTTP/2 and IPv6.

Plus, Apache is responsible for many familiar technologies of its own. Development staples like .htaccess, gzip compression, and URL rewriting are supported.

jQuery

People continue to write off jQuery. But it’s hard to find evidence of a slowdown. The JavaScript library is used on over 77% of all websites.

Compare that number with its supposed heyday of 2012. Its usage was a mere 49% back then.

Being bundled with WordPress is one factor in jQuery’s growth. The world’s most widely used content management system (CMS) boosts those numbers. But that’s not the only reason.

Many of us are familiar with jQuery. And we know how to use it. That level of comfort continues to make it a go-to library.

Plus, it’s still in active development. jQuery continues to be refined and optimized for performance.

Yes, there are other worthy frameworks. And vanilla JavaScript has come a long way. But we bury jQuery at our own risk.

JPEG Images

We’ve been attempting to replace JPEG images for some time. Newer formats like SVG, WebP, and AVIF promise lossless compression. But this old-school file type from 1992 still bests them.

Both SVG and WebP are gaining ground. Yet JPEG carries on with a nearly 78% usage rate. Why is that?

For one, JPEG has the advantage of being a long-established format. Just about every image editing app supports it. And many of us have become used to saving images this way.

It’s also universally compatible with web browsers. WebP, for instance, doesn’t work with some legacy apps. That’s becoming less of a concern, however. Many of these browsers are vanishing from the landscape.

But after all these years, JPEG still works well for photographs. And its file size outperforms WebP in certain situations. It may not be the best option in every instance. But the format is still a viable choice.

The Command Line

The command line harkens back to a time before the graphical user interface (GUI). You may remember typing commands into MS-DOS if you’re of a certain age. And early systems like Unix were also command-based.

It almost seems ironic that the command line interface (CLI) is still a part of web development. The lineage is there, though. Linux powers many web servers, after all. But it’s also the “Throwback Thursday” of the industry.

Web hosting companies have attempted to replace or supplement the CLI. Visual control panels can replicate some functionality.

But the CLI also brings speed and efficiency to the party. Tools like WordPress have their own CLI flavors. And they can accomplish tasks without the overhead of a GUI.

It also offers fine-grain control over commands. You can target specific database tables or folders with relative ease.

The CLI survives because it’s still incredibly useful. And it beats using punch cards any day.

HTML

Maybe it’s a bit obvious. But no talk of old-school web technologies is complete without HTML. It’s still the basis of what we do.

Conceptualized in 1989, HTML saw its first release in 1991. It has since seen numerous iterations. And it is still evolving to meet the needs of the modern web.

HTML is capable of powering a website by itself. But it no longer stands alone. We can combine it with other languages to get the desired result. That could be CSS, PHP, Java, JavaScript, Ruby, or anything else that comes along.

These additional tools allow us to style and manipulate elements. We can tie in with a database to conditionally produce output. That has paved the way for the complex web applications we see today.

At 30+ years old, HTML is still as relevant as ever. And perhaps more flexible to boot.

Older Tech Continues to Find New Purpose

Longevity isn’t very common on the web. Or not on the front end, at least. Design trends come and go quickly. As do the tools and services we rely on.

But beneath all of that lies a bedrock of foundational technologies. Each of the items above qualifies. They’ve been a part of our job for decades.

And they’re far from the only ones. We didn’t delve into CSS or FTP, for instance. But they, along with dozens of other tools, are vital pieces of the jigsaw for developers.

Their continued presence brings comfort. That’s a good thing in an industry that changes so quickly.

The post How Old-School Technologies Still Shape Web Development appeared first on Speckyboy Design Magazine.

You’ll likely take notice of the issue as you try to do them at scale. The more clients you have, the more difficult it is to manage. Things that used to take a few minutes of your day can turn into hours.

Developing processes for these tasks can help. It’s all about finding ways to create efficiency in your workflow. You can cross items off your to-do list faster and without cutting corners.

How does it work? And what tasks can be streamlined? Here are a few examples to help you get the most out of your time.

Use Tools to Speed up Software Updates

The age of content management systems (CMS) has brought a constant stream of updates. Apps like WordPress require a lot of attention. The core software, plugins, and themes all need to be updated.

The process isn’t too bad if you manage a single website. But it can also get out of hand rather quickly. Keeping track of new versions across multiple sites is difficult. And it’s too easy to miss an important update.

The right tool can help, however. Some services allow you to manage multiple sites via a dashboard.

These tools are a game changer for busy web designers. You can perform maintenance tasks within a singular user interface. They list available updates and can even alert you to security issues.

Keeping your CMS up to date is critical. The right tool can streamline the process and save you time.

Bulk Browser and Device Testing

Modern web browsers are outstanding. But there are plenty of outdated apps still in use. And we can’t forget about the wide range of mobile devices.

Ensuring our websites work across all screens is tedious. A litany of tests is required to verify that everything looks good and works correctly.

Automation can make a positive difference in this area. Browser testing tools will run your site on multiple devices. They’ll then provide screenshots to help you spot any issues.

These tools don’t replace hands-on testing methods. But they will provide you with a heads-up regarding what to look for. Plus, you can use them to test on lesser-used browsers and devices.

The idea is to gauge how your site works across platforms. And do so without spending a lot of time.

Keep Track of Your To-Do List with a Task Management App

How do you keep track of your projects? You’re wasting time if you’re using email or handwritten notes. These methods require fumbling through mounds of content.

Sure, your inbox has search capabilities. But what if you have thousands of messages? And thumbing through a stack of paper isn’t exactly efficient.

A task management app may be what you need. This category has come a long way in recent years. And there’s one for just about every niche. Popular tools like Trello and Asana come to mind.

Even better is that many work across platforms. That means you can look things up on your phone or computer. You can stay in the loop regardless of where you are.

Collaborative features can help you communicate with stakeholders. For example, you can check in with a colleague directly – rather than creating an email chain. And multiple people can cross items off their to-do list.

But even solo freelancers can benefit. Simply having a single point of reference is helpful. You’ll be less likely to forget something.

Automate Client Invoicing and Payment

Billing-related tasks are often a pain. They take precious time away from your projects.

And speaking of which, invoices are time-sensitive. This clashes with other things you have going on. It’s not ideal when you’re working on a tight deadline.

Old-school accounting software can help you create invoices. However, it often lacks the polished automation features of specialized platforms. You still have to get those invoices to your clients somehow.

Several cloud-based providers will do the dirty work for you. They’ll take your input and automatically email an invoice to your clients. An integrated payment gateway will collect your hard-earned money.

But these services offer more than just time savings. They also make it easier for clients to pay on the spot. Thus, your invoice is less likely to sit on their desk collecting dust.

Tax time is also simplified. Earnings and expense reports can be generated and shared with your accountant.

Make Your Web Design Business More Manageable

Every aspect of your web design business can benefit from repeatable processes. That covers technical areas like CMS updates. And it also applies to more mundane tasks like billing.

The ideas above are only a starting point. Think about other tasks that could use some attention. You can then identify ways to streamline them.

It may be easier than you think. Sometimes, it’s a matter of finding the right tool. Several apps cater to web designers and freelancers. And they can transform your workflow.

Don’t panic if you’re feeling stuck and falling behind on projects. Refining a process or two can make all the difference.

The post Develop Processes for These Web Design Tasks appeared first on Speckyboy Design Magazine.

That last part can be tricky. And it’s not just financial resources that are in short supply. Clients may lack brand assets as well.

The issue often occurs with smaller organizations. They might not have the budget for custom photography or print materials. Thus, you could receive a low-resolution logo and not much else.

Is a logo enough to build a design around? You may be surprised at what a logo can inspire. Even basic images can tell us a lot about our client.

With that, let’s see what we can learn from a client’s logo.

Their Preferred Colors and Typography

Here’s hoping your client’s logo features a few colors. It’s a big help in determining the website’s color scheme.

However, even a single color will provide clues. You can create a palette based on a primary color. Several online tools will do the job for you. They’ll generate complimentary colors and shadings.

You’ll want to run these by your client for approval. But a logo can do wonders for inspiring the perfect color scheme.

The same goes for typography. Simple logo fonts could be appropriate for use elsewhere. For example, a clean serif font makes for a solid text heading. Unsure of the fonts used in the logo? You can use a font identification tool to help.

Script and display style fonts aren’t always a fit, though. They could be too difficult to read as headings or body text. But you can still use them as a basis for finding acceptable pairings.

The Client’s Personality and Tone

Is your client’s organization serious and buttoned down? Or maybe they’re a bit more relaxed? Their logo can provide clues.

Both color and typography tell a story. Bright and neon colors may indicate a casual vibe. An old-fashioned wordmark says it’s all business.

Illustrations also play a role. Does the logo contain a cartoonish figure? What about a simple line drawing of an office? Each can help you create the right mood.

You can also use this information when choosing other design assets. Items like icons and stock photos should match the tenor of the logo.

There are other indicators beyond the logo. Your client’s industry is important. Their communication style is also a factor. Still, their logo says a lot about who they are.

A Path for Reaching the Target Audience

Who is your client’s target audience? Their industry and clientele are deciding factors.

But details may be scarce. Clients with limited brand assets may not have a lot of demographics to share. And they’re unlikely to have a research budget.

In that case, a logo can show you a path to reaching the right audience. Or at least facilitate an educated guess.

For instance, an image could convey the relative age of the audience. And it’s also possible to target other identifying characteristics. Things like gender, identity, or financial status come to mind.

All of this assumes that the logo fits your client’s brand. That’s not always the case. However, web designers can only work with what’s available. Any imperfections are out of our control.

Making the Most of the Brand Assets You Have

Designing a website without brand assets is difficult. How can we create a relevant look without a guide? And even a client’s previous website may not be of much help.

In many instances, a logo is all we have to go on. It happens time and again, even in this digital age. And it presents a challenge for web designers.

However, a decent logo provides a starting point. It can lead us to some answers. We can use it to craft color and typographic schemes. And it’s also possible to understand more about your client’s personality and target audience.

At the very least, a logo serves as a basis for discussion. Assess what you have and ask for your client’s feedback. You may be on the right track. Or your client may have to go back to the drawing board.

Either way, the logo might be the best tool to move the project forward. There are more details within than you may think.

The post Web Design When a Logo Is Your Only Brand Asset appeared first on Speckyboy Design Magazine.

I’m particularly fond of the Doomsday scenarios. You know, the very darkest of sci-fi fantasies. The possibility of working for a machine sounds modern. I wonder how well it pays?

Then there’s the idea that we must “learn” AI. The term “prompt engineer” has been thrown around. This one sounds perfect for a grumpy designer! It also seems like a job with a short shelf life.

We used to write code to direct a computer. But now we tell it what to do. It’s less work for more money. Who wouldn’t want this job?

But seriously. What should web designers learn about AI? Do we need to learn anything at all? I have a few unscientific ideas. Just take them with a grain of salt. I haven’t run any of this by ChatGPT yet.

AI Prompts Test Your Communication Skills

The idea of a career in prompt engineering sounds strange. But I admit that the job requires some skill. You might have issues if you’re not a gifted communicator.

Generative code seems like an area of relevance. Large language models (LLMs) like ChatGTP and Bard can accept vague instructions. That will likely produce some basic code. It serves as a foundation to build upon.

But complex code needs clear, detailed instructions. Not everyone possesses this ability.

Just think of the clients who have trouble explaining a design feature. Do we expect these people to generate the next great WordPress plugin?

The results may suffer if a prompt is too light or wordy. LLMs will likely improve. But there will still be hurdles for those who struggle with clear communication.

Your primary language may also be a barrier. What if a model isn’t well-versed in your language? That’s going to make prompts more difficult.

Therefore, it’s wise to brush up on your written communication skills. They’ll come in handy.

Using APIs To Build AI Apps

Several AI tools either have or will release an application programming interface (API). The concept should be familiar to web designers. The likes of Google and social media providers have similar offerings.

You can tap into the power of ChatGPT to build an application. This is useful if your project needs one-off functionality. Or if you have a killer idea that will make billions. That may be far-fetched. It seems like most people are using it to generate text thus far.

Learning one of these APIs won’t apply to everybody. It’s more likely that we’ll use apps created by others. For instance, a WordPress plugin that adds a chatbot to your site.

Understanding how an API works is still valuable, though. And there’s a market for niche applications. Perhaps the real money will be in helping organizations implement AI.

When To Use AI Tools

It’s tempting to use AI for just about every task. Just like your mother told you, the machine knows best.

But the reality is that AI isn’t good at everything. It struggles with accuracy. It even hallucinates occasionally.

Learning a tool’s strengths and weaknesses is vital. The facts, figures, and code generated by AI may look great. But how do you know for sure?

Practicing blind faith in these tools is not recommended. If accuracy matters, take the time to double-check the results. You might want to regenerate a response as well. AI tools will often provide multiple answers for the same prompt.

Thus, treat AI like that shady friend you had in high school. Feel free to hang out together. But don’t rely on it for anything too important. It will only get you into trouble.

Learn How To Get What You Want From AI

Like any tool, AI has a learning curve. But there’s no need to study every aspect. It’s more important to learn how to produce the desired results.

Your communication skills are vital. And tools that understand your instructions also play a role. Your success depends on both items.

What if you struggle to write AI prompts? There are a lot of guides popping up that can help.

And you can do more than follow their examples. Pay close attention to the way each prompt is worded. Experiment with similar language in your virtual conversations.

It also helps to be a bit grumpy skeptical. This will help you better understand the limitations of these tools. They don’t “know” everything. And, like the people they are supposedly replacing, they make mistakes.

The machines aren’t taking over yet. But it’s worth learning how to take advantage of them. You may end up as the more powerful being.

The post The Grumpy Designer Ponders What It Means To ‘Learn’ AI appeared first on Speckyboy Design Magazine.

I’ve been a user since 1999. I had a contracting gig. The client insisted that I use Dreamweaver. I wasn’t thrilled about this as I had come to despise WYSIWYG editors. The apps I tried wrote sloppy code. They weren’t for me.

But this software left a positive impression. Dreamweaver produced clean code and made my job easier. I found it to be miles ahead of my text editor. And I remained a fan as Adobe acquired the app in 2005.

Now, I’m a bit concerned about the future. As of this writing, Dreamweaver hasn’t released an update since June 2022. And even that was a security fix.

The competition isn’t standing still. Other code editors have long since surpassed Dreamweaver. They do a better job of integrating with modern frameworks. And they are typically more flexible.

With that, it’s worth asking where Dreamweaver fits in. Does it still have a place in web design? Or has it become irrelevant?

Dreamweaver Was Ahead of Its Time and Built for Longevity

The late 1990s saw an explosion of web design tools. Independent developers rushed to release WYSIWYG editors. And a few big players like Microsoft (FrontPage) and Adobe (PageMill) also jumped on the bandwagon.

As you might expect, many of these tools were rudimentary. Some were a little overambitious. The result was often a design that didn’t hold up in the browser.

Dreamweaver was like a breath of fresh air in this landscape. It was stable and didn’t try to do too much. It didn’t force proprietary or non-compliant code on us. It was an app that HTML purists could accept.

Plus, it kept up with a rapidly changing industry. Dreamweaver openly embraced languages like CSS, JavaScript, and PHP.

The app was a well-established favorite by the time Adobe acquired it. And the company continued to add bells and whistles to keep users happy.

And we can’t forget about the community. Dreamweaver had a thriving plugin directory. These extensions helped developers work more efficiently. And they tied in with burgeoning content management systems (CMS) like WordPress.

But Dreamweaver’s evolution has slowed to a crawl recently. Why is that?

An early version of Dreamweaver. Image courtesy of the Web Design Museum.

The Way We Design Websites Has Changed

Dreamweaver was initially a layout tool. Writing code was also part of the deal. Yet designing websites with a point-and-click UI was the software’s calling card.

That’s how I used to do things. I cobbled together layouts and then styled them using CSS. But this was during a time when websites were static. That’s generally no longer the case.

My workflow has changed. I use Figma to create a design mockup. From there, I build custom WordPress themes.

I still use Dreamweaver. But it’s primarily a code editor these days. I test my work in a web browser. That leaves the app’s WYSIWYG out of the picture – most of the time.

The feature still comes in handy for one-off HTML projects like this article. I use Dreamweaver to convert my word-processing documents to code. It’s a little taste of what once was.

Yes, it’s possible to connect the app to a WordPress website. But I’ve found the process to be clunky – and perhaps unnecessary.

As such, Dreamweaver’s core feature isn’t as relevant. I suspect that’s the case for many web designers.

Websites have become dynamic. Designers have found more efficient methods of building them.

Where Things Could Improve

The software still works as a passable code editor. You’ll find expected features like syntax highlighting and code hinting.

Things could certainly be better, though. There’s no built-in code hinting for WordPress, for example. A few outdated plugins are available. But native support could attract more users.

To that point, the plugin library has also become stale. It’s similar to the sunsetted Adobe XD. The remaining options tend to be from many years ago.

Community involvement has slowed. Thus, adding features relevant to modern web development should be a priority. Modernizing Dreamweaver might entice more developers to extend the software.

And there’s great potential in adding artificial intelligence (AI) capabilities. Adobe is already doing this with Photoshop. Generating code seems to be a natural fit.

Dreamweaver Hangs On, but for How Long?

I still open my copy of Dreamweaver daily. I use it to write CSS and PHP. It gets the job done. But I’m also stubborn when it comes to change.

I have a few other code editors installed. But I haven’t taken the time to explore them. Maybe I’m afraid that I’ll fall in love?

Regardless, I’d like to see Dreamweaver evolve. The app is iconic and a link to the early web. And it could be part of the future, too.

Here’s hoping it doesn’t go the way of web rings and MySpace.

The post Where Does Dreamweaver Fit in Modern Web Design? appeared first on Speckyboy Design Magazine.

Our answers come from experience (or a quick search). Yet, there is one question that seems impossible to answer. It has confounded even veteran designers: “How long will it take to build my website?”

It’s a perfectly reasonable question. One that should be simple to answer. But it’s also loaded with uncertainty.

The design and build processes are unpredictable. As such, you might hesitate to provide an estimate. Unfortunately, this clashes with a client’s need to know specifics.

Today, we’ll look at the factors that impact your project’s launch date. We’ll also provide some tips for giving accurate time estimates. Let’s get to work!

The Size and Scope of the Website

The larger the project, the more time it will take to complete. This will always be a key factor.

Both the size and scope of a website can impact its timeline. For example, building a content-heavy website could require a lot of work. And it also affects redesign projects.

The same goes for functionality. Readymade software like shopping carts are more efficient than ever. But they often need at least some level of customization.

Building features from scratch is also challenging. The trial-and-error process can be difficult to predict. There are always bumps in the road when writing code.

And we can’t forget about human resources. Large projects can be a slow go for solo freelancers, especially if you are juggling multiple duties.

Availability of Content and Project Assets

Launching a website is a two-way street. We can’t accomplish much without client participation.

The delivery of content and other project assets is often an obstacle. Waiting for these items to arrive can be the longest part of the process. The situation can grind progress to a halt.

There are several potential reasons for a delay. Sometimes it’s because a client is overwhelmed. That leads them to disappear. And just when it’s time to put the project to bed.

There could also be a lack of clear direction. Design politics can lead to a vicious cycle where ideas are debated and tossed aside.

The Synergy Between Client and Designer

There’s something to be said about the relationship between clients and designers. A bad one will lead to endless revisions and misunderstandings. A good one can keep a project on the fast track to completion.

Developing a solid rapport is important. Effectively communicating needs and ideas is a key to getting things done.

For example, setting clear expectations makes the job that much easier. Clients are more likely to deliver when they understand your needs. It’s also great to know what clients expect from us as well.

Being on the same page (or not) greatly impacts the project timeline. The more synergy you have, the greater the odds of an efficient process. It’s something to keep in mind.

Your Other Commitments

None of us lives in a project bubble. Thus, it’s likely you have multiple websites to focus on. This can be a challenge when it comes to providing an accurate project timeline.

It’s not just a matter of having additional work to do. The other items we mentioned are relevant to all projects. Therefore, you might face a lot of uncertainty.

One typical scenario: you’re waiting for several clients to send you project assets. What if they arrive simultaneously? You’ll be left scrambling to make progress on multiple fronts.

You’re either waiting for work or swamped with it. Sound familiar? Welcome to the rollercoaster that is freelancing!

Providing a More Accurate Project Timeline

It’s no wonder that this simple question seems impossible to answer. Even so, a fairly accurate answer is still a requirement.

Establishing a line of communication can help. It starts by learning about a client’s needs and wants. Try to uncover as much as possible early in the process. Spell it all out in your proposal.

Clients must also be aware of your needs and wants. For instance, they need to know their role in supplying project assets such as content. A delay in getting you those items can mean missing a targeted launch date.

There can still be unexpected roadblocks. That will usually be the case. But there’s a chance to minimize them through early communication.

The next time you’re asked that oh-so-important question, bring up the factors mentioned above. Together, you’ll be able to come up with a solid answer.

The post The Impossible Question: How Long Does It Take to Build a Website? appeared first on Speckyboy Design Magazine.

The 90s were also a golden age for technology as well. The personal computer made its way into the mainstream. And so did the World Wide Web. As such, I started toying with web design during this period.

Building a website in those days was undeniably different. The web design industry was nascent – if it existed at all. Standards and best practices were still years away. Web designers had to adapt existing tools for this new medium.

We made a lot of mistakes. But that’s OK. The lessons learned in that era have brought us to the present.

What was it like to build a website back in the day? Here are a few observations based on my experiences. One obstacle does stand in my way, though. I hope that I can remember that far back!

Web Design without a Map

I first began experimenting with HTML in 1995. The web was very much a novelty. Thus, few organizations had a website.

Web designers had no history to work from. We couldn’t, for example, find previous examples of successful websites. And there were no guides to tell us the ingredients of a great site.

That lack of precedent had benefits. We had the freedom to try all manner of designs and layouts. There were no trends to follow. With that came the chance to establish our own.

There were some downsides, though. We didn’t account for factors like accessibility. Websites from that era had all manner of issues. Poor color contrast, tiny fonts, and intense animation were among them.

We made things up as we went along. And that philosophy covered every aspect of a website.

Tools? What Tools?

Where would we be without web design tools? From code editors to prototyping, they help us work more efficiently.

The right tools are essential for modern web design. But early web designers had no such luxury. There were very few apps aimed at this new medium.

My toolbox consisted of a plain text editor (Windows Notepad) and a graphics app (MS Paint). Not exactly a dynamic duo for web design. But repurposing apps was common.

Even Photoshop was ill-equipped in those days. Its “Save for Web” feature wasn’t introduced until version 5.5. That meant large file sizes and little optimization.

Plus, helpful features like code hinting weren’t yet available. There were no frameworks to provide a quick start to projects. That meant manually writing code.

There were also few references for learning HTML. A handful of extraordinarily thick books existed. But the best way to learn was by viewing the source code of other sites. This technique also came in handy when CSS and JavaScript hit the scene.

Managing Content was a Hassle

We’ve become accustomed to using content management systems (CMS) like WordPress. But such apps were still years away from mainstream availability.

In the beginning, every page was a separate HTML file. Website navigation consisted of links to these files. As you might expect, there were also links within the page content.

Large websites could get incredibly complex. For example, my first job was working on a newspaper’s website. It grew from a handful of pages to over a thousand.

Ensuring that every link worked was like wrestling a giant squid. Changing the navigation was also a challenge. You might have to make the same edit to every file on the site. The advent of Server Side Includes (SSI) eventually simplified the process.

You also had to consider the site’s file structure. Everything was built from the ground up. Consistent file locations and naming conventions were vital. I came up short on a few occasions. But that’s how you learn!

Planning for future growth was essential. Otherwise, you may end up having to refactor the entire thing.

Technology Was Exciting, but Limited

As I mentioned, the 90s were a transformative time for technology. It seemed like computers were changing the world daily.

There were still some limiting factors, however. The computers of the day had little processing power. Graphics were also paltry compared to today’s standard. And we can’t forget the painfully slow internet speeds.

It’s a good thing websites were simple. Users didn’t have the necessary tools to view anything large or complex. Using a 28.8 kbit/s modem, it would take nearly 5 minutes to download a 1MB file. And that’s assuming a stable connection.

These technological limitations presented a challenge to web designers. Using large images was out of the question. Audio and video content had to be highly compressed. And a lack of standard formats meant relying on third-party software like Flash or Real Player.

None of this stopped designers from implementing poor practices. Some websites added “features” like background audio and proprietary code (thanks, Internet Explorer).

Oh, and if you haven’t experienced dial-up internet, the following video offers a great demonstration.

We Had No Idea What the Web Would Become

The web’s novelty wore off within a few years. It slowly became a necessity for all types of organizations. And the audience had grown beyond hardcore computer geeks.

The seeds of online commerce were beginning to take root. Even so, I had no idea how big the web would become. And I couldn’t foresee the impact of smartphones and wireless internet.

But it’s worth remembering that things didn’t start that way. The 1990s version of the web seems light-years away from the present.

Little did we know that our experiments would lead to something bigger. A platform that adopted standards and developed trusted techniques. Not to mention methods for interacting with data in real-time.

Maybe the web is a better place in terms of technology. But it couldn’t be more fun than it was back in the day. It was amazing to witness.

The post Here’s What It Was like to Build a Website in the 90s appeared first on Speckyboy Design Magazine.

But “small” is a relative term. A project can be small in terms of profit. Yet that doesn’t mean that it’s quick or easy. You may still need to perform a lot of work.

Why is that? These less-profitable projects tend to fall into two categories. The first involves clients who are on a tight budget. The other belongs to cheap clients that aren’t interested in spending money.

We need to be aware of the latter group. They offer opportunities for neither learning nor growth. Here’s how to tell the difference between cheap clients and those on a budget.

What Are Your Client’s Expectations?

The majority of people live within a budget. That often means settling for what we can afford.

Having realistic expectations are a part of the deal. For example, we wouldn’t expect to buy a new Lamborghini for the price of a used Chevy.

Clients often have similar budgetary restrictions. And most are reasonable in their approach. They’re willing to work within the parameters we set. If a feature is too expensive, they may save up to add it later.

But some clients don’t seem to grasp this concept. They expect enterprise-level features on their website. Yet they’re unwilling to pay the price to make it happen.

Instead, they haggle and harass. They question our ability to get the job done efficiently. And they scoff at paying for services like hosting.

Sometimes it’s a matter of educating a client. They may not understand what’s required to fulfill their requests.

But some people are unabashedly cheap. They’ll go to extremes to save money. This behavior hurts both the project and your relationship.

Cheap Clients Try to Pass Costs to You

Creating a website proposal follows a familiar pattern. A client tells us about their project. And they’ll tell us how much they’re looking to spend. We then provide an estimate based on their budget and needs.

In other words, we tell clients what they can do for the money. We may also advise them on how to get the most value.

Nothing here is set in stone, however. A client may decide to spend more or less. It often depends on the expected return on investment (ROI). If spending more gets a better return, some clients will gladly do so.

A cheapskate client may see the value of an expensive feature. But they’re likely to haggle about the price. They may want a discount – even if it hurts our bottom line.

There’s no harm in trying to reduce costs. But expecting their web designer to absorb the hit is unreasonable. And it renders their project goals unrealistic.

The rule of thumb is simple. If you can’t pay for what you want, make adjustments. It seems like the cheapest clients are incapable of this kind of change.

Be Careful of Who You Work With

Most web design projects come with a budget. That’s a normal part of working with clients. We do our best to deliver the most bang for the buck.

And working with clients on a tight budget can be worthwhile. Lower profits aside, the experience is valuable. It’s often the perfect introduction for new freelancers or small agencies.

Plus, there’s a chance that your relationship will grow. A client’s budget may increase in the future. That could mean more revenue when it’s time for a redesign.

These relationships are worth pursuing. But be careful. Not everyone is on the up and up.

Some people will try to take advantage of your generosity. They’ll ask for the moon and pay pennies on the dollar.

Accepting this type of project will make you miserable. A cheap client won’t appreciate your efforts. And your bank account will suffer. It’s time you could have spent working on something better.

There’s a difference between a cheap client and one on a budget. The former will expect you to bend to their needs. The latter will be happy to compromise where necessary. Make sure you choose wisely.

The post The Difference Between Cheap & Budget Clients appeared first on Speckyboy Design Magazine.

What do they want? The traditional “fast and cheap” website, of course. These clients expect us to perform Herculean tasks for peanuts. And they’d appreciate it if you could do it all within two weeks. No pressure!

These requests have always been a thorn in our side. And it’s fair to wonder how realistic they are. Even more so as the web has matured.

Let’s take a fresh look at this old nemesis. Should they be tossed into the dustbin of history? Or does fast and cheap still have a place in web design?

Build Tools Are Better. But Websites Are More Complex.

My first experience with building fast and cheap websites came long ago. These were the days before content management systems (CMS) and no-code tools. Static HTML was the primary technology used.

There’s no denying that it was a stressful situation. But I routinely churned out new websites within 2-3 weeks. It sounds counterintuitive when looking back. How did I do this without the help of advanced tools?

I think client expectations played a role. A typical website was relatively simple. And the projects weren’t heavy on content. Most were of the five-page brochure variety. Functionality consisted of a contact form.

These days, a CMS like WordPress would seem to be a perfect fit. Install a theme, add the content, and off you go. You wouldn’t need to touch code for something basic.

But that’s just it. Clients no longer want a barebones website. Their expectations have evolved along with technology.

There’s always “one more thing” to do. Plus, there are multiple pieces to put together. All of this takes more time than a client realizes. The result is higher costs and a longer time to launch.

Ignoring Mobile and Accessibility Isn’t an Option

Something else stands out from the past. We didn’t have to build and test our websites on dozens of devices.

Ensuring quality and consistency across screens is tedious. There is a nearly endless array of viewport sizes to consider. And even a readymade CMS theme isn’t without hiccups. Therefore, testing is mandatory.

And the same logic applies to accessibility. We didn’t think twice about “just launching it” twenty years ago. That’s a dangerous proposition these days.

There are both legal and moral obligations. Plus, building an accessible website requires a plan. It works better when baked in from the start.

Once again, these steps mean more time and money. Ignoring either of them isn’t an option. And neither is hurrying through their implementation.

When ‘Fast & Cheap’ Might Make Sense

Building a website quickly and cheaply doesn’t fit with most projects. The factors above are the primary reasons.

And we can’t forget about a client’s role. They may not be able to deliver on their outsized expectations. That’s how two weeks can turn into six months. The reality of their requests often results in a reconsideration.

But there are still a few occasions where this mix might make sense. A single-page website is one example. A promotional microsite is another possibility.

It may be wise to consider these websites to be temporary. There’s not enough time or money to build with the future in mind. Thus, they’re best suited for a short-term goal.

A page builder tool or a predesigned template could make quick work of this type of project.

The caveat is that the site must be light on customization. Clients must be limited to the options offered by the build tool. That means no fiddling around with PHP or JavaScript. This strategy also eliminates most eCommerce possibilities.

A client must also be willing to compromise. They may not get everything on their wish list. A shoestring budget and narrow timeline will only get them so far. That’s how this is supposed to work, after all.

Should You Accommodate These Clients?

Yes, it’s technically possible to build a fast and cheap website. The real question is whether you want to accommodate these clients.

You could pull all-nighters to create a fully functioning 500-page site in record time. But is that worth your time and effort? Probably not.

You should be paid handsomely for this level of work. And it’s only fair to have enough time to complete the project. Otherwise, your client isn’t valuing your time or talent.

Therefore, any consideration of fast and cheap should come with strict boundaries. Give your client minimal options and plenty of conditions to abide by.

And if you’re not comfortable with the arrangement? It’s more than OK to decline. That’s something you can do quickly – and for free!

The post Is the ‘Fast & Cheap’ Website Still Realistic? appeared first on Speckyboy Design Magazine.