szabesz

Sorry for the off topic reply, but I cannot help wondering what will Google do with WordPress sites which take up most of the personal and small company landscape? Will it hide them at the bottom of its search results, just because they fail to adhere to any kind of "Core Web Vitals"? Don't let me wrong, optimizing for performance is always a good thing, I just cannot imagine how Google envisions forcing everyone to do it according to its own taste.

Some of us (including me) are lucky enough to have clients who do not care about the look of processwire.com and trust us that ProcessWire is the best. Not all of us are that lucky. So for those who are not so lucky, it matters a lot what a potential future client perceives when visiting processwire.com.

I built "my" first website in `96 with Adobe PageMill, fighting with tables to craft the basic layout it had. It was for a bank, a handful of static pages. I had no prior experience with HTML... :P

No to mention other issues like the following. On my 2560x1440 monitor, while scrolling, I get views like: I guess I do not have to explain why this is far from ideal. Just a big bulge blob with a subscription form in it and that’s it? To whom does it look professional?

But there is one thing we can all agree on, and that is the new design is quite controversial. And as far as I can tell, one either likes it a lot or does not like it a lot. And I don't think that such a controversial look is good in general. As for being "contemporary"? I started my designer career in 1997 and back then everyone used QuarkXpress, Aldus Freehand, and Color Studio (later Photoshop 2.5+). Because Macs were not too powerful, most designs were put together in QuarkXpress only. Why am I bringing this up? Because the current processwire.com design does look like "QuarkXpress only designs" from about 1995-2002. For this reason, to me, this is vintage.

I burnt some credits on Seedream v4. (BTW, Our grandchildren will surely ask us: Grandma, Grandpa, is it true that your image generators were so stupid back in your day?)

Recommended read: https://www.smashingmagazine.com/2025/10/the-grayscale-problem/ Quote: "Colour seems an appropriate place to start. When given the choice, try something audacious rather than safe. The worst that can happen is that it doesn’t work. It’s not like the sunk cost of painting a room; if you don’t like the palette, you simply change the hex codes. The same is true of fonts, icons, and other building blocks of the web."

I quite agree with your two points above. "Section for practical code examples." They could be added to the method descriptions, and not just sample code strictly related to a given method, but code showcasing typical scenarios with related methods and often used techniques, "coding patterns". "Currently a lot of core features are very fragmented and hard to find if you don't know they exist in the first place." So true! I have some notes of some important settings, which I often set up differently from the defaults, but having to look through them just to find something is time consuming. Some sort of clever way of gathering information and providing it in a categorized and digested way would help, I think.

That will definitely be welcome, for sure! Thanks in advance.

You guys rock!

Good luck to the Craft team, but to me it looks like they need to reinvent the wheel every now and then. Luckily, we have our own genius, Ryan, who figured that reinventing the wheel is not for everyone. At least not for us ;)

I would not say a "rollback" is desirable, it is just that the new theme needs some more work because it is rough around the edges. Eg. when selecting pages in a Lister, the "label" showing the number of selections makes the list jump, which is bad UX but can be fixed with a display:"inline-block". Also, used to be shaded inputfield groups can have their background color back, etc... So while I agree that it is sort of half-baked, it can surely be made better.

Awesome! Just what I will need in the near future. Thanks @Mikel for sharing!

News: "...npm got rocked by a record-breaking exploit..." https://youtu.be/QVqIx-Y8s-s And self-driving cars, AI agents, refrigerators, cat feeders, and who knows what else are and will be based on code written by who knows who...

Great new features, thanks a lot!

+1 Is it possible to bring it back?

Hello, This is the closest but also not being maintained: https://processwire.com/talk/topic/22665-module-imagereference-pick-images-from-various-sources/ Not a media manager, but it can fulfill certain requirements: https://processwire.com/modules/process-media-lister/ and "combined" with this https://processwire.com/talk/topic/29985-file-mover/ they can fulfill even more requirements. Not being overly complex, Robin will probably be able to update these whenever needed. That's an advantage....

I think both developers and clients should be the target audience and I cannot see why it would not be possible to target both. Anyway, in my opinion, the new design "targets typographers". To me, it looks like solution to a school assignment for students studying typography. BTW, I found an error in the following href:

I second that. While I completely appreciate all the work that has been put into the redesign, but I think the "brand spirit" is off. I feel like I've arrived at a typographer's portfolio site. To me, the new design conveys no message other than bold typography. All the messages are explicitly spelled out in writing, which is fine, but aside from that, we have plain, rounded boxes, practically no colors, no images and that is all there is to it.

Hi, I do not know it this has been reported or not, but there is at lease one "This video is private": https://processwire.com/docs/multi-language-support/multi-language-fields/ see:

Thanks @Robin S I love tools like this as often there is no need to do the same task again in the future.

Thanks @gmclelland! Pretty useful service for getting high-level overviews. I tried this prompt: Explain how ProcessWire handles locales. And got this: # How ProcessWire Handles Locales ProcessWire provides comprehensive locale support through its **LanguageSupport module system**, which manages internationalization (i18n) and localization functionality across the entire framework. ## Core Locale Management ProcessWire's locale handling is primarily managed through the **Languages class**, which extends WireArray and provides centralized locale management functionality [1](#0-0) . This class contains the main `setLocale()` and `getLocale()` methods that handle locale settings throughout the system [2](#0-1) . The system uses PHP's native `setlocale()` function as its foundation, with extensive wrapper functionality to support multi-language environments [3](#0-2) . The locale settings affect various categories including `LC_ALL` and `LC_NUMERIC` for proper formatting of numbers, dates, and other locale-specific content. ## Individual Language Objects Each language in ProcessWire is represented by a **Language object** that includes its own locale management methods [4](#0-3) . These objects provide wrapper methods that allow setting locales on a per-language basis, enabling fine-grained control over locale settings for different languages in multilingual sites. ## Translation Functions ProcessWire implements a GetText-like translation system with three core functions that work with the locale system [5](#0-4) : - `__()` for basic string translation - `_x()` for contextual translation with additional context - `_n()` for plural form handling These functions are available both globally and as methods in Wire-derived classes [6](#0-5) . ## System Integration The locale system is initialized during system startup through the **LanguageSupport module** [7](#0-6) . This ensures that proper locale settings are established early in the request lifecycle. Locale settings also integrate with other core components: - **Number formatting** through WireNumberTools, which uses locale information for proper numeric display [8](#0-7) - **Page name localization** for multilingual URLs through LanguageSupportPageNames [9](#0-8) - **Field value management** for multilingual content through specialized field types [10](#0-9) ## Locale Validation and Maintenance ProcessWire includes system checks to ensure locale settings are properly configured and functional [11](#0-10) . These checks help identify and resolve locale-related issues during system updates and maintenance. ## Notes ProcessWire's locale handling system is designed to be flexible and comprehensive, supporting both simple single-language sites and complex multilingual installations. The system builds on PHP's native locale functionality while providing ProcessWire-specific enhancements for content management scenarios. The modular architecture allows locale functionality to be enabled or disabled as needed, making it suitable for sites that may not require internationalization features.

I installed it on MAMP Pro and also on its own cPanel account, as it does not support shared hosting. I also tested the Docker option back then and it worked as well, but I am not fluent with Docker so I abandoned that project for a while. But I might get back to it as the idea was to run it it on a QNAP NAS. And it worked but I did not find the time to finish the task to setup automatic backup for it.

First of all, thank you for all your heroic efforts! And I am not exaggerating. Please consider https://www.bookstackapp.com/ Free, open source, and contributors do not have to set up anything. I've used it, it's great, stable, and its developer is actively working on it, improving it regularly.

Back or not, having only one lone icon/image among non-skeuomorph icons/images is, at the very least, questionable.