Creating Your Own Website, Even if You’re a Tech Noob!

For a lot of people who aren’t really tech-savvy, creating their own website is a bit of a daunting idea. While GoDaddy and other vendors show alluring prices of $6-20 to register a domain name of your choosing, is that all you really need for a website? What’s actually involved with doing this?

Let’s step through the components of getting your own website booked and hosted, and also how to build it. Again, while having tech expertise helps, you need almost no tech experience to create a website.

As a disclaimer, this article is mostly directed to an audience with little to no technical background; people who are just starting to consider the idea of getting their first website.

Pieces Involved

There’s a few components you’ll need to get your website off the ground. They are:

  1. A domain name (, for example)
  2. A DNS server supplier
  3. A website hosting provider
  4. A way to build your website code

Step 1 – Booking Your Domain Name

​Let’s start with getting a domain name. There’s a plethora of registrars on the Internet to register domains through. I’ve used GoDaddy, OpenSRS, DynDNS, and Enom before, and all of them work pretty well for booking a domain for less than $20/year. Usually it’s a just a matter of going to your vendor’s homepage and searching to see if the domain you want is available, then registering it.

When you use a registrar to book a domain, you’re essentially paying the people who manage name registration for the Internet for the rights to your domain name. Note that you’re only paying for the rights to the name, and nothing else. The domain name is useless in itself unless you have DNS and something, such as a web server, to point the domain to.

Now, a common misconception at this point is that all domains can be booked for under $20. This isn’t exactly the case. Domains are divided into two groups known as regular domains and premium domains. Regular domains are your run-of-the-mill $20/year domain, and are categorized the way they are because they aren’t an incredibly high-profile name for whatever reason ( is a regular domain). Premium domains usually have short names, and you can immediately tell them apart because of the price to book them; this is usually in the thousands of dollars ( is a premium domain, for example).

Another noteworthy point is that a large number of domain registrars will also give you the option to use them as your DNS server supplier as well, and may offer a price discount if you choose to do DNS with them if you’re already using their domain name registration. I’ll describe this a little more in Step 2, but this is usually the route you want to go down if you don’t already have another dedicated vendor for DNS.

Once you’ve registered your domain, you’ll be asked to provide administration and technical contact information for the domain. Use either yours or your company’s contact details for this, and make sure they’re correct. This information is used to show to the world who owns this domain.

Step 2 – Setting Up DNS Servers

DNS stands for “Domain Name Service”. The reason it’s necessary is that computers and servers don’t communicate with each other on networks and the Internet through easily-read names, such as “”. They communicate using something called an “IP Address”, which looks like this:


Computers have to use IP addresses to communicate due to the way that traffic is routed and categorized on the Internet. Using a human-readable name to direct traffic on a computer’s circuitry level would be a nightmare from a technical standpoint!

Now, you might be thinking “then how does the Internet work, since it clearly does use human-readable names for servers?”. Great question! This is where DNS comes into play. A DNS server takes a computer’s IP address, and ties it to a record entry for a human-readable name. So, I don’t have to go to in my web browser! I can instead type in, and my computer will query the DNS server for my domain and ask it what IP address the web server for my domain name has! My computer then goes to that server based on it’s IP address, and voila! My website appears!

As I mentioned it Step 1, it’s usually easiest to use the same vendor as your domain registration for your DNS as well. They usually offer a price cut to do this, and often set your domain name up to point to their DNS servers by default. Since each vendor does this a little differently, you might have to contact their technicial support staff to find out how to point your newly-acquired domain name to your DNS servers. Tech support can also help answer any questions you have regarding this. I can offer assistance as well (see my contact page).

Step 3 – Choosing A Website Hosting Provider

One of the great things about using GoDaddy or some of the other big-name vendors for Steps 1 and 2 is that they offer competitively-priced web hosting packages as well! You also have the option of finding another web host vendor, such as Bluehost, that does independent web hosting, although it’s convenient for you to pick a vendor from the start that can do Steps 1 – 3 all themselves.

To offer some clarification, a website hosting provider is the one that gives you access to a web server on which to store your website content.

I use Weebly personally for my site; one of the nice things about Weebly and Wix, for example, is that they also have integrated tools for designing a website as part of your web hosting package. This makes it really easy to set up your site even if you have zero programming experience! Squarespace and VistaPrint are also a few other vendors that have similar web hosting/design packages. If you’re not very technical and aren’t sure what to do, this is usually the route you want to go down.

You can design your website with these vendors, then take it live once you’ve finished building it, eliminating the need for Step 4. If you’re more code-savvy and want some of the really nice features that the tools in Weebly and Squarespace can’t give you, then you’ll need to buy separate tools, which I’ll touch on in Step 4.

Step 4 – Designing Your Website

If you don’t want to use the built-in tools that come with some of the hosting vendors mentioned in Step 3, you’ll want to explore the option of manually coding the site in the programming language of your choice. Other options include purchasing a Web Design Suite software package, such as Adobe’s Dreamweaver. Dreamweaver gives you some really powerful options for designing sites in a graphic interface instead of a coded command line, although it’s not recommended for the faint of heart (it takes a lot of training to master it). You’ll also need FTP credentials for the server, and possible access to a MySQL database backend.

You also have the option of using a website “skeleton” for designing the site. WordPress, Joomla, and Magento are some options that let you build a website for free that’s virtually fine-tunable up into the sky. They do require a much steeper technical learning curve to use. I’d actually recommend against using this method, as an engineer that has dealt with hundreds of security problems with these frameworks over the years (they’re much easier to hack into). I mention it because a large number of web developers still favor designing websites using this method.

If you’re just starting out with a website, and aren’t too computer-savvy, then skip this step altogether. Seriously! Just go with a vendor like Weebly which lets you build a site using easy-to-use tools, and is pretty secure at the end of the day.

You’ve Got Your Tools, Now to Take the Site Live!

Let’s say you’ve got your domain, DNS servers, and website/design package booked. What now? Well, you’ll need to build the site, and then start preparing to unveil it to the world!

What’s involved in this is working with your hosting vendor and making sure the site is completely ready to go live (sometimes additional billing aspects come into play in this regard, so talk to your hosting vendor if you’re not sure). You’ll then need to “point” your DNS servers to the server that your website is going to be hosted on; again, the hosting vendor will provide you with the IP address for the server to use.

Once you have your IP address, you have to point the ‘www’ and ‘@’ records of your DNS server to the web hosting server. Different vendors do this in different ways, so consult with them if it’s not apparently obvious as to how you can make this change. The change may take up to 24 hours to propagate around the world after it’s made.

​That’s about all you’ll need to do, give or take a few minor details. Questions or comments? I’d love to hear them!

Caleb Huggenberger is a 31 year-old systems engineer, old-school guitar and amplifier builder, and Eastern culture enthusiast. Outside of long work days, he enjoys electronics engineering, cast iron campfire cooking, and homesteading on his acreage in the Indiana countryside.

Leave A Comment (please keep things clean & civil)

Your email address will not be published. Required fields are marked *