#fediverse logo in #3D for later use. Yes, I know that the colors do not correspond to the original, but the pattern itself is also an unofficial proposal.
Maybe after years and a few small attempts I will check if I can handle WebGL.
@ernest I only use blender to create web assets, branding, icons, etc. I'm a rather weak artist. I planned to expand my skills with animation, but it ended on the basics from years ago. In the fall I even bought an RTX4090 for this purpose, but it is still hanging in the PC unused.
On the occasion of buying a license for Figma and putting Adobe Xd aside, I thought about creating a kbin system design ((unofficial, for testing figma and plugins).
But the post is not about that. I've been living for a while now and I still don't understand why designers stick to a full color palette. From 100 to 900 for each variant. Practice shows that no development team is able to implement it the way the ui designer dreamed. And this is regardless of the size of the company and the money spent on it. Not to mention pallet modifications.
I can't decide whether it's the designers' lack of knowledge that in ordinary SASS you can generate a practically full palette from one base color, or maybe the attitude that everything must be in line with their vision to the letter.
After all, the average user will not even notice the difference. Anyway, monitors have different settings, brightness, contrast, technology and screen quality and the effect will still differ from the designer's vision.
@cody Checkout Chakra UI we use it at work, and it's been far and away the best way to implement designs to spec from figma. Their variant and theme system is next level. We can access all those variants with just like "red.900" instead of having to use convoluted SASS functions.
@knoland I know chakra, in fact it's the same as what I'm writing about, only prepared and ready to work.
I'm not talking about the development side, but the masses of designers who spend days/months creating palettes, tints, shades. When in practice it doesn't really make sense. Whether the colors are generated in CSS, JavaScript or is a function built into a given framework is not so important. The point is not to do it manually because the marginal tonal differences in manual selection and generated shades will not be noticed by most users anyway.
However, it should be remembered that the project is being temporarily developed by one person and it is not possible to respond to everyone. For this reason, it is logical for the community to explore the proposal as broadly as possible. Validation and refinement of the topic will allow the developer to decide faster whether to implement changes and when, and shorten the implementation time.
Unfortunately, the information funnel is a matter that affects all media, the Internet, press, television, etc. Even if the operator does not block anything, a person is not able to assimilate all information. And what if we add information noise and disinformation to this.
In the case of a narrow topic such as #fediverse, there is also the issue of its low popularity. There are simply no users on the Polish #kbin instance who could at least point out the mistakes made. And since man is constantly learning, or rather should be learning, I decided to move to international waters.
In the Polish instance I was spamming as grumpydev @grumpyDev
Stumbled upon this microblog, hoping it's the right place to talk about this.
As a fan of the Tokyo Night color scheme, I spent the last couple hours making a variant of this for kbin. Would love to contribute some good ol' css to the project but I'm not familiar with all moving parts that need to be changed to add this.
For now I'll just post a preview of the style :)
This is also my first post/participation on kbin, yay!