If you have ever visited a restaurant, then you can understand how dev tools like Chrome Dev Tools and text editors like Sublime Text work.
When you are building your first website with HTML and CSS, you can easily get overwhelmed with all the new technologies that are needed to deploy even a basic site.
So, I figured a quick tutorial on using text editors and dev tools would remove one confusing part of the process.
In fact, all of this closely resembles the way that a restaurant chef might create new meals to serve to customers. Think of the concept of a recipe. A recipe is a specific set of instructions and ingredients that will produce the exact same meal over and over. As you are about to see, the process of developing a new recipe is kind of like building a website with HTML and CSS.
In order to understand this tutorial, you just need to know HTML and CSS basics. Let’s jump into it.
Comparing A Recipe and Front-End Code
Let’s think about the fundamental goal of being a chef. Your goal is to translate recipes into delicious food for customers. Of course, it becomes difficult when you consider all the factors that you need to juggle at once- incoming orders, different timings etc. But let’s forget about that for a moment.
Here is what a restaurant system might look like.
- A chef develops a recipe that will be used every single night at the restaurant. It can be replicated over and over again by the kitchen staff, and turned into the same meal every night.
- The kitchen staff follows instructions on the recipe
- The final product is the meal (looks like pasta and meatballs in this case, what kind of chef is this?)
Similarly, when you are building a website, you must write code that can be interpreted by a browser so that the exact same website can be served to visitors across the world.
- A browser interprets that code and transforms it into a GUI (graphical user interface)
- A website visitor experiences the site (google.com, for example)
Each time that you visit a particular website is called a “session“. Every time that you open up a page on a new domain (like google.com or faceook.com), a new session begins and lasts until you leave the domain. So, one person can visit multiple pages within a session. The session is kind of like the visit to a restaurant.
What are dev tools, then?
Dev tools allow you to inspect the underlying code of a website and play around with it. If you use the Chrome Web Browser, then you can use Chrome Dev Tools, for example. Just right-click anywhere on the page, and select “Inspect”, the last option on the menu.
In this case, I changed the background color of the input element to blue. Pretty boring stuff. You can go to any other website and do the same thing. Of course, the changes will never last beyond your individual session.
This is kind of like being that person on the restaurant that takes a delicious meal… and puts hot sauce on it. Becuase you love hot sauce on everything.
Your love for hot sauce will have no impact on the recipe itself. It will have no impact on the other similar meals that will be served that night. And, if you go to another restaurant, you will have to ask for hot sauce all over again.
In the same way, you can use developer tools to play with the code on another domain, but it will not have any impact beyond that particular session on that domain.
Using Dev Tools While Building Your First Website
As the chef, it’s your job to come up with recipes that will lead to food that customers love. But, you PROBABLY don’t want to figure this out by inventing a recipe, giving it to the kitchen staff, and learning later whether the customers liked it or not.
Instead, you probably want to test out a bunch of recipes in your own kitchen, and then release the one that seems to taste best.
This removes all the complexity of working with a kitchen staff and producing a high volume of food. You are acting as both the chef and the customer at once.
Notice that in this case, you have control of both the recipe and the final product. So, instead of pushing one meal out to customers, you can make part of a recipe, then combine ingredients in different ways. Then, you can adjust the recipe as you go to reflect the combinations that are working.
When you are building your first website, you should also use the original code alongside developer tools to adjust your website on your laptop or desktop.
However, as you are adjusting your browser in real-time, you probably will not want to change the “recipe”, save the file, and reload the page every single dang time. It’s exhausting. You can shorten this feedback cycle by making changes using developer tools, and then adjusting the “recipe” after you create something worth saving in the browser itself.
Remember, if you build something valuable using developer tools, but then refresh the page, your changes will be gone. Even if the file is hosted locally on your computer.
Developer Tools Only Work For Front-End
Of course, a restaurant has many processes going on at once that support the chef. There is the person that greets you at the door… the waiters… the cleanup crew… the bartender etc.
These are the people that are not involved in the translation of recipes into food… but still run the restaurant’s operations.
This is kind of like server-side code, or the back-end. Although you write server-side code with a text editor as well, you cannot make any changes via developer tools.
Why is this? Well, can you imagine if individual customers were allowed to change the rules of the restaurant like they can change their food? It would be madness! Customers can’t change the way the restaurant operates, no matter how badly they want to.
If you’d like to learn more about setting up server-side code for the first time, check out my guide to the concept of localhost.
Get The Latest Tutorials
Did you enjoy this tutorial? Sign up here to get the latest visual tutorial on web development topics.