Back in the 90s and into the 2000s, rendering inconsistencies between

browsers meant that tables were a good option for web page layout.

People would create a table, and then would create cells

to place all of their text and images on the page.

This worked pretty well at the time because, CSS was still maturing

and there weren't too many other great ways to get an exact look.

However, browsers have improved a lot and those days are long behind us.

So, you should never use tables for layout in a web browser.

In other words, tables should only be used for displaying tabular data.

And not for positioning images and text, because that can now be done with CSS.

There is one major exception to this.

In HTML emails, tables are still used for layout.

Because rendering and consistencies, still persists.

The table that we made is not very interactive,

so here are two challenges for you to consider.

If you continue to learn about front end

development, try adding some jQuery to your table.

With the right plug-in, you can add features

like sorting and filtering to an otherwise static table.

If you learn about back end languages, like Ruby, PHP, or

Python, try to see if you can populate a table dynamically.

By using data from a database.

Databases store information in a table structure.

So it's very normal to see data from a

database, rendered in the form of an HTML table.

This is common in website administration interfaces,

where you need to manage all of

your data without writing database queries every time you want to make a change.

That about wraps things up for HTML tables.

If there's one thing that you take away from

this, remember that tables are used for tabular data.