Alexander

Off-topic, https://www.softaculous.com/apps/cms/ProcessWire demo is not working.

A funny personal observation: after all these years, the black ProccessWire logo on a light background looks like inverted.

The main metric for an open-source website is converting visitors into software users. However, the main issue with the open-source adoption cycle is that there is a years-long gap between users becoming aware of the project and actually starting to use it. Overall, the goal of any rebranding is to maintain recognition while solving new challenges for the brand. The level of visual identity change for ProcessWire would be acceptable in the case of rebranding when a product has totally failed, but that's definitely not the case here. This redesign will likely result in a dramatic failure of adoption for PW among new users because they will not understand that PW is something they were familiar with before. There are hundreds of CMSs and random visitors don't remember ProcessWire by name alone, and all visual branding on the new website has no brand consistency from the dozen years of the previous PW website. The new website (as commenters in other threads noticed) simply "hey what happened to my browser bookmarks, it‘s not PW." It's hard to provide suggestions without understanding what goals the new web design is solving, but I can recommend at least changing the German interface on the first screen to a screenshot with skyscrapers, because they were there all along and are strongly associated with PW even through new designs. @ryan, please don't take my word for it and instead look at the metrics. Something like PW downloads or PW module downloads per month compared with the same period in the previous year should show the real effect of this redesign. Update: there are some performance issues that result in over 200% CPU overload on the first page.

First look at ProcessWire GitHub as I remember it.

@Ivan GretskyTechnically it's a 2-digit count instead of the full 1000. Just 1k.

We all know that ProcessWire started much before all the stars hype on GitHub. Moreover, the initial repository with ProcessWire 2.0 had over 722 stars and nearly 200 forks, which means that ProcessWire reached the 1k milestone a long time ago. But as @Ivan Gretsky mentioned early "... keep the love to ProcessWire always burning deep in your heart..." And of course, the most important and valuable star for PW is always inside our hearts (even if it's not always visible on Microsoft GitHub). I would like to take this opportunity to congratulate @ryan, @adrian for initial initiative to give PW more visibility on GitHub, all contributors, and the whole community on this formal milestone and wish for decades of successful development and deployments ahead. Congratulations!

Thank you, @taotoo! <3 <3

Thank you, @thomas! <3

@Ivan Gretsky We are not affiliated, so that should be fine. However, it seems that this demand violates rule number 8 of posting, therefore we could indeed be banned. So, I will not mention all 8,370 (9,363 members minus 993 stars) members who ignore the matter that if you use someone's code and don't pay for it, you can at least star it on GitHub to help it get a better position in the rankings.

@kaspercom, @ondrejzeleny, @AMOC - guys, we are trying to get PW to 1,000 stars on Github. Are you in? https://github.com/processwire/processwire

I'm sure everyone is waiting to post the 1,000th star on ProcessWire's GitHub - don't be shy, being the 994th star is even better!

Hi there! I love ProcessWire, and whenever I see someone asking for a lightweight CMS, I always recommend it. However, ProcessWire is somehow still extremely underestimated on GitHub, 201 forks, which is really good, but only 990 stars. Let's make an effort together and bring ProcessWire to 1000 stars this weekend! Only 10 stars left. Star on Github: https://github.com/processwire/processwire More context about initial GitHub stars initiative of @adrian: Upd: 10 stars done in five hours.

@Ivan GretskyWe cannot use proprietary code in our work. In our case, we only need the ability to catch logged-in user events (hooks?) and send them via cURL to the Tirreno endpoint. As I understood the best start point is http://modules.pw from @Nico Knoll Happy New Year for you and your team, Ivan!

We had a chat a bit with @Ivan Gretsky and understood that probably I need to complete our story with more details. Unlike common images of start-ups, this is not fun at all. As mentioned, we developed this system bootstrapped for 1,000 days with a remote team of 11 (4 female, 7 male) from Ukraine, Georgia, Netherlands, Germany, Switzerland, Poland, and Thailand. My second son was born during this period, and I was literally working on this with a baby in one hand and a laptop in the other. We lost connection with our lead developer, as he was in Kharkiv (Ukraine). We haven’t had a connection with him since July, but I sincerely hope he is safe… If someone had told me that it would take 1,000 days (I had planned for three times less) and several thousand engineer hours, I probably would have never started this development, as it looked so unreal. It took approximately half the time to develop the system itself and another half to debug it to the condition it has now. Of course, during this development, we had to rewrite everything from nearly scratch several times, and it still doesn’t look perfect, but at some point, we understood that it is impossible to develop the code on our own and we need to share it with the community. The code release itself was quite a journey. Especially the last weeks, days, and, most difficult of all, the last hours. Arina (our junior lead developer) and me spent all day in a smoke-filled bar in Belgrade polishing the last version prior to release. And, of course, at the very last moment, we found a very unusual error that was extremely difficult to debug at 1AM. And at 6AM, I had to rush to the airport. There was a 37.5cl bottle of champagne for the three of us: myself, Arina and our director (photo attached), and despite popular images of startups, there was no party at all, only a pretty intensive and really hard time prior to release. So my advise for everyone whom working on large code base are following: - multiply every realistic time estimation for three; - have always backup for lead developer; - be ready to release the code better soon than later, as it will never be accomplished. I write this here now because I wish to learn this before starting this journey. Of-course I expect that there another bunch of rakes around that only waiting for it’s time P.S. If someone could share simple user tracking event module for ProcessWire that we can adopt for use with tirreno, it would be highly appreciated. I was not aware how stars are important for GitHub ranking, so would like kindly ask to put one if you see this software helpful: https://github.com/TirrenoTechnologies/tirreno

Thanks, @Ivan Gretsky. I wasn't sure whether the community guidelines allowed sharing links. There's a publicly available online demo for anyone who doesn't want to mess with the codebase themselves. Online demo: https://play.tirreno.com/ (Login: admin/tirreno) You can find Tirreno's source code on GitHub. It needs PHP 8 and PostgreSQL and should normally work after a short installation, which was also inspired by ProcessWire. Source code: https://github.com/tirrenotechnologies/tirreno/ By the way, if you see the Frogger game, something didn't go quite right! Game: https://play.tirreno.com/game/ Enjoy!