![]() * Theme: Create template part for single pledge * Plugin: Add functions for handling xprofile data * Plugin: Add helper function for getting contributor user objects * Theme: Display aggregated contributor data on single pledge view * Theme: Add functions, markup, and styles to show team badges * Theme: Add badge for Test team * Theme: Add tentative URL for report a pledge link * Theme: Add support for post thumbnails * Theme: Add org logo to single pledge view * Theme: Update `$content_width` to 960 This matches the width of the content in the global header and the About page. * Move pledge template to a file used by the template heirarchy * Clean up some PHPCS errors * Move pledge structure out to just the list items * Create file for single pledge styles * style badge grid into a grid. * Add a custom image size for the logo * Update styles * Un-hide pledges with no confirmed contributors * Fix content width |
||
---|---|---|
.. | ||
base | ||
components | ||
generic | ||
objects | ||
settings | ||
tools | ||
utilities | ||
README.md | ||
style-editor.scss | ||
style.scss |
CSS Structure
This loosely follows ITCSS.
01 Settings
Typography, colors, any spacing variables, etc should be set here.
02 Tools
This contains any mixins. We inherit the following libraries:
- breakpoint
- kube
- modular-scale
03 Generic
Any generic styles. Used for normalize & reset styles. We inherit:
- kube
- normalize
04 Base (aka Elements)
Styles for plain html elements. We inherit the base theme's styling here.
05 Objects
These are pieces of UI. These should be self-contained (or nested so that they are self-contained). Blocks should be defined here.
06 Components
This section puts together the base and objects to create pages. Page-specific styles are defined here.
07 Utilities
The is-*
/has-*
classes, these custom classes override previous styles. For example, has-background
would be
defined here. This is where block styles should live.
Editor Styles
Editor styles will use a custom import of a subset of the above folders, TBD?