refactor(css): Cleaned up stylesheets

[crptk]

Summary

Splits the ~34,000 lines of CSS in static/styles.css into multiple smaller stylesheets organized by purpose under a new static/css/ directory.

An index.css file imports all stylesheets and serves as the single entry point.

It's important to note that no CSS has been changed, simply reorganizedand refactored into their own files. No UI changes are intended with this PR. The goal is to make the CSS easier to navigate and maintain, since working with a single 34k-line stylesheet has become increasingly difficult. The CSS itself could still benefit from further cleanup, but organizing it into smaller, purpose-based stylesheets should make future improvements much easier.

The new organization has been split like so:

static/css
|-- base/
|   |-- reset-and-typography.css (289 lines)
|   |-- tokens.css (91 lines)
|-- layout/
|   |-- shell-and-windows.css (6366 lines)
|-- components/
|   |-- forms-and-buttons.css (699 lines)
|   |-- modals-and-popovers.css (2020 lines)
|-- features/
|   |-- calendar.css (2965 lines)
|   |-- chat.css (766 lines)
|   |-- cookbook-and-models.css (3621 lines)
|   |-- documents.css (3504 lines)
|   |-- email.css (2281 lines)
|   |-- gallery-and-editor.css (6338 lines)
|   |-- notes.css (3596 lines)
|   |-- settings-and-admin.css (2510 lines)
|-- utilities/
|   |-- helpers-and-overrides.css (3322 lines)
|-- index.css (18 lines)

Target branch

• This PR targets dev, not main. All PRs land in dev; main is curated by the maintainer at each release. If your PR is on main by accident, click "Edit" on this PR and change the base.

Linked Issue

Fixes #2617

Type of Change

• Bug fix (non-breaking — fixes a confirmed issue)
• New feature (non-breaking — adds new behaviour)
• Breaking change (changes or removes existing behaviour)
• Refactor / cleanup (behaviour unchanged)
• Documentation only
• CI / tooling / configuration

Checklist

• I searched open issues and open PRs — this is not a duplicate.
• This PR targets dev
• My changes are limited to the scope described above — no unrelated refactors or whitespace changes mixed in.
• I actually ran the app (docker compose up or uvicorn app:app) and verified the change works end-to-end. Type-checks and unit tests are not enough.

How to Test

1. Run docker compose up -d --build
2. Open http://localhost:7000
3. Double check that no UI has been changed and it remains responsive.

Visual / UI changes — REQUIRED if you touched anything that renders

Anything that changes what the UI looks like — buttons, icons, padding, colors, fonts, spacing, layout, CSS, HTML, SVG, or any static/js/ module that draws to the DOM — needs all of the following. PRs that change rendering without these WILL be closed.

• Screenshot or short clip of the change in the running app, attached below. Mobile screenshot too if the change affects mobile.
• Style match: the change uses Odysseus's existing visual language. Specifically:
  • Reuse existing CSS variables (--red, --fg, --bg, --card, --border, etc.) — do not introduce new color values, font sizes, or spacing units.
  • Reuse existing button/input/card/border classes. Don't invent parallel styling.
  • No Unicode emoji in UI or code. Use inline SVG (matching the monochrome icon style already in static/index.html) or plain text.
  • Monospaced font (Fira Code) for primary UI text. Don't override.
  • Dark theme is the default; any light-mode work must be wired through the existing theme system, not hard-coded.
• No new component patterns. If a similar widget already exists in the app, extend it instead of writing a parallel one.
• I am not an LLM agent submitting a bulk PR. If you are, please open an issue describing the problem first — bulk auto-generated PRs that don't match the project's visual style are closed on sight, even when the underlying fix is correct.

Screenshots / clips

https://streamable.com/0zkqow

[pirren]

(Not a maintainer)

I came here looking for an issue like this or I would have opened one myself. I'm happy to take a closer look later and give my five cents👋

[alteixeira20]

Thanks for continuing to work on this. I agree with using #2617 as the canonical CSS maintainability tracker, but this PR is not safe to merge in its current form.

Requesting changes because the current head is still not a behavior-preserving CSS extraction.

