Skip to content

Commit

Permalink
Edge is better now
Browse files Browse the repository at this point in the history
  • Loading branch information
@AndrewDonkin-Gallagher
AndrewDonkin-Gallagher committed Oct 21, 2024
1 parent 114e78b commit 0bd8c19
Show file tree
Hide file tree
Showing 6 changed files with 178 additions and 196 deletions.
73 changes: 35 additions & 38 deletions ref/cardholders.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -714,44 +714,41 @@ <h1 id="topic-Documentation-suite" data-traverse-target="topic-Documentation-sui
<div class="panel">
<div class="doc-row">
<div class="doc-copy">
<p align=center>
<img width=44 src="https://www.google.com/chrome/static/images/chrome-logo-m100.svg">
<img width=44 src="https://upload.wikimedia.org/wikipedia/commons/a/a0/Firefox_logo%2C_2019.svg">
<p>Best viewed in Chrome or Firefox. Microsoft Edge does not render the table of contents correctly in the orange column on the left, making navigation difficult.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, non-cardholder items, and bulk status monitoring</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
<p>Microsoft Edge users please note: early versions did not render the table of contents correctly in the orange column on the left, making navigation difficult. Chrome, Firefox, and recent versions of Edge work well.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, non-cardholder items, and bulk status monitoring</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
</div>
</div>
</div>
Expand Down
73 changes: 35 additions & 38 deletions ref/events.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -375,44 +375,41 @@ <h1 id="topic-Documentation-suite" data-traverse-target="topic-Documentation-sui
<div class="panel">
<div class="doc-row">
<div class="doc-copy">
<p align=center>
<img width=44 src="https://www.google.com/chrome/static/images/chrome-logo-m100.svg">
<img width=44 src="https://upload.wikimedia.org/wikipedia/commons/a/a0/Firefox_logo%2C_2019.svg">
<p>Best viewed in Chrome or Firefox. Microsoft Edge does not render the table of contents correctly in the orange column on the left, making navigation difficult.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, non-cardholder items, and bulk status monitoring</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
<p>Microsoft Edge users please note: early versions did not render the table of contents correctly in the orange column on the left, making navigation difficult. Chrome, Firefox, and recent versions of Edge work well.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, non-cardholder items, and bulk status monitoring</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
</div>
</div>
</div>
Expand Down
73 changes: 35 additions & 38 deletions ref/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -58,44 +58,41 @@ <h1 id="topic-Documentation-suite" data-traverse-target="topic-Documentation-sui
<div class="panel">
<div class="doc-row">
<div class="doc-copy">
<p align=center>
<img width=44 src="https://www.google.com/chrome/static/images/chrome-logo-m100.svg">
<img width=44 src="https://upload.wikimedia.org/wikipedia/commons/a/a0/Firefox_logo%2C_2019.svg">
<p>Best viewed in Chrome or Firefox. Microsoft Edge does not render the table of contents correctly in the orange column on the left, making navigation difficult.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, non-cardholder items, and bulk status monitoring</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
<p>Microsoft Edge users please note: early versions did not render the table of contents correctly in the orange column on the left, making navigation difficult. Chrome, Firefox, and recent versions of Edge work well.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, non-cardholder items, and bulk status monitoring</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
</div>
</div>
</div>
Expand Down
Loading

0 comments on commit 0bd8c19

Please sign in to comment.