further standardize key views
Ticket
further standardize key views+status
further standardize key views+priority
further standardize key views+tag
further standardize key views+commit
further standardize key views+issues
.content is always in body div, meaning it often wraps stuff that is not, strictly speaking, card content.
the class "content" has a poor name, likely to conflict with other systems
in content view, there are two nested divs that are basically redundant. to style content inline, both must be altered.
further standardize key views+solution
image in +discussion outlines changes:
- rename .content to .card-content for consistency
- use just one div to wrap content in content view
- get rid of view-specific content classes (eg .titled-content), because content has a consistent relationship to view and can be specified in other ways (eg .titled-view > .content)
- only add .card-content to card-body when it actually contains card content and only card content ( not in denial, options, etc)
- add set classes wherever there is content, so that standard selector pattern for content becomes, eg, .SELF-menu.content