Visit Lex


How to Build a Website Without Wix


When you want to get somewhere, you’re probably going to use a GPS or some other pathfinder. The same should apply to building a website for the first time. However, instead of telling you how to get there, many blog posts tell you what you need to get there. They’d list the technologies you need to know to build a website but they won’t show you the path. It’s like saying to get to Yellowstone National Park you need a car.

The purpose of this post is to show you the tools you need to build a website and how these tools will contribute to building your first website.

Let’s start off with the basics, shall we?

Text editor

text editor


Get a text editor and love it, because you’re going to be staring at it while gnashing your teeth at every new problem that arises. You can save a lot of trouble by becoming familiar with your editor’s quirks.

Sublime and Atom are the best GUI options, in my opinion. Having used Sublime, I can tell you that the customization options are seemingly endless. Give it a go.

Command line


No, hackers are not the only people who use command lines. Don’t run away from it. This black screen will become your closest virtual friend in due time.

Go through this painless tutorial here

If you don’t need any hand holding, check out this cheat sheet

Now, Let’s Learn Languages



HTML helps form the skeleton of the website. Most website consist of a navigation bar, main content area, and a footer.

Learn Page Layout:

<!Doctype html>  
    <title>MY Website</title>  
    <!  Navigation section   
      <h1>Home Page</h1>  
    <!  Main Content   
     <!  Sidebar   
     <!  Bottom   


Now you have to make these elements look presentable. This isn’t as hard as it seems. Remember that every HTML element is a potential box. Look at your favorite websites. The most common shape is a quadrilateral, or a four sided figure. All of these quads are positioned nicely using a grid system. Colors and shadows and thingamabobs are then added to create a unique user experience. This is CSS in a nutshell.

Learn about CSS selectors

Learn the Box Model

Learn about CSS Grid

Learn about Flexbox for responsiveness and positioning

If you want to do cool things, like applying shadows, just ask Google.


Before you panic, you only need to learn the essentials of JavaScript which I’ll list below.

When you click a button, an event occurs. The specific library we use to create events is called jQuery.

Learn jQuery from scratch here.

That’s all for the Front End

This is all you need to learn if you want to create a static website like a portfolio or a personal site. You can skip all of the server stuff. To host your site, you can use free hosting. One I’ve found to be user-friendly is Github Pages. Jekyll is actually a really good static site builder you can use to get started right away.

But, if you want to make the next Facebook, you need to learn the back end.

The back end: Server-side Languages

Nodejs(server-side environment for JavaScript), Ruby, Python, PHP are the four primary server-side languages used to create dynamic websites. Anything that needs to be updated on a website requires the server. A log in attempt immediately triggers an exchange of information between the client and server.

I’m not going to dive into every single language. You have to pick one. Nodejs is hot right now, so if you feel comfortable with JavaScript, go for it. Ruby is easy to use and has superb documentation. Python has similar syntax, but less support than Ruby. PHP is widely used and relatively easy to learn.

After you pick your language, you need a database. Server frameworks use databases to save, fetch, update, and delete data. Keep that in mind as you read this guide.

MongoDB, PostgreSQL, and MySQL are some of the database management systems that get thrown around every so often.

Once you’ve picked your server-side language and database, try learning:

A Server Framework

Frameworks make it easier to build web applications from scratch. Every language has its own particular framework. Mozilla breaks them down here

The MVC File Structure

If you pick a framework, this is the way you should think about web programming from now on. Of course there are other structures, but this a good one to start out with for your first project.

Model: Object Oriented Programming (OOP) in insert language

I know, I know. Wax on, wax off, right? How does OOP help? Well, in the back end, every form of data is an object. For example, every user on Medium is a user object.

In Ruby, using the Rails framework(this is a crude example), a user will look like this:

class User < ApplicationRecord
#Lot of relationships goin’ on in here. More on that later.

Controller: Restful routing

The controller is used to render HTML pages depending on the route. Within the route method, you can manipulate data from the database which would then be showed in the view.

I’ll pseudo code an example. Note that frameworks will abstract HTTP routing in their own way:

