Skip to content

feat(google-chat): init#2223

Open
thequantumquirk wants to merge 3 commits intocatppuccin:mainfrom
thequantumquirk:google-chat
Open

feat(google-chat): init#2223
thequantumquirk wants to merge 3 commits intocatppuccin:mainfrom
thequantumquirk:google-chat

Conversation

@thequantumquirk
Copy link
Copy Markdown

Website: Google Chat

URL: https://chat.google.com

Description:

Google Chat is Google's team-messaging product (web client at chat.google.com and the embedded /chat/ view in Gmail). This PR adds a Catppuccin userstyle that themes the top bar, left nav, conversation list, message bubbles, mention chips, link previews, popovers, and related surfaces by overriding Google's GM3 design tokens and the chat-specific CSS custom properties.

🗒 Checklist 🗒


  • I have read and followed Catppuccin's userstyle submission guidelines.
  • I have made a new directory underneath /styles/<name-of-website>.
    • I have ensured that the new directory is in lower-kebab-case.
    • I have named the userstyle catppuccin.user.less within the new directory.
    • I have followed the template and kept the preprocessor as LESS.
  • I have updated the userstyles.yml file with information about the new userstyle.

💬 Comments 💬

current-maintainers is left empty — happy to adopt if a maintainer handle is needed.

@WalkQuackBack
Copy link
Copy Markdown
Member

Hi, thanks for the work on this!

Sorry it's not documented better; but currently, we're moving to a unified library system for all GM3/Material 3 applications. You can see #1705 for more information.

We would want to rebase this on top of #1876. The library isn't well documented at the moment, but these open PRs may help you with the syntax of them.

Marking this as pending for now.

@WalkQuackBack WalkQuackBack added 2.status: pending Pending until internal discussion, planned updates, etc. 0.kind: init A new userstyle 4.topic: libraries Relating to the standard library and/or library modules labels Apr 20, 2026
@thequantumquirk
Copy link
Copy Markdown
Author

Hi, thanks for the work on this!

Sorry it's not documented better; but currently, we're moving to a unified library system for all GM3/Material 3 applications. You can see #1705 for more information.

We would want to rebase this on top of #1876. The library isn't well documented at the moment, but these open PRs may help you with the syntax of them.

Marking this as pending for now.

Hi, Thanks for the reply.
I noticed that the PR is still open and hasn't been updated for a while. What would be the next steps after these changes? Is it still in WIP?

@WalkQuackBack
Copy link
Copy Markdown
Member

Hi, thanks for the work on this!
Sorry it's not documented better; but currently, we're moving to a unified library system for all GM3/Material 3 applications. You can see #1705 for more information.
We would want to rebase this on top of #1876. The library isn't well documented at the moment, but these open PRs may help you with the syntax of them.
Marking this as pending for now.

Hi, Thanks for the reply. I noticed that the PR is still open and hasn't been updated for a while. What would be the next steps after these changes? Is it still in WIP?

The M3 library is finalized, but there's some blockers for libraries in general. See #1844 for where these things are being tracked.

Even though it's blocked, you can still base the userstyles on it.

Again, apologizes for the poor documentation at this stage. But you Change the base branch of this PR to feat/m3-lib in the meantime, as a start.

Also, new userstyles require maintainers; add yourself as a maintainer in the userstyles.yml.

NotebookLM shows off how the prefix system works. I would cover gm3-sys-color, gm3-color, and pkw for Google Chat, but I can do a deeper review into that later.

Let me know if you have any inquiries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

0.kind: init A new userstyle 2.status: pending Pending until internal discussion, planned updates, etc. 4.topic: libraries Relating to the standard library and/or library modules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants