Book Image

Mastering Responsive Web Design

By : Ricardo Zea
Book Image

Mastering Responsive Web Design

By: Ricardo Zea

Overview of this book

Building powerful and accessible websites and apps using HTML5 and CSS3 is a must if we want to create memorable experiences for our users. In the ever-changing world of web design and development, being proficient in responsive web design is no longer an option: it is mandatory. Each chapter will take you one step closer to becoming an expert in RWD. Right from the start your skills will be pushed as we introduce you to the power of Sass, the CSS preprocessor, to increase the speed of writing repetitive CSS tasks. We’ll then use simple but meaningful HTML examples, and add ARIA roles to increase accessibility. We’ll also cover when desktop-first or mobile-first approaches are ideal, and strategies to implement a mobile-first approach in your HTML builds. After this we will learn how to use an easily scalable CSS grid or, if you prefer, how to use Flexbox instead. We also cover how to implement images and video in both responsive and responsible ways. Finally, we build a solid and elegant typographic scale, and make sure your messages and communications display correctly with responsive emails.
Table of Contents (16 chapters)
Mastering Responsive Web Design
About the Author
About the Reviewers

The <nav> element

As per the MDN definition:

The HTML Navigation Element (<nav>) represents a section of a page that links to other pages or to parts within the page: a section with navigation links.

Here are a few important points to remember about the <nav> element:

  • It is used to group a list or collection of links. The links can either point to external resources or to other pages within the site/app.

  • It's common practice to use an unordered list <ul> inside the <nav> element to structure the links, because it's easier to style.

  • Including a <nav> in the <header> element is also a common practice but not required.

  • Not all groups of links have to be inside a <nav> element. If we have a list of links inside a <footer> tag, then its isn't really necessary to include those links in a <nav> as well.

  • There can be more than one <nav> element in a single page, for example, a main navigation, a utility navigation, and a <footer> navigation...