Start With a Purpose, Not a Tool
Most first websites go wrong before any code is written, because the builder never decided what the site is for. Write down, in a sentence or two, who the site is for and what you want a visitor to do: read an article, contact you, buy something, or find your opening hours. That sentence will settle most later decisions.
Then list the pages you actually need. A small business site often needs only a home page, a page about what you offer, an about page and a contact page. A personal blog needs a home page, a list of posts and an about page. Sketching these on paper, with a rough idea of what goes on each, is enough. Resist adding pages “just in case”; a small, finished site is better than a large, half-written one.
Understand the Moving Parts
A website is a set of files (pages, images, styles) stored on a computer that is always connected to the internet and set up to hand those files to visitors. Three things make that work:
- Content and code. Pages are written in HTML, which describes the structure of the content. CSS controls how it looks, and JavaScript adds behavior such as menus or forms.
- Hosting. The computer that stores and serves your files. Basic server ideas are covered in server basics, but as a site owner you usually rent space on one rather than run it yourself.
- A domain name. The readable address (such as
example.com) that people type instead of a numeric address.
When someone enters your address, their browser asks the Domain Name System to translate it into the numeric address of your host, a process described in more detail under DNS lookups. The browser then requests the page from that host and displays what comes back.
Choose How You Will Build It
There are three common approaches, and none is universally best.
Hand-written pages. You write HTML and CSS yourself. This teaches the most and produces very small, fast pages, but it becomes tedious once you have many pages that share the same header and footer.
A website builder. A hosted service lets you drag and drop elements and publishes the result for you. It is the quickest route for a simple site, but you are tied to that service’s features and pricing, and moving away later can be awkward.
A content management system or static site generator. A content management system stores your pages in a database and lets you edit them in a browser. A static site generator turns plain text files and templates into ready-made pages. Both separate content from design, which makes growth easier, though they come with more to learn and maintain.
For a first site with a handful of pages, a builder or a simple generator is usually a reasonable choice. If you want to learn how the web works, hand-writing a small site first is worthwhile.
Pick and Register a Domain
A good domain is short, easy to say aloud, and easy to spell. Avoid hyphens and unusual spellings if you can, since people will mistype them. Check that the name is not too close to an existing business, and consider whether the name will still make sense if your focus changes.
You register a domain through a registrar, usually for a yearly fee that varies by extension (the part after the dot). Be aware of renewal: if you forget to renew, the name can eventually be released for others to register. Turning on automatic renewal and keeping a working contact email on the account helps prevent that. Many registrars offer to hide your personal contact details from public records; this is worth considering.
Choose Hosting
Hosting comes in a few broad forms. Shared hosting places many small sites on one server and is inexpensive and adequate for modest traffic. Virtual private servers give you more control and more responsibility. Managed hosting handles updates and maintenance for you. Static hosting serves pre-built files and is often simple and cheap for sites made with a generator.
When comparing options, look at what is included (storage, email, a free security certificate), how backups work, what support is offered, and how easily you can upgrade. If you run your own server, you also take on patch management, keeping the software up to date, which is easy to neglect.
Build the Pages
Whatever tool you use, work in this order:
- Set up a shared layout. Decide the header, navigation and footer once, so every page matches.
- Write the content first. Clear headings and short paragraphs matter more than decoration. Each page should have one main idea and a descriptive title.
- Add images with care. Compress them so they load quickly, and give each a short text description for people using screen readers.
- Make navigation obvious. A visitor should reach any page in a click or two from the home page.
- Add a way to get in touch. A visible email address or a simple form is enough.
Keep your files organized from the start, with a consistent naming scheme and one folder for images. As the site grows, version control lets you record changes and undo mistakes, and it is useful even for a solo project.
Look After Security Basics
A small site is still a target for automated attacks. A few habits go a long way, though none is a guarantee:
- Serve the site over HTTPS so traffic between the visitor and the site is protected by data encryption.
- Use strong passwords that are unique to each account, and consider a password manager to keep track of them.
- Turn on multi-factor authentication for your hosting, registrar and site editor accounts.
- Keep any software, themes and plugins updated, and remove ones you no longer use.
- Keep a backup strategy that stores copies somewhere other than the host itself.
Test Before You Launch
Open every page on a phone, a tablet and a computer, and in more than one browser. Click every link and submit every form. Check that images load, that text is readable without zooming, and that the site works reasonably on a slow connection. Ask one or two people who did not build the site to find a specific piece of information; where they get stuck shows where the layout needs work.
Also check the basics that affect how people find the site: each page needs a unique, descriptive title and a short description, and the site should have a sensible address structure. Search engines may take days or weeks to notice a new site, and results are never guaranteed.
Launch and Keep Going
Launching usually means pointing your domain at your host, uploading or publishing the files, and confirming the live address loads correctly with HTTPS. Allow some time for the change to spread, since DNS updates can take from minutes to a day or more.
After launch, the work shifts to upkeep. Review the site every few months for broken links and outdated information, renew the domain and hosting on time, and update the content that matters most. If you want visitors, share the site where your audience already is; basic digital marketing ideas such as consistent posting and clear calls to action may help, but growth is typically gradual. A simple, accurate, maintained site is a good result for a first project.