HMCB

@Juergen you are awesome. Great final addition to this module.

@Juergen great work. I’ll be using this for upcoming landing pages for a sales/marketing company. Thank you.

Thanks again guys. Great advice. I’m going to set up a PW installation well ahead of building the site and play around with the approach.

Sorry for just now getting to respond to all the great input. Thanks for taking time to jump on this thread and help me think this through, especially @poljpocket! Having only dealt with English and the North American market for all my career, this is new ground for me. Would you agree that starting off with 'domain.com/en-us/' would be wise versus just domain.com? And how exactly would PW allow for that…is it simply a process when using localization?

I was not planning on detecting language automatically. The user would simply choose it within the select-your-country page, but I will give you code consideration. That could is very much appreciated. For the most part, we are leading people to the various site home pages and sub pages by means of advertisements, social, etc. but in the case of someone landing on the root of the site, I planned on providing the country menu page as noted above.

Yes, 90+ % will be the same but pricing will vary by region. Yes, @poljpocket has solid advice. Thank you for confirming it and your input.

I forgot to add, there will be cases where subdirectories are needed to denote locations, like… - domain.com/location/01 - domain.com/location/9999 My initial thought is use the above structure, but location 9999 may _one_ location in Costa Rica. Can I do redirects in PW where both point to the same page and how does that affect localization? - domain.com/location/9999 - domain.com/cr/location/9999 (Costa Rica)

The nature of a project I’m taking on is what will eventually become a global company. We are building a retail footprint internationally. We are starting in the USA first. So I am thinking in country URLs instead of language (although I understand that language generally goes hand-in-hand with the region). Consider the following URL structure… - domain.com (USA) - domain.com/ca (Canada) - domain.com/ge (Germany) - domain.com/it (Italy) - domain.com/au (Australia) - domain.com/co (Colombia) - domain.com/cr (Costa Rica) In the case of the last two, they are both Spanish-speaking countries. Will ProcessWire allow me to map Spanish to both of those URLs and duplicate the content? I am not so sure how localization fully works in ProcessWire. I would like to start at the ground level with a good strategy and not have to backtrack. Thanks for your input.

@kongondo Thanks for your efforts on this. I personally think you should have started a GoFundMe to help you. The end result of your efforts will give PW a credible option to turn to instead of defaulting to Shopify.

Very well put. Thank you.

I am probably the least capable person in the community. I was able to build a very nice delivery app two years ago with Processwire. I was proud of it although it needed more polish. Because of being a relative newbie and designer by trade, I built a front-end that was meant to replicate a backend. Why? Because I wasn’t versed enough on creating custom admin pages in PW plus I didn't want it to look like the PW backend. That left me open to security holes, no doubt. But the end result was decently slick. But guess what really bothered me about the PW backend? I didn’t want my client seeing the word “Pages” throughout the UI they’d be working on. PW is powerful and I didn’t want them thinking this app was a glorified website. “Pages” stuck out like a sore thumb. Other CMSs forgo that which makes building something on top of them seem more custom and crafted to the specific use case. For instance, Craft CMS (see attachments) has a modern backend UI that would feel at home to me and yet there is no mention of “Pages.” I think that extends the use of their product beyond just a website. I know some of you may think I’m crazy but it’s been touched upon throughout this thread in one way or another. PW is the perfect ground floor. Being so opinionated on Pages just seems to pigeon-hole it and especially if the backend UI improved to feel more modern, then we’d have a tool that would allow relative beginners (to custom app development) to build some powerful stuff. Thanks for listening.

@Juergen amazing stuff. Thank you very much.

Wasn’t that linked enhancement already addressed?

@Juergen holy smoke! That’s exactly what I meant and wanted. Thank you my friend.

It would be awesome if there were a way to indicate whether a form input should be displayed, right within FrontEndForms, when we define our fields. I know this was asked on page 11 of this post/thread. Something like… $privacy = new \FrontendForms\InputCheckbox('privacy'); $privacy->setLabel('I accept the privacy policy'); $privacy->setRule('required')->setCustomMessage('You have to accept our privacy policy'); $form->add($privacy); $customNote = new \FrontendForms\Textarea('message'); $customNote->setLabel('Custom Note'); $customNote->setRule('displayIf')->$privacy(true); $customNote->setRule('required'); $form->add($customNote); I’m not a programmer but 'displayIf' was meant to check if a form field (in this case the privacy checkbox) was selected. But the same should be true if a radio button was selected or a choice in a dropdown or a value entered into a standard text/message input field. And of course, the required rule of customNote in the example would only fire off if that field was displayed on the page. Otherwise, that field is hidden.

@FireWire this was masterful. Just wow. You, Ryan, ProcessWire, and the entire community is awesome.

This is masterful. I can see using this on just about every site. Thanks Ryan!

@BitPoet amazing and helpful response. This is perfect for an opportunity that just materialized in the last 48 hours. Thanks ??.

@BitPoet This module is assigned to specific fields, like an image upload field? The resulting URI is then saved in Processwire in a separate field? What I am looking to do is save have both the image and URI saved in PW.

@bernhard, I meant “_not_ beholden to UIKit…” At any rate, I understand everything you’ve explained. I appreciate your input.

@bernhard, this module uses both UIKit and Tailwind in conjunction? The use of UIKit is because it has premade components not available in Tailwind (out of the box)? If in conjunction, won’t the CSS styles clash with each other? My preference is for Tailwind styling so for the components we are beholden to UIKit-way of styling?

I like your efforts on this. Visualizing the title portion is very helpful.

@teppo Thank you. This is fantastic.

Very cool. Thank you, @Robin S.

Just finding this. THIS IS HUGE! Thank you, @FireWire.