Articles

It’s no secret that having a custom domain name is an essential piece of any company’s branding strategy. While there are a myriad of hosting plans available that offer domains like your company.webhost.com, making the shift from one of those to simply yourcompany.com is an important step.

However, your domain branding strategy need not end there. Domain mapping offers an opportunity for web developers and online business owners the ability to improve their marketing campaigns, protect their brands from competitors, cut down on costs, and develop a more efficient workflow.

What is Domain Mapping?

Domain mapping refers to how visitors to your website are directed to different domains and subdomains and what URLs will be displayed in the visitors’ browsers.

When you first set up your online business, one of the very first things that you do is register a domain name for your company website. But depending on the business, it could be wiser to actually register multiple domain names at once. This is because you will want to lease the primary domain name you plan on using in addition to all related TLDs. This way, cybersquatters will not be able to hold your domain name hostage, especially once you have grown into a more established brand.

For example, if you register the name yourcompany.com, you might also want to register yourcompany.net and yourcompany.org. Then you might set up a URL redirect so that visitors to the latter two sites will be redirected to yourcompany.com. However, with a domain redirect, visitors to yourcompany.net and yourcompany.org will be redirected to yourcompany.com, meaning the URL in their browser will appear as yourcompany.com no matter what they typed.

With domain mapping, this isn’t the case. A visitor to yourcompany.net will still see that URL in their browser even if the content is actually being hosted on yourcompany.com.

Benefits of Domain Mapping

Although domain mapping may seem a bit esoteric and complex at first, it serves several purposes and offers many benefits:

1. Make Web Addresses Easier to Remember

Imagine that your restaurant chain, Larry’s Lunches, just opened a new chain on 116th Street in New York City. Your first instinct may be to direct customers to larryslunches.com/116thstnyc, but that domain is a bit long and hard to remember. Instead, you might want to register the domain larrys116th.com for customers for that specific store.

With domain mapping, you can serve up the content from your main domain, larryslunches.com, while still having your visitors see larrys116th.com. This makes it easier to brand your sites without having to manage several different sites.

2. Boost Your Web Development Career

If you are a web developer yourself but are not admittedly well-acquainted with domain mapping already, you would do well to change that.

One of the easiest ways would be to look at online web development programs that one can take to read through documentation to get caught up to speed on how domain mapping can help their efforts and how to implement it. These kinds of programs can be more comprehensive than university courses and offer an impressive 88% job success rate for those who successfully complete the programs.

3. Shield Your Brand from Competitors

Remember, it’s a good idea to purchase several different related domains in anticipation of competitors snatching them up from you. Choosing the right domain names is essential to protecting your brand.

For example, Larry’s Lunches might want to snag larrysnyclunches.com and larrysfamouslunches.com as well. However, simply leaving those domains parked can be a bit of a waste, and managing multiple domains can be a pain in and of itself.

But with domain mapping, you can manage those domains just as easily as if they were your primary site, so you no longer need to leave them empty.

4. Save Time and Lower Development Expenses

Development isn’t cheap, and time is money. While the maintenance costs for a website are already high enough, adding in separate domains can sometimes break the bank due to the increased complexity of managing so many different moving pieces.

Domain mapping can lower expenses and save time by keeping everything tidy and in one place. By managing everything from a single WordPress installation, for example, you can push updates to all your subdomains at once, saving you from the tedium of going through each domain and making the same updates.

5. Manage Client Sites from One Place

If you’re a freelance developer or run an agency, using domain mapping for some of your clients’ sites can save you time as well. For example, if several clients want blogs, and you use the same infrastructure for them, you can easily push updates and changes to all of them at the same time. In short, domain mapping can make maintaining sites much easier and quicker.

How to Implement Domain Mapping

