...of course, we might need to edit that Coding Standards page; some of the rules seem a little too OCD, imo.

But we should definitely stick to the rules of writing valid CSS (as far as is possible), putting selectors on their own line (except in the case of things like h1, h2, h3, h4, etc.), and proper property spacing.

Basically - we should check all the included core .css styles to see if any are non-compliant, and make them so, editing the Coding Standards page to make it more relevant, if need be.

Comments

effulgentsia’s picture

effulgentsia commented
Status: Active » Closed (fixed)

Closing this issue for lack of attention. If you find any specific bugs, please open an issue for them. Or, if you're intending to do a general sweep, please re-open this issue and assign it to yourself.

geerlingguy’s picture

geerlingguy commented
Version: 7.x-dev » 8.x-dev
Status: Closed (fixed) » Active

This issue was created during the radical tpl refresh for Drupal 7. One of the things that we started to get into, but never really finished, was the organization and structuring of the CSS, and finalizing a set of true CSS standards. I'd rather leave this issue open for the time being, as we should try to keep our design code as meticulous as our programming code.

ilsoda’s picture

ilsoda commented

How to style the wp_list_pages(); and make the title not to show on the front-end

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Status: Active » Closed (duplicate)

This issue doesn't have a clear strategy for completion. Closing it in favor of #1891580: [policy] Finally agree on CSS coding standards and #1921610: [Meta] Architect our CSS