[GH-ISSUE #1386] Allow to put css in the config file #6034

New issue

Closed

opened 2026-05-23 01:54:44 +01:00 by JakeStanger · 4 comments

JakeStanger commented

2026-05-23 01:54:44 +01:00

Owner

Originally created by @lypwig on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1386

Similarly to #1385, sometimes a small amount of css is required for a specific module and it can be convenient to put the style directly in the module:

  - type: custom
    style: |
      .item {
        background: red
      }
    bar: ...

Originally created by @lypwig on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1386 Similarly to #1385, sometimes a small amount of css is required for a specific module and it can be convenient to put the style directly in the module: ```yml - type: custom style: | .item { background: red } bar: ... ```

JakeStanger closed this issue

2026-05-23 01:54:44 +01:00

JakeStanger commented

2026-05-23 01:54:45 +01:00

Author

Owner

@imnotpoz commented on GitHub (Feb 17, 2026):

This can already be achieved in the main css file, e.g. https://github.com/JakeStanger/ironbar/wiki/battery#styling

Each module has its own class selectors you can use to theme them separately

@imnotpoz commented on GitHub (Feb 17, 2026): This can already be achieved in the main css file, e.g. https://github.com/JakeStanger/ironbar/wiki/battery#styling Each module has its own class selectors you can use to theme them separately

JakeStanger commented

2026-05-23 01:54:45 +01:00

Author

Owner

@lypwig commented on GitHub (Feb 17, 2026):

I know I can customize the modules in the css file (and I love it!). :)

This suggestion is more about putting the css directly in the config file itself, where the module is defined.

This also allows to put all the required resources in one file, which is greet to share modules (related discussion: #1384).

@lypwig commented on GitHub (Feb 17, 2026): I know I can customize the modules in the css file (and I love it!). :) This suggestion is more about putting the css directly in the config file itself, where the module is defined. This also allows to put all the required resources in one file, which is greet to share modules (related discussion: #1384).

JakeStanger commented

2026-05-23 01:54:45 +01:00

Author

Owner

@lypwig commented on GitHub (Feb 19, 2026):

I think all this stuff represents a considerable amount of work and might be out of scope of this project, sorry for the inconvenience. Feel free to reopen if necessary.

@lypwig commented on GitHub (Feb 19, 2026): I think all this stuff represents a considerable amount of work and might be out of scope of this project, sorry for the inconvenience. Feel free to reopen if necessary.

JakeStanger commented

2026-05-23 01:54:45 +01:00

Author

Owner

@JakeStanger commented on GitHub (Feb 19, 2026):

I don't want to add support for languages inside the configuration other than small script snippets. CSS files can be imported from the main stylesheet if you want a modular system.

@JakeStanger commented on GitHub (Feb 19, 2026): I don't want to add support for languages inside the configuration other than small script snippets. CSS files can be imported from the main stylesheet if you want a modular system.