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.
@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.
@cutitdown The matter is a bit simpler. I noticed Ernest's posts on another site and I looked at "karab.in" from time to time and followed the changes out of curiosity. Ernest did all the work himself, and while this has its advantages, it also has serious limitations, to help him a bit I made a logo for the site and some UI mockups.
Yes, I can see the issues you've been writing about for a long time, but they are code issues. It actually takes a few lines of CSS to fix it, but here's Ernest's time issue again. Also, almost no developer likes to bother with CSS.
The solution is to push the patches into the repo and then harass Ernest to accept them.
@kris Upvotes and downvotes work and do the job, the problem is that they require a disciplined community and admins.
If the ratings do not affect the real ranking, users do not see the point in it, they get irritated and the service slowly but surely dies. It happened with digg, it's happening with its Polish clone, wykop.pl, and it's happened with several other counterparts.
Unfortunately, the natural course of things. The site becomes popular, money begins to appear, this affects the ranking through sponsored content and begins a slow decline.
upvote/downvote meets the needs you write about. If it works as it should. It is less important whether it will be an arrow, stars, hearts or any other object used to illustrate the functionality.
Though maybe thumbs up/down would be a better choice than arrows.
@garrettw87 Yes, detailed information would be visible in the "activity" tab or better "stats". In fact, this feature already exists.
In this example, it's not even about combining top-ups with likes, etc., it's about unifying the user interface. Instead of buttons on the left in threads, on the right in microblogs, etc., it's the same everywhere.
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.
Curious if anyone here knows why PHP was chosen for kbin's implementation? I know PHP has come a long way, but there's still a lot of uncertainty / dislike for it out there. @ernest might just really like PHP, which is totally cool, but as someone who would like to contribute, but also as someone who hasn't touched PHP in almost 10 years, I'm genuinely curious!
@rodhlann I wonder why people think that the choice of programming language is an indicator of the quality and success of a project. It's as if #rust or some other currently trendy solution automatically solves any problems.
BitBag acquired Sylius a few days ago, so maybe development will speed up a bit.
I'm not sure I understand why "Threads" and "Microblogs" are separate entities in kbin. From my understanding, "Threads" are like Reddit's link/image posts and "Microblogs" are like text posts. Why are these only viewable in separate tabs? It seems like a bad thing to completely separate certain content from the same Magazine and make it unable to view everything at once. Am I misunderstanding something?
Microblog = smaller posts, on any topic and seriousness.
Threads - articles, more meaningful entries, longer posts. Where the OP usually expects extensive interaction with other users
For example, your post is a short question. You should get an answer and that closes the topic. In threads in this case, there should be a description of the problem, ideas for a solution, information on what causes what, etc. Or a link to such content.
@Pietson Yes, a microblog is something between a chat and normal entries. In short, it's built-in Twitter/Mastodon, which in this case is not the main and practically the only functionality.
What is important, or rather the most important in this type of threads (UI/UX) is a matter of time. The project is developed by one man/programmer who is both backend and frontend developer, DevOPS, CEO, CIO, CMO, helpdesk, etc. :) And the project itself, despite the rapid increase in popularity, is in the alpha phase.
For this reason, it is natural for minor and major ailments to be visible. Also conceptual. Also remember that kbin is not reddit, mastodon, twitter, lemmy or any other 1:1 platform. This project should not be considered as an attempt to copy. In which direction the development will go, I don't know.
Slowly but forward. Main pages with no content, but they are there. Blog without pagination, but it works. Currently, the font jumping on swap annoys me the most.
@ernest After the mechanics, RWD and content, it would be good to visually diversify the home page a bit, but we'll see how with time. Parallax in the hero/header section is a few minutes of work, but taking the time for more interesting animations can be problematic.
Font Awesome vs Feather Icons. CC BY 4.0 vs. MIT. Pack of 2020 icons vs 287. Despite the advantage expressed in numbers, I do not have feelings for Font Awesome. What's better? Or maybe looking at things like icons is just a designer's whim? #kbin#ui
@odddev Thanks. I know Tabler but completely forgot about it, and most of the listings now refer to icon search engines, icon selling platforms, not icon families. I guess I need to do some research after years and refresh this topic.
#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.
The first approach to "warehouses", channels, rooms. Personally, I don't like the solutions seen on #reddit, but people seem to like them. And yet, the user interface is for people, not for themselves. At least to a large extent.
While reddit's layout isn't fully polished (many subreddit-related modules and pages still use the old layout), I decided to use a drop-down menu that I don't like and redesign it a bit.
@narF The letter "M" visible in the kbin address is the first letter of the word "magazyn", which in English translation is equal to the aforementioned "warehouse". Meanwhile, "magazine" in Polish is "czasopismo".
@Kierunkowy74 There may also be a "periodyk". Either way, it doesn't change much. The problem is that "magazine" is an unfortunate term for English-speaking users, and changing this element would be quite painful now.
Although it's better to change it sooner rather than later. On the other hand, this is a side issue that the creator can skip. A possible workaround is to change the text value, leaving the "mechanics" unchanged, in short leave the subkbin address with /m regardless of the translation.