heldercervantes

This is a particularly good one. Very well designed ????

Just noticed this one, published a few days ago: https://www.ionos.com/digitalguide/hosting/cms/processwire/ Cheers

Right now, just one or two hundred. I have a universe of 600 potential users, and I expect about 100 to enroll. These users will get email notifications selectively if a gig is posted that matches their preferences. But this is intended to grow and there will be an effort to increase the user base.

By the way @bernhard, this is my first project using RockFrontend, and I could just kiss you ? Rockfrontend with Latte + Tailwind + Alpinejs is such an awesome mix.

This is one of my worries. Right now we have a universe of 600 potential users, so we might be talking about hundreds of emails. Not even sure if the hosting provider will be happy with it. In terms of UI I'm thinking of having a checkbox at the end of the page for "Send email alerts on save", which would be used in the hook. And then maybe tie this with ProMailer for throttled sending, handling unsubscribe and all those nice things it does. But I haven't tried it yet so idk if there are any cons.

Hi guys. I'm currently developing a volunteering board solution. Basically users register saying what are their areas of interest and how they are available for helping, and then there's a "job board" of sorts that lists where help is needed. So I'm doing a simple user registration form, creating users with a specific role. And when I publish a new help request, I want the admin to be able to select from the options of the areas of interest and availability fields, and that should fire an email alert to all corresponding users. This process should be as dummy-proof and straightforward as possible. Any suggestions on how to approach something like this?

Seasons Greetings to you all! I'm wondering, does anyone know of a good online magazine powered by processwire? Like a proper magazine with sections, articles, tags, featured articles, related articles and all that? Think stuff like https://www.archdaily.com/ or https://www.designboom.com/ I'm in that lovely position of trying to convince someone who's thinking wordpress to build their site properly.

Hey guys. Shouldn't the showcase section have a list by author feature? I just found myself wanting to send someone a link to the showcase of the sites I made in PW and there doesn't seem to be a way to do it. And while at it, how about mentioning which projects were featured on PW Weekly? We now have a quite large projects list there, and if the point is to show off the best work made with PW to legitimise it, we might as well bring out the best projects and make it cool to be featured. What do you think?

Here's one of my latest projects: https://petibol.pt/ Petibol develops and produces of all types of EPP (Expanded Polypropylene) and EPS components and packaging for various industries. This website is a collaboration between Supertiny and GOdesign. Super simple approach: The frontend is just SCSS and vanilla js "components" (no libraries), and pages are built with a blocks system based on a repeater field. Having tried a bunch of stuff between building this site almost a year ago and publishing it (Tailwind, AlpineJS, VUE...) it's pleasing to return to this site's code and compare the approach. Here I've basically set up Laravel Mix to compile SCSS, join and minify a bunch of <1kb js files. A BEM style approach to the styles so that I have a bunch of preset variables for typography, spacing and whatnot, and the JS files follow the same logic of identifying components like the hamburger or the parallax effect by looking for specific data-attributes and going from there. Super clean, performant, and couldn't be easier to pick up and maintain.

What would really be great is a tutorial on how to set up a project in DDEV, something I'm trying to figure out right now ? Edit: Spoke too soon. This is so easy it sounds like a lie. `ddev config` - Choose PHP project `git clone https://github.com/processwire/processwire.git web` - Downloads PW into the 'web' directory `ddev launch` - Go through the config, enter db, db, db, db in the database step Done

Here's my most recent project: https://velhinhos.pt/ Velhinhos (translates to something like "little old people") is a free service that helps people understand their needs and find the best care for their elderly, be it nursing homes, at-home services or daycare. The branding – name, logo, tone – is also our work, and we're providing continuity support on ads management and social media. This site features some information/advice about the available options, a blog, and a quiz that helps users better understand the level of dependency. It also feeds leads to their Pipedrive CRM. The frontend is a mix of Tailwind and StencilJS.

@bernhard coming back to this as I just stumbled upon a scenario that was discussed here. In the Craft project I'm working on someone added changes that I needed to add to my setup. Got the message, tried applying and it stopped saying that these changes require the "Navigation" plugin. I added it (just a 'composer install' command line), came back, ran it again and done. The whole process feels very polished. I also had conflicts in the yaml files yesterday, two devs adding new fields. The way to fix it was to include both lines, and right at the beginning there's a timestamp that Craft uses to verify if it's up to date. Used the highest one and added 1 at the end to make sure everyone got an update check. It's really interesting to see how these yaml files are set. There's a main one that describes the project, with plugins, system stuff, some names and keys, and then there are individual files for each field, sections (templates), globals and other stuff that doesn't exist on PW.

