-
Notifications
You must be signed in to change notification settings - Fork 96
01. Getting Started
This and subsquent labs will make of GitHub repos to provide starter files and guides in the Wiki (of which this is an example).
Tip
As you clone each repo it would make sense to save your own copies in a sensible file structure, with a folder/director for each week of the module.
This lab is based on the 20 HTML elements listed.
Starting with a good naming convention can also help. Generally avoiding mix cases names and working in lowercase is tidy. Also avoid the use of special characters in file and folder names. In particular don’t use white space in file or folder names as this will be translated by a browser into %20.
Most of the projects we build will include images, style sheets and scripts. It is a good practice to create folders in your site for this kind of content for example an images folder for all your JPGs, WebPs and PNGs, a scripts folder for your Javascript and a styles folder for your CSS.
As you make additions to your project you should view them in a browser. In Visual Studio code select the file in the side panel and right click to find Copy Path. You can then paste this in the address bar of your Browser.
For debugging purposes, you would be advised to open the file in Google Chrome. Chrome has a range of sophisticated tools to help in web page development - collectively these are referred to as the Chrome Console.
As you amend your HTML pages in Visual Studio Code, simply save it and then in Google Chrome refresh.
Tip
Alternatively, you may want to install the liveServer extension for Visual Studio Code to allow testing through a local development server.