HMCB

I’ve been following this ping pong match for a few days. 😁. Gotta say, I loved it and @nbcommunication, you are awesome. Great developer. Thank you for your contributions to the PW community.

@bernhard Understood. Thank you. And I see you have been a beast in my year away; you’ve got a slew of modules. Great work.

So awesome. I’ve been away from PW for nearly a year and I come back to this good news. Question: Can we replace the PW logo with our client’s and keep this throughout updates to PW?

I have been singing the praises of MailerLite for years. I use it in all my sites. Thanks for creating this! The documentation is sparse on this module and I have yet to use this, but only an email signup can be captured at the moment? No form field data can be written to a ML entry? This works great for forms with just an email field. For capturing more data (like interests), I assume having an automated email at signup at ML itself would be preferred (for completing their newsletter profile)? And that’s fine.

Can it also perform actions based on date/time plus a value of specific field(s) in a page?

I saw Stripe mentioned. That’s a must-have here in the USA 😂🙏🏼.

Is there a way to include the calendar view in front-facing pages (public, non-admin; obviously view- only)?

@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.