Sorry, been away and lost your message. On this particular project I don't see anything there, just a message saying "No content migrations". But it doesn't seem to be related to any of this. I found some documentation here: https://craftcms.com/docs/4.x/extend/migrations.html

How Craft warns you of changes to the YAML files that you haven't applied yet (pulled from the repo): (I'm so used to the simplification of PW's tree that just seeing a "Routes" button in settings gives me the chills ?) And this is the apply changes screen: First chance I get I'm going to have a serious look at RockMigrations. Every new project I get is increasingly demanding on maintenance, with multiple devs, and this is a really big deal. This and SPAs, but thats a different discussion.

That bit is very similar to PW. They have fields and templates just like us (templates are called sections). It's a bit more friendly and straightforward in PW though. They have "entries" that aren't tied to the page tree and some global stuff, but the basic way of doing things is pretty much the same. And as I create fields and sections I see these YAML files being updated to reflect the definition that's on the database. I haven't interacted with applying changes, but I assume in a case like you described the process would somehow detect module requirements and ask you to install or update them first. I guess it could never be a miraculous solution that just does everything and works, but once a project is set up and you get to a point where devs make small increments to the site, this sounds like it will make life a lot easier. If you're curious I found some details here. Interesting stuff.

@bernhard That looks super cool. I'm now working for a studio that uses Craft CMS and although PW still feels way better in most aspects, in this one Craft has a very good solution. More or less like an automatic RockMigrations. As you create fields, sections (templates) and whatnot, Craft generates and updates a bunch of yaml files that contain all configurations. If these files are updated, i.e. you pull someone else's changes from the repo, run a command and it applies all the changes for you. Awesome solution.

This was probably discussed and maybe I'm just searching wrong, so apologies if I'm spamming. In a scenario where we have a production website with a ton of content, and a local dev version with less stuff for tests and sanity. We make structural changes like adding a new page template on the local, adding a couple of fields in an existing one, changing settings on a field and whatnot, and in the end want to publish those changes to production. Any good approaches for doing such a thing without moving the whole content around or breaking it? I mean, personally I've been doing that with DB backups and I have to lock my client out of the CMS while I'm working on updates. No likey. Thanks, H

@kongondo thanks, that certainly makes the detection more elegant. Still have to json-parse the "php://input" to get to the object that I'm passing, though. Example: $fetchVars = json_decode(file_get_contents('php://input'), true); include('./form-processors/'.$fetchVars['form-name'].'.php'); Wouldn't it make sense to have something more processwirey for this as well?

Hi guys. On my frontend I'm using fetch to submit stuff. Is there a neater way to access this from PHP other than the vanilla json_decode(file_get_contents('php://input')) ? $input doesn't seem to get anything from such a request.

So... I've been reinventing the wheel this whole time ? Excuse me while I go hang myself. BRB.

Initially to keep it core, but now I wouldn't replace the thumbnails grid for RepeaterMatrix's UI. It would make everything less intuitive.

By "standardised reusable groups of fields" I mean something like what's described in the Combo ProField. FieldsetPage works nice, or at least improves my current solution, which goes something like this: So basically I'm using a repeater, a block type selector and a bunch of fields (this screenshot is from my last project). The block type selector is a custom module I made based on FieldtypeSelectFile. I just added a way of assigning thumbnails to illustrate what php file you're selecting. This works pretty well, but something that's a pain in the ass is that I have to dump all fields that every content block may use in the same repeater, and then for each of them, make visibility depend on the block type's value. Also, I have to order the fields and use names that work on any block type that uses them, which becomes a bit of a puzzle sometimes. With the FieldsetPage, I at least have things more organised, and I can make adjustments like having fields sorted as it makes more sense for each content block, override titles and descriptions and whatnot. I'm liking this approach. On a first glance only the required fields are still a bit weird to set up, but it's a nice improvement from my previous solution.

Awesome, thanks for the tip. Going to try it out right now

Has anyone thought of the idea of a Fieldset where you can select the inner fields like you do on a repeater, but in the fieldset itself instead of the page template? This would be super useful for standardised reusable groups of fields, or in my case, content block building. EDIT: Well, that's basically the Combo ProField https://processwire.com/store/pro-fields/combo/ - Time to pay up ?

I'll need it. The control panel on this host doesn't tell me the SMTP settings for a new email or allow me to generate a certificate, let alone a MySQL console. Waiting for a reply from support ?