GET /users
let users = User.findAll
render the index.html.faketemplate

Routing doesn’t have to be hard at all. We usually set up routs in a route folder or an equivalent folder. The basic aspect of routs is as follows: Create, Read, Update, and Destroy. You want to create a route where something is created, like when someone creates a new account; you want a route designated to adding a user to the database. You also want a lot of Read routes where you’re getting information from a database to populate a page. You want an update route in case a user wants to edit a page. Finally, you want a destroy route in the event that someone wants to delete something.

Here’s a good post about routing:

View: Templates

Everything you learned about HTML applies, but now you can inject your server language in your HTML files to create dynamic content. If you have 10 users in your database, you can loop through all of the users we stored to the users variable in the controller and render them.

#this is just pseudo code

_{loop through users.each do}
<div class= ‘user-card’>

There are many templates to choose from. Mustache is a popular one. Check it out.

How to integrate the database

If you look up at the template pseudo example, you’ll see that each user object has accessible attributes. These attributes are defined using what’s called a schema. Essentially, a schema is a fancy word for a table of organized data.

It’s best to plan how your database should look like before creating the database with a database language like SQL. You use a relational database management system to properly make use of the language. MySQL is an example of one such framework.

You can learn how to install MySQL here:

You can learn how to use MySQL here:

Once you’re done, you can access a cheat sheet here:

If you’re using a framework, then you’ll see how the hard work of learning a framework’s nuances payoff here. When I pseudo coded User.findAll, “findAll” was an abstracted method.

The SQL equivalent would be SELECT * FROM users. “Users” is the table we would have created using a database language. Note how all tables are plural. Semantically, it’s the correct way to represent a data that will be available in multitudes.

Schemas are blueprints for SQL tables. Note that frameworks will use syntax from your chosen server-side language for table creation. Under the hood, SQL is driving everything.

Once you create a table with the aid of a framework or SQL, this table is mapped to an object. The object corresponds to the Model you create. In my case, its the User model. This is what Object Relational Mapping is all about(ORM). The relational aspect describes the relationship between objects.

Let me clarify that non definition with an example: a user can author many posts, but a post can only be authored by one user — a one-to-many relationship. This is just one of many relations that objects can have with one another.

For more examples of relations visit this link

Note: Non relational databases like MongoDB do not follow the relational paradigm per se, but if you read MongoDB’s documentation, there are ways around this restriction.

Let’s Put All Of This Together

Before you begin, wireframe your project. You should know what your site will look like and how it will function.

Once you have a wireframe, organize your schema. Both wireframe and schema will serve as a blue print for the front and back ends of your app.

1) Initialize your MVC framework.

2) Start the development server that comes with your framework.

3) Code models based on your tables.

4) Write HTML in view files.

5) Now its time to create database tables based on the schema.

6) In the controller file, use REST to create routes. Query the database if you need data and render the view pages.

7) Once your website is running and the routes are configured, start applying CSS.

8) Finally, go wild with JQuery.

One, Two, Three Lift Off!

Deploy your website to Heroku so that the world can see your hard work. To start your launch, click here.

Bonus tools

Once you’re more advanced, you should start using build systems like Webpack to package all your JavaScript files so your code runs faster.

You should also have a test suite set up; one that I’ve used for JavaScript is called Jasmine. There are different test suites for different languages. Grunt is a cool tool that can manage all of the tests you want to run. Beginning to see a pattern? There’s usually a framework for almost every level of development.

Want to be able to create CSS without having to think too hard about naming your styles? Then, use Bootsrap.

When you build a website with JavaScript, you’re going to want to use the cool features, but not all browsers support them; you’re going to want to use Babel to transpile your code back to the older version.

There are many other tools out there in the wild. But the one’s mentioned here are the barebones. Once you get your coding up to a certain level, you’re going to want to get in the habit of using production tools.

Final Words

This is a simplified overview of what goes into building a website. The point of this article was to help those who don’t have a clue as to how to get started building a website. The links provided are meant to show you a path towards success. The best way to make use of them is to go ahead and start attempting to build a website. The cheat sheets should help you if you get stuck. Plus, there’s Google.