Tables
Most users no longer have the ability to create tables in Omni CMS. This information is provided as a reference for users editing existing tables as well as those who are tasked with creating new tables. For help creating a new table or editing an existing one, please contact an Omni CMS administrator.
Use tables only to contain data. The markup for a table creates specific relationships between the data and the table's headings, which is usually not valid when the table is used for content layout. For content layout, use the components and snippets provided by the site's templates.
Creating all of the relationships within a data table properly can require a lot of extra work, but the WYSIWYG does provide the necessary options to make most tables accessible. The following are the properties which will be used to specify table relationships:
- Table Properties:
- Show Caption: This provides the option to specify a caption for the table, which is usually recommended.
- Class: A CSS class may be specified to provide styling for the table.
- Row Properties:
- Row Type: Body, Header, or Footer. Most tables will have a header row across the top for the column headings, followed by any number of Body rows. Footer rows are a little less common, but the row type should be specified when a footer row is used.
- Class: A CSS class may be specified to provide styling for the row.
- Cell Properties:
- Cell Type: Cell or Header Cell. All cells in a Header Row usually should be specified as Header Cells, as well. If a table has headings for each row, they should also be specified as Header Cells.
- Scope: If the cell is a Header Cell, the scope should also be specified, indicating whether it is the header for a Row, Column, Row Group, or Column Group.
- Class: A CSS class may be specified to provide styling for the cell.
While the table, row, and cell each provide an option to specify a CSS class, it is recommended to only apply a class to the table and use the relationships to specify the appearance of the rows and cells in the CSS.
Do not use the other properties provided in the WYSIWYG to specify the appearance of the table and its rows/cells (e.g. width, height, alignment, spacing, padding, and borders), as the appearance should be specified in CSS based on the classes applied to the table/rows/cells and must account for accessibility, usability, and responsive functionality.
