Replies: 13 comments 31 replies
-
This doesn't seem like it would be beneficial to the goal of centralisation here. Would the move notice be applied by maintainers, or the staff team? Additionally, would that be placed at the top, or the bottom? (The example isn't 100% clear). How would these styles be applied, updated, etc? Similarly, how would this interact with CTP CLI and the catppuccuin.yaml stuff? |
Beta Was this translation helpful? Give feedback.
-
Hope that answers your questions! |
Beta Was this translation helpful? Give feedback.
-
https://github.com/catppuccin/cli/wiki/Contributing#what-these-points-mean The CLI would have to be adapted to search |
Beta Was this translation helpful? Give feedback.
-
|
You know, you'd think I would know these things since I added those hooks. |
Beta Was this translation helpful? Give feedback.
-
https://github.com/catppuccin/catppuccin/blob/main/resources/ports.yml |
Beta Was this translation helpful? Give feedback.
-
|
Alright, that sounds fine. If we already have the categorisation for userstyles we can think of how the CLI will interact with them in more concrete terms later on. My only concern was "this is a lot of work we'd also have to do to all our userstyle repos"! |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree with this solution as proposed in the issue I created a while ago. Solid work from staff :)) Edit: forgot to add my opinion on the question regarding the workflow. I think that the first solution (1) is the better one. It sticks to the old workflow and doesn't confuse new people. |
Beta Was this translation helpful? Give feedback.
-
|
How would this affect styles that can be used in multiple capacities? Such as the Codeberg style potentially being able to "compile" into a theme? Overall I think this is a good move, and I'm assuming the staff have taken consideration carefully, so centralizing them should be a positive thing. Ideally it also helps to keep them from going stale if more eyes see them, even in passing. |
Beta Was this translation helpful? Give feedback.
-
|
I'm totally for having catppuccin/gitea as a separate repository, so that people can use that on privately hosted instances, even when access to github.com is not available. Ideally I'd like to see userstyles/codeberg import catppuccin/gitea, then if needed apply Codeberg-only styles on top of that. Here's a stylus example where we're loading already-compiled files: |
Beta Was this translation helpful? Give feedback.
-
|
I like this idea! It seems like it would be very helpful for reducing load on maintainers and gathering the userstyles into one place. I know that I have had trouble trying to find all of the available Catppuccin userstyles in the past, just to see if there are any I would want to install, and this CAT would fix that. However, it does kind of make userstyles second-class citizens, and I feel like it might negatively impact SEO if the URL for the port is https://github.com/catppuccin/userstyles/tree/main/foo instead of just https://github.com/catppuccin/foo. To be clear, I don't think either of these objections are very important. |
Beta Was this translation helpful? Give feedback.
-
|
Okay two things at works here:
|
Beta Was this translation helpful? Give feedback.
-
|
I believe this approach is the best way forward! nice job, staff! ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
Part of unifying the styles is also trying to get a common build system for them. I'm currently looking into some ways to achieve that. |
Beta Was this translation helpful? Give feedback.
-
|
One tiny thing, I think it would be better to put all of the userstyles in a subdirectory in the repo, because the number of ports would make scrolling down to the README slightly painful 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
As far as I'm aware, the true end goal for our READMEs is actually being able to link off to our website which would contain all the information you need packaged in a much nicer way for users/maintainers. It's still a WIP so it's truly a Soon™️moment. For the short term, I think having all the important information at the top of the README would be beneficial as you wouldn't be scrolling down to see if there's any info you're missing. You'd only be scrolling down because you want to see the list of ports. |
Beta Was this translation helpful? Give feedback.
-
|
I think there's a slight misunderstanding here 😂 What I mean is that there will be so many folders in the top level repo that it will be painful to scroll down to see the actual README |
Beta Was this translation helpful? Give feedback.
-
|
maybe in a similar kind of way to how it's done in nixpkgs? |
Beta Was this translation helpful? Give feedback.
-
But doesnt the main README show without the need to manually pick it? |
Beta Was this translation helpful? Give feedback.
-
|
Ah, yup sorry! My bad. We've discussed this on the #dev chat in discord and agree that we don't want a super long README. Sub-directories sound like a simple and clean solution 👍 I think we'll want to draw inspiration from nixpkgs! |
Beta Was this translation helpful? Give feedback.
-
|
Created a skeleton repo here in the catppuccin-rfc organisation: https://github.com/catppuccin-rfc/userstyles We'll be improving it with more automation and tidying it up in the coming weeks. I'll update the RFC with the final decision in the next few weeks too! Thanks everyone again for the comments, really appreciate it ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
catppuccin/catppuccin#1940 It's already happened for the main repo, besides it'll only be a paragraph or smth |
Beta Was this translation helpful? Give feedback.
-
|
Oh no. Well, it's fine if it's just a paragraph then. 😸 |
Beta Was this translation helpful? Give feedback.
-
|
In my opinion, as long as the start of the userstyles list is within the initial page load - it's all good. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe just link to a CONTRIBUTION.md |
Beta Was this translation helpful? Give feedback.
-
|
That was the plan! Same as the main repo |
Beta Was this translation helpful? Give feedback.
-
|
Hi there! What happens to ports that are published to stores and discovery markets? |
Beta Was this translation helpful? Give feedback.
-
|
stable-diffusion-webui won't be included in the centralized repo, since it's not a stylus userstyle. |
Beta Was this translation helpful? Give feedback.
-
|
sure! |
Beta Was this translation helpful? Give feedback.
-
|
@nekowinston does the whoogle port classify as a userstyle? |
Beta Was this translation helpful? Give feedback.
-
|
@rubyowo I just had a look at it and it actually doesn't seem to be using stylus, probably worth changing the ports.yml then? |
Beta Was this translation helpful? Give feedback.
-
|
okay |
Beta Was this translation helpful? Give feedback.
-
|
@sgoudham thoughts on adding a new category to |
Beta Was this translation helpful? Give feedback.
-
|
Initial thoughts are that it feels like a slippery slope and almost seems too specific for us to change our schema entirely. I'd like to understand the rest of @catppuccin/staff's thoughts on this. |
Beta Was this translation helpful? Give feedback.
-
Progress UpdateBit of a progress update on the migration, it's going quite well I think!
Next StepsHowever, the next big decision that we need to take is defining the port workflow for someone that requests a userstyle to be made for Catppuccin. It's important to note that we don't want to make the process too convoluted and ideally, a person requesting a website to be themed shouldn't even need to understand what a "userstyle" is from Catppuccin's point of view. @backwardspy and I have discussed 2 options so far Option 1
Option 2
I'm personally okay with both options but unsure which one to commit to. Of course, We'd also like to hear about other viable approaches which might be better! Please give your thoughts below! cc: @catppuccin/staff @catppuccin/core |
Beta Was this translation helpful? Give feedback.
-
|
I would suggest option 1, as to reduce the amount of confusion within the port request process. With this option, we do not need to define new forms / processes for people to follow. This also means ports are centralised on ctp/ctp, but actual code is put in ctp/userstyles, which seems like the best logical categorisation of information. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like we're going with Option 1! Agreed with all the points you raised there |
Beta Was this translation helpful? Give feedback.
-
|
I've made a project board: https://github.com/orgs/catppuccin/projects/14 which includes all the issues that need to be completed before the repository is effectively ready. I don't really have time to work on it continuously so it'd be great if others could look at some of the issues and try to help out! |
Beta Was this translation helpful? Give feedback.
-
|
Hello again! 👋 It's been a while since the last update but I'm ecstatic to announce that repository has been transferred over to the main organisation 🎉 You can view it at https://github.com/catppuccin/userstyles. We'll now be focusing on catppuccin/catppuccin#1981 to make sure that the main repository points towards the userstyles in the central repository. @nekowinston will be helping to transfer issues from the existing repositories and archiving them. |
Beta Was this translation helpful? Give feedback.
-
|
I'm extremely happy to announce that our work on this RFC has now concluded! 🎉 🎉 🎉 I'll be updating the RFC with a little postmortem section describing what actually was implemented. Thank you to everyone that was involved in the feedback and discussions for this effort 👏 The new home for all thing userstyles is now https://github.com/catppuccin/userstyles |
Beta Was this translation helpful? Give feedback.
-
Hey everyone,
I hope you are all doing well!
We're going to be testing out a new process with RFC's with our first issue that we want to try and tackle together as a community: Userstyles!
Please read the following document: CAT-0001-Userstyles.md and leave your thoughts below, we want this to be a collaborative discussion to walk through ideas and evolve the Catppuccin project.
The short and simple proposal is listed below but please please only give your thoughts after reading the full document above! Otherwise, this process doesn't really work that well 😅
The Proposal:
We're looking forward to seeing your comments ❤️
Beta Was this translation helpful? Give feedback.
All reactions