eydun

Thanks for the reply. I have actually seen most of those templates, but I find them a bit dated. I will post back, if I find some good resources.

Can you recommend any html-templates, free or commercial, to use as a starter for building new templates/site-profiles with ProcessWire?

I has been my experience that Microsoft's mail-servers, such as Office365 and Hotmail, are the most aggressive to filter out incoming e-mails that are suspected to be spam. Often they even do not make it to the spam-folder in the user's mailbox.

Is the school perhaps using Microsoft Office365? Then it is possible that the emails get blocked by Microsoft's spam-filter.

I would use " summary" as meta-description. If you do not want to do that, then you can create a new field for meta-description.

It can possibly be related to some faulty configuration in the .htaccess file.

Impressive site! Which "page hits"-module did you use?

Hi iipa Does the user use the "Paste from Word"-button?

From the docs https://code.google.com/archive/p/jquery-asmselect/ addItemTarget: Where to place new selected items that are added to the list. Allowed values: 'top' or 'bottom' Default: 'bottom'

Not yet, I am afraid.  I just bought this module. Any chance to make it compatible with UIKit?

Thank you for the fine replies. PW is not only the best CMS, but also has the nicest community 😀

I am still a PW-newbie, and have just started diving into setting up templates and fields. How do you typically name your fields? For example, do you use the template-name as prefix to the field-name? Do you re-use many of the same fields across templates? Or do you create one field per template? I ask these question, because I wonder if it does not get complicated when you build a site when many templates and many fields.

Thank you for the reply. I was also coming to the conclusion just to use the "regular" profile, so I am happy to hear that you also say that.

What module do you recommend for a news/blog-website?

Thank you all for your helpful comments. I think I will go with the solution building the new site in a sub-directory. The old site is quite large (100+ pages), and therefore I plan to merge some content from the new processwire-subdirectory via the fantastic API that processwire provides into the old site, during the conversion-process. Quite messy, I know. But with such a complex-reducing system as processwire, I think it is doable. Thanks again!