Leaderboard

What will happen to developer directory?https://directory.processwire.com/ It is not mentioned anymore on the website but you can still find it on Google. You cannot login anymore. At this point I think it should either be deleted or relaunched. 😆 Regards, Andreas

Hi @cwsoft, thanks for your questions and your help. You are right, I should no longer worry about the database as long as the rsult fits. At the moment I am working with a local copy of the site in order not to publish half-finished results. I implemented variable sorting (by name, date or newest first) by visitor, and had some problems finding the right conditions, especially with the reverse part. The result I found looks a bit crazy, but it works. So I think, we can close this topic here.

And a JS error is preventing anyone from showing on the map.

Rather late to the party, but congratulations to everybody involved on the website redesign! It's turned out really well. Such a clear and fun design for a CMS, I like it better with every minute. One thing that doesn't quite work yet (I think) are the admin screenshots on the homepage. These could be much more lively and colorful. As in: examples of working with images and other multimedia content in the backend. Sure, the tables and custom fields are important, the search, filter, etc. But it's all rather dry. And I kind of miss the skyscrapers, they lent themselves to integrating images easily. Or maybe it's time for trees or birds. As someone said before, keeping the skyscrapers comes with some free brand recognition. I agree that not of all the animations make actual sense or match the text beside them, but that's... okay? They're fun to look at, and the text is large and easy to read.

First of all, hats off to everyone involved in the redesign! I can only imagine the countless hours that must have gone into this project – really impressive work. Of course, a redesign will always divide opinions. Some will love it, some won’t – that’s the nature of design (a bit like beer: there’s no accounting for taste). But let me share a perspective from my three decades of experience working with clients: 99% of paying clients couldn’t care less about what CMS powers their site. What matters to them is that the website looks good and feels professional. The ones we really need to convince are the second tier of decision-makers: the people who will actually use the system day-to-day. These users are rarely designers. They don’t care much about animations or typographic finesse – what matters to them is clarity, ease of use, and a sense that the CMS won’t get in their way. That’s why, in practice, we almost never show clients a backend during the decision-making phase. Instead, we show them beautiful, carefully crafted frontends, and sometimes highlight the inline editing capabilities. That sells. Clients are impressed when they see polished websites that “might be running on ProcessWire” (since, let’s be honest, you can’t tell a CMS from the frontend anyway). How this focus on real-world client priorities could be reflected more strongly in the redesigned ProcessWire website is something I’d love to explore further. Cheers, Mike

I'm currently looking at Grav/Kirby/Statamic etc. for certain simple sites where MySql doesn't make sense, but I'd much rather use PW with SQLite.