MrSnoozles

I really liked your post in general, but can't agree with this. It is true for end clients that just want something that works and don't care about how it's done. But have you ever worked with other agencies? Can you imagine working for the first time with another agency and you're telling them you want to do the project with ProcessWire? They know a thing or two about technologies as well and also know a variety of CMS from other projects. They usually have never heard of ProcessWire so they're inevitably going to inform themselves about what they're getting into and what they're offering to their client (since we're just the contractor implementing the design). I feel like we've had a harder time convincing those to trust us and use ProcessWire since the new website launched.

I don't disagree with that. Design is very subjective. While I don't understand why the headline is so massive (on a 4K screen), why texts are not aligned (see screenshot), and I don't like the boxes with the shadows and the box that has the "ProcessWire weekly" signup, I still understand that it's professionally made. The main point is that the content is IMO written more towards developers and less towards companies that have to choose a CMS for their next project. I made a quick AI mockup of how I think it could be improved, highlighting the value for the business and developers, that with PW everything takes less time. And time is money.

Hi all, first of all I'm sorry this is going to sound a bit negative. But ever since the new website launched I feel like it's increasingly difficult to convince clients that have never heard of ProcessWire to use it. Have any of you experienced the same? I'm not a designer, but I feel like the content and the design have been made to target developers. That's valid, but if our clients don't want to use the system, neither can we, at least professionally. In my opinion at least the homepage would need a design and content overhaul to streamline the first impression and explain to non-techies why ProcessWire is awesome.

Agreed. I'm missing headless too. Because it's a buzzword that's trending and PW for sure can be used headlessly. We used the really excellent GraphQL plugin from @dadish to use PW as an API for an entire mobile app.

Hi @Dharma, I haven't done this myself yet, but I would look into hooking PagesRequest::getPage . Also check how LanguageSupportPageNames.module is hooking into that method, and get an idea of what it's doing to figure out how to overwrite the behavior.

@diogoDo you have anything planned for these bigger changes already? I have a vision in my head how the ProcessWire backend could look more modern and at the same time be faster to use and cover more use cases, especially when ProcessWire is used for applications rather than websites. If you're planning on working on more profound changes I'd love to discuss some ideas.

ProcessWire has a lot of great features that make it better than many competitors. I'm sure there's much more, but here's a start: Build anything Powerful field types and unlimited templates allow you to build anything. Simple yet powerful API ProcessWire gives you the tools to build what you want, easily and in record time. Headless or hybrid Create a REST or GraphQL API or a traditional website. Any template engine Twig, Blade, Latte or plain PHP? We've got you covered. Multi language Reaching an audience in multiple languages is not an afterthought but built right into the core. Powerful permissions Let users see only what they need to see, with a fine grained permission system. Easily Extensible Modules can change or extend almost any aspect of the system. Long-term backwards compatible We know you hate breaking changes. So do we.

@ryanThe Custom Field module has changed the way I work with ProcessWire more than any other module in the past 10 years. The possibilities are insane. No more "being scared" of adding a new field because it will clutter the admin UI and might have an impact on performance. If I want to store more information about something I can now just do it. And everything is immediately version controlled - no need to create fields or run migrations when going live. It's incredible!! Is there a chance the module will be developed further anytime soon? I so wish it would support the file and image types.

Have a nice weekend, Ryan. Any chance of getting a sneak peek at the redesign you teased at the end of last year?

Updated the post to be clear it's an example and varies depending on which modules are used.

It looks like you need to make $map available in your Latte file first. Then, as Bernhad has said, you could write in your Latte file {$map->render($page, 'YOUR MARKER FIELD')} With https://processwire.com/modules/template-engine-latte/ you would write something like the following in your PHP template file (or ready.php): $view->set('map', $map); It might vary depending on which modules you use exactly in your project.

Okay cool. I thought with JSON functionality they were starting to diverge.

@ryan The module sounds very cool. Does it support MariaDB too or only MySQL? A storage_name option could be useful to be able to rename the field in the api, but keep the values in the database.

Clickbait title aside, I recently found a cool new feature in PHP 8.1 and wanted to share it with you, in case you didn't know this either. Starting with PHP 8.1 you can write $this->method(...) (yes, that's the actual syntax, not a placeholder) to reference a method. I find this super convenient, especially for defining hooks. Plus the IDE can refactor this much better than the traditional [$this, 'method'] callback. <?php class MyModule { public function init() { $this->addHookAfter('ProcessPageView::finished', $this->doSomething(...)); } private function doSomething(HookEvent $event) { // TODO: something } }

This is super useful, as is Mystique. Will it support searching and more complex fields, like repeaters? Agree, this is very useful.