Avatars display profile photos and information relevant to the avatar's context.
user_helper.rb
for more info. The following are the most common implementations.
Masonry cards are used to feature content across the site.
Masonry cards should always be setup on a grid. By default, each card will occupy 4 columns, except for Featured cards - which will occupy 8 columns.
When the
.grid__row
also contains a class of
.masonry
, the cards will be vertically positioned by our masonry library.
There is a helper method available for each card type in
card_helper.rb
.
Typically, you will only need to provide the object or page location that each card represents.
Comment / Reply counts will be displayed if the object has that association.
Discussion cards will always have a transparent footer area. Only cards for objects with featured images will have an image.
The following represent a sampling of cards for each type of object.
Only objects with featured images may be used for featured dynamic cards.
Thumbs are used to display Downloads and E-Learning Examples on listing pages. Thumbs should be used within a grid.
This is how jobs will appear in the job center.
Each of the core Heroes data types can be injected into the search result template.
Each of the core Heroes data types can be injected into the bookmark template.
Each of the core Heroes data types can be injected into the contribution template.
Flash messages should appear upon page load, fixed to the lower right side of the page. They are set to fade out after 8 seconds.
All images are constrained by width, but not by height.
This is to ensure that we can use CSS to fill the image space with the image, via
background-image
and
background-size
, without having to use massive image files and hopefully avoiding pixelation.
Authors have been provided the below optimal image dimensions and are expected to upload only images with those dimensions.