See "Dashboard" page for updated header for Updates with sort, filter, export, etc.
Incident Profile Page:
Event Parent
Based on: .callout (class name of organism it's based on)
Class name: .event-parent (class name for element)
Elements: (data found in the)
title context - static text
title - {{parent event title}} (when talking about a variable you could wrap it in double curly brackets)
action button - link to event page
event meta data
{{zero-hour}} (name all dynamic data that is needed)
{{closed time}}
{{location}}
event related links
# incidents in event + link
# resources in event + link
# posts in event + link
event label (active)
active
inactive
(list all possible states)
Incident Profile [.profile] .incident-profile (item name [class name of base molecule] .class-name-of-this-element, this is a single line format of the above. All bullet points are elements within this element)
Incident Profile Header [.info-bar] header.incident-header (you can nest child elements using the same format)
Incident status title
active $green-name (define color names and use those to describe colors, rather than HEX, these can be described on a "general" page)
closed (if no color is defined I'll understand that as "use the molecule's default color")
flag this
icon: fa-flag
on-click: (describe interactions, I think you could nest another element under it if it pops up)
bookmark this
icon: fa-bookmark
on-click: add incident to bookmark list
share this
icon: fa-share
on-click:
share modal [.modal-share] (leave off custom class name if the element doesn't require any customization)
(the share-modal elements should be defined elsewhere)
incident-profile-summery [.summery] .incident-profile .summery (we'll have to be careful about class names so they don't conflict with foundation and jQuery UI)
title - {{incident name}}
meta
updated on {{update date}} @ {{update time}} by {{last user to update}}
tag list
incident-profile-summery-location [.panel] .incident-profile .summery .location (note the use of class names, we should be thinking very hard about our naming conventions)