Namining IDs

NOTE: IDs should be treated like variables in other languages, with regards to the naming conventions.

The value should be surrounded by double quotes (i.e. name=“value”).
For IDs, the value should start with a lowercase letter (i.e. a-z).
IDs can contain lowercase letters, uppercase letters, numbers, and some special characters (although the latter should typically be avoided).
ID’s should be explicit and clear with regard to what they are referencing.(i.e. “firstSection”, “aside-paragraph”, “hero_image”).
Try to avoid abbreviations for words in IDs (i.e. “first-paragraph” over “firPara”).
When creating IDs that are multiple words, you should follow one of three conventions. Additionally, you should follow this convention in all of your code, so that there is consistency to your work and style.
- camelCase - Camel Case pushes multiple words together into a single word, capitalizing the first letter of every word, except for the first (i.e. name="exampleValueHere")
- hyphen-separated - Each word is separated by a hyphen ( - ) character.
- underscore_separated - Each word is separated with an underscore ( _ ) character.

Why?

Hrefs reference URLs, so just like our discussion from Topic 02, you must follow naming standards to locate even portions of a page.

For example, did you notice how the URL changed in your address bar when you clicked one of the links on the previous page? Image of address bar changes