[meta] Remove CSS from module CSS files that should not be there

Created on 10 September 2015, about 9 years ago
Updated 28 July 2024, 4 months ago

Problem/Motivation

Post-banana, the split between 'essential' CSS and 'nice to have CSS' is very clear through the Stark/Classy split.

Modules should only provide essential CSS that is required for functionality, we aren't consistently enforcing this right now.

Proposed resolution

Either move the CSS to Classy, or delete it if it's not necessary

Remaining tasks

Create an issue for every module/group of files the module has a lot of CSS.

User interface changes

None for Classy/Bartik/Seven. Stark will be more Stark

API changes

None

Data model changes

None

πŸ“Œ Task
Status

Closed: outdated

Version

11.0 πŸ”₯

Component
CSSΒ  β†’

Last updated about 3 hours ago

Created by

πŸ‡¬πŸ‡§United Kingdom lewisnyman Nomadic

Live updates comments and jobs are added and updated live.
  • CSS

    It involves the content or handling of Cascading Style Sheets.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024