The merge from current dev resolved the previous freshness problem, but it updated static/style.css by 902 additions and 33 deletions without updating any of the extracted static/css/** files. The new CSS entry point is therefore already stale.

The imported bundle also is not equivalent to the original stylesheet. It has additional and missing declaration occurrences, duplicated reset/token sections, and 162 keyframe definitions versus 142 in static/style.css. That can change cascade, reset, token, and animation behavior.

There is also an offline-cache issue: index.html now loads /static/css/index.css, which imports 14 stylesheets, but static/sw.js still precaches only /static/style.css. The old stylesheet also remains in the repository.

Please rework this as a strictly mechanical, order-preserving split from the current dev stylesheet:

• preserve declaration content and cascade order;
• remove unintended duplication;
• demonstrate exact declaration/order parity;
• decide and document whether the old stylesheet should be removed;
• update the service-worker precache for the actual CSS dependency graph;
• provide durable desktop/mobile, dark/light, density, modal, hard-reload, and offline validation evidence.

Separately, the Conventional Commit title check is currently failing.

Token redesign, reset cleanup, visual changes, and broad deduplication should stay out of this initial extraction and be handled separately after a validated modular baseline exists.

[crptk]

Appreciate the reviews! I've read anything and I'll make the following changes:

1. Pull from remote dev to resolve conflicts and keep the PR up-to-date with the code changes
2. Manually look through every CSS file to remove duplicated sections that Claude made when helping me refactor
3. Compare the old universal style.css to the new changes I made to fix and preserve cascade order
4. Rigorously test the new CSS changes on every page with every theme and record it, and put all the recordings in a CSV file with all the different test cases so you can skim through them to verify everything works
5. Will remove styles.css since if this is this refactor goes through cleanly, there shouldn't be any need to keep it anymore as the new stylesheet structure will be the baseline for any future frontend changes. Future developers (or AI) might be confused by its presence as well which might result in unintentional UI changes

This may take me a while, I estimate by the end of next week since I'm quite busy at the moment, I hope this can be my first major repo PR merge in my career though :)

[crptk]

Finished adding the fixes, sorry it took me a while!

• Went through every file to remove duplicate references
• Went through (hopefully) every stylesheet that I made and compared it to the cascade order in styles.css to match
• Updated service worker precache in sw.js to reference the new stylesheets
• Updated all CSS references in relevant python tests to use the new stylesheets instead of the old one

Here is a video showcasing in detail the CSS ui that remains unchanged, in the video i restart the docker container entirely, showing that the CSS refactor is in place in VS code (correct branch + changes), then go through each UI screen and showing that the UI behaviour remains unchanged: https://youtu.be/FWFtUtlOyEo

I've removed styles.css accordingly as well

Let me know if there's any further changes to be made

[entitycs]

I need a notification the second this is mergeable. :)

[crptk]

@entitycs this should be mergeable now, I pulled from origin dev branch and adapted all new styles to updated stylesheet, preserved cascading order, and resolved any conflicts. Functionality is maintained of course since I haven't touched any files outside of the stylesheets and files that import them.

Here's an updated demo of the CSS maintained:
https://youtu.be/ILYOk7gmgX8

let me know if this is all good

[entitycs]

@crptk so far so good on my end. I'm battling some other conflicts (eg. emails) so I am not able to test everything yet.

edit: It looks to be a little behind - a lot of recent changes got pushed apparently, but no biggie. You've designed it to make it easy to re-diff and re-parse out, so I'm doing just that to get the latest changes in.

One pointed question though: Did you use 2-space tabs - or is that an artifact of something I did on my end? I only ask because the original diff I tried exploded in whitespace changes (the repo desperately needs a linting pass + config).

notes as I merge changes:

• .mermaid-container is defined twice, throwing off the diff tool's ability to show 'moved' sections.
• .doc-version-diff - your version uses params, --green and --red - the repo currently shows a tan and blue with transparency. I like your version here, instinctively, but I'm going to go ahead and treat it as a pure refactor, then give it a lookover.

original

Everything I can see - login/logout, chat, most modules, the background effects... all working as expected. Backend-driven tests pass.

All existing & new tests related to css are passing for me. Though, I'm moving some tests from the style of 'loading node through python' into actual frontend tests (unit, and end-to-end w/ playwright). So I may have some overlap there, and would have replaced those existing tests.

Eventually, in my svelte branch, every component/page will have its own style block

<script>/* scripts */</script>

<div>/* html elements */</div>

<style>/* applicable styles */</style>

Not having to pick from a 40K line file will make this much more manageable down the road. A big thanks for cutting that down.

[crptk]

@entitycs Thanks! Glad this PR helps, I was somewhat surprised that nobody has made a PR about this earlier and I'm glad I was able to kick it off.

About the whitespace issues, I believe it may be on my end. If you'd like I can fix it no worries! I'm just not sure if you already made changes to it and if I make a new commit it might produce more merge conflicts on your end

[entitycs]

@crptk don't worry about me. It's better handled by you, ofc, but additionally, because I know I made some personalized changes in style.css itself that could potentially pop up otherwise.

Still, I'm just about done making the git difftool see the changes correctly (ie. make edits such that it can graph out the moved sections correctly). Out of the 40k lines or whatever it is, at least on my VSCode install, it gets confused between handfuls (or dozens) of identical batches of lines.

If you want to compare, as patches against dev, I'm up to do that; otherwise, don't let me stop you :)