If you’re sold on the benefits of domain mapping, here’s a quick primer on the steps you’ll need to take to get started:

  1. Choose a domain registrar: The ideal registrar you choose should come with a number of important features including adequate hosting for keeping your website visitor friendly, SSL certification to ensure security, 24/7 customer support, comprehensive packages that make it easy to operate your online business.
  2. Register the domains you’re interested in: These can either be domain misspells (otherwise known as typosquatting), like youcompany.com, yourcmpany.com, etc, or related domains like yournewproduct.com, yournewlocation.com, etc. Whatever you decide to go with, you’ll need to have it registered before you can get started.
  3. Install WordPress Multisite: WordPress is one of the easiest ways to develop websites, and that holds true for domain mapped sites as well. Plus, considering WordPress sites account for over a third of the entire internet, you can’t go wrong with the famed CMS. All you need to do is install WordPress and, once that’s installed, open wp-config.php and add define(‘WP_ALLOW_MULTISITE’, true) above the /*.
  4. Configure your DNS settings: Next, you’ll need to point all your name servers to your hosting account. These changes can take up to 72 hours to go into effect.
  5. Add domains to your hosting plan: From your hosting platform, you’ll need to link your custom domains. You can usually do this from your cPanel.
  6. Map subsites to your custom domains: Once you have your domains set up, you’ll need to link them through WordPress. To do so, simply login and navigate to Sites -> Add New. After you assign them a subdomain or subdirectory name, you can click Edit and add your custom domain. Then just hit Save Changes, and you’re good to go.

Take note that domain mapping is not necessary for transferring a domain name. When you map a domain, you’re simply telling your domain where it can find your website on the internet through having your name servers updated. When you change your name, it only affects where the domain has been resolved.

The Bottom Line

While domain mapping isn’t necessary for all websites, it can still be a major timesaver. By utilizing it properly, you can greatly improve the standing of your online business by saving time and money, making website management easier, and improving the branding of your sites.

 

Featured image via Unsplash.

Source


Source de l’article sur Webdesignerdepot

We are gathered here today….

Today I write in memory of Adobe Flash (née Macromedia), something that a bunch of people are actually too young to remember. I write this with love, longing, and a palpable sense of relief that it’s all over. I have come to praise Flash, to curse it, and finally to bury it.

We’ve been hearing about the death of Flash for a long time. We know it’s coming. December 2020 has been announced as the official timeframe for removal, but let’s be real about this: it’s dead. It’s super-dead. It’s people-are-selling-Flash-game-archives-on-Steam dead.

That last bit actually makes me happy, because Flash games were a huge part of my childhood, and the archives must be preserved. Before I’d ever heard of video cards, frames per second, and “git gud”, I was whiling away many an hour on disney.com, cartoonnetwork.com, MiniClip, Kongregate, and other sites, looking for games.

I think we’ve established in my previous work that even as a missionary kid, I did not have a social life.

The Internet itself gave me a way to reach out and see beyond my house, my city, and my world, and it was wonderful. Flash was a part of that era when the Internet felt new, fresh, and loaded with potential. Flash never sent anyone abuse, or death threats. Flash was for silly animations, and games that my parent’s computer could just barely handle, after half an hour of downloading.

I even built my first animated navigation menus in Flash, because I didn’t know any better. At all. But those menus looked exactly like the ones I’d designed in Photoshop, so that’s what mattered to me, young as I was.

That was a part of Flash’s charm, really.

What Flash Got Right

Flash Brought Online Multimedia into the Mainstream

Funny story, JavaScript was only about a year old when Flash was released. While HTML5 and JS are the de-facto technologies for getting things done now, Flash was, for many, the better option at launch. JS had inconsistent support across browsers, and didn’t come with a handy application that would let you draw and animate whatever you wanted.

It was (in part) Flash that opened up a world of online business possibilities, that made people realize the Internet had potential rivalling that of television. It brought a wave of financial and social investment that wouldn’t be seen again until the advent of mainstream social networks like MySpace.

The Internet was already big business, but Flash design became an industry unto itself.

Flash Was Responsive

Yeah, Flash websites could be reliably responsive (and still fancy!) before purely HTML-based sites pulled it off. Of course, it was called by other names back then, names like “Liquid Design”, or “Flex Design”. But you could reliably build a website in Flash, and you knew it would look good on everything from 800×600 monitors, to the devastatingly huge 1024×768 screens.

You know, before those darned kids with their “wide screens” took over. Even then, Flash still looked good, even if a bunch of people suddenly had to stop making their sites with a square-ish aspect ratio.

Flash Was Browser-Agnostic

On top of being pseudo-responsive, the plugin-based Flash player was almost guaranteed to work the same in every major browser. Back in a time when Netscape and Internet Explorer didn’t have anything that remotely resembled feature parity, the ability to guarantee a consistent website experience was to be treasured. When FireFox and Chrome came out, with IE lagging further behind, that didn’t change.

While the CSS Working Group and others fought long and hard for the web to become something usable, Flash skated by on its sheer convenience. If your site was built in Flash, you didn’t have to care which browsers supported the <marquee> tag, or whatever other ill-conceived gimmick was new and trendy.

Flash Popularized Streaming Video

Remember when YouTube had a Flash-based video player? Long before YouTube, pretty much every site with video was using Flash to play videos online. It started with some sites I probably shouldn’t mention around the kids, and then everyone was doing it.

Some of my fondest memories are of watching cartoon clips as a teenager. I’d never gotten to watch Gargoyles or Batman: The Animated Series as a young kid, those experience came via the Internet, and yes… Flash. Flash video players brought me Avatar: The Last Airbender, which never ever had a live action adaptation.

Anyway, my point: Flash made online video streaming happen. If you’ve ever loved a Netflix or Prime original show (bring back The Tick!), you can thank Macromedia.

What Flash Got Wrong

Obviously, not everything was rosy and golden. If it was, we’d have never moved on to bigger, better things. Flash had problems that ultimately killed it, giving me the chance, nay, the responsibility of eulogizing one of the Internet’s most important formative technologies.

Firstly, it was buggy and insecure: This is not necessarily a deal-breaker in the tech world, and Microsoft is doing just fine, thank you. Still, as Flash matured and the code-base expanded, the bugs became more pronounced. The fact that it was prone to myriad security issues made it a hard sell to any company that wanted to make money.

Which is, you know, all of them.

Secondly, it was SEO-unfriendly: Here was a more serious problem, sales-wise. While we’re mostly past the era when everyone and their dog was running a shady SEO company, search engines are still the lifeblood of most online businesses. Having a site that Google can’t index is just a no-go. By the time Google had managed to index SWF files, it was already too late.

Thirdly, its performance steadily got worse: With an expanding set of features and code, the Flash plugin just took more and more resources to run. Pair it with Chrome during that browser’s worst RAM-devouring days, and you have a problem.

Then, while desktops were getting more and more powerful just (I assume) to keep up with Flash, Apple went and introduced the iPhone. Flash. Sucked. On. Mobile. Even the vendors that went out of their way to include a Flash implementation on their smartphones almost never did it well.

It was so much of a hassle that when Apple officially dropped Flash support, the entire world said, “Okay, yeah, that’s fair.”

Side note: Flash always sucked on Linux. I’m just saying.

Ashes to Ashes…

Flash was, for its time, a good thing for the Internet as a whole. We’ve outgrown it now, but it would be reckless of us to ignore the good things it brought to the world. Like the creativity of a million amateur animators, and especially that one cartoon called “End of Ze World”.

Goodbye Flash, you sucked. And you were great. Rest in peace. Rest in pieces. Good riddance. I’ll miss you.

 

 

Featured image via Fabio Ballasina and Daniel Korpai.

Source


Source de l’article sur Webdesignerdepot

Writing good code in accordance with all the best practices is often overrated. But is it really? Writing good and clean code is just like good habits which will come with time and practice.
We always give excuses to continue with our patent non-efficient bad code, reasons like no time for best practices, meeting the deadlines, angry boss, tired of the project, etc. Most of the time we try to procrastinate by saying will make it efficient and clean later but that time never comes.
Bad code is not problematic for us to understand but for the other developers who will handle that after us.

So, let me get you to the points by Robert C. Martin in his captivating book Clean Code.

Source de l’article sur DZone