Leaderboard

Maybe we can extend the site-wide search to include the body / description of modules as well, be it with less priority? This is an example of a use case: I knew a module exists that uses DeepL to translate site content, but when I searched for DeepL I got 0 results: https://processwire.com/search/?q=DeepL. However, DeepL gets mentioned 5 times in the body of this module page. It was only until I tried searching for terms like 'Translate' that I could find this module. Edit: there is another module that I missed and in my opinion should have popped up.

Hi everyone, we’d like to share a small but handy module we developed at frameless Media: TextformatterSmartQuotes. 🧠 The Problem While working on a client project, we needed to replace straight quotes ("...") with typographic quotes (like „...“) — but only in the visible text content, not inside HTML tags or attributes. Using the TextformatterFindReplace module, a case like this: <strong style="font-size: 18px;">Improved "well-being"</strong> would turn into: <strong style=„font-size: 18px;“>Improved „well-being“</strong> which breaks the HTML. We tried solving it with regular expressions, but none proved reliable enough. Every approach either failed to match all valid cases or accidentally modified tag attributes. That’s when we decided to build a dedicated solution. ✅ Our Solution TextformatterSmartQuotes is a Textformatter that replaces quotes only in visible text, leaving HTML markup untouched. It supports the following quote styles: German: „…“ English: “…” French: « … » The quote style can be selected in the module’s settings. 📦 Installation Place the module in /site/modules/TextformatterSmartQuotes/. Install it via the Modules admin interface. Assign it to any text/textarea/CKEditor field under “Text formatters”. Configure your preferred quote style if needed. This module helped us avoid fragile regex workarounds and keeps content formatting clean and reliable. Feel free to use, improve, or contribute to it. You can download it on GitHub or via the Modules Directory We’re happy to hear your feedback! Cheers, Mike

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.

That would be nice. To be honest, I never use forums or website search. By default, I just fire up Google. My usual suspects are /talk /blog /docs site:processwire.com/ deepl site:processwire.com/talk deepl site:processwire.com/blog languages site:processwire.com/docs $page

The conversation continued: "AI Agent said: Would you like me to compare some of the popular platforms (Bubble, Glide, Retool, Make, etc.) from the perspective of building an AI tool like you’re doing? You said: Not needed. You just reinforced what I already suspected. The hype is just that, hype. AI builders have their niche but are not right for scalable, secure, hosting-agnostic apps or allow true design freedom. AI Agent said: Exactly. You’ve summed it up well. No-code/low-code AI builders are like prefab houses: quick, convenient, good for certain needs — but if you want a solid, scalable, secure, and truly customizable structure, you still need an architect and builders." Our jobs are safe for now! Just need to convince clients. 🙂

I have been called out for just talking and not actually doing some work repeatedly. So I followed up on @bernhard's proposal, simplified it, added a JS build system and added some example hooks for InputfieldDatetime to illustrate what this can do. It's still a draft because at this time, I am not sure if I did understand the hooks system correctly especially when dealing with callbacks. https://github.com/processwire/processwire/pull/323 What do you think? Sorry Bernhard that I removed your rockdevtools integration and example code. I am trying to get as close to a mergeable implementation as possible.

I'm confused. Isn't ProcessWire primarily the tool we want to convince more developers to use in order to gain a larger user base? So this page should primarily be used to convince developers of the advantages with examples (sorry to say that) instead of animations that have nothing to do with ProcessWire. To convince customers of the system, it would be better to provide a good demo that shows how simple ProcessWire is to user. However, this could also be done here, among other places: https://www.softaculous.com/apps/cms/ProcessWire

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.