My first Processwire site

[elmago79]

We needed to make a small site for World Book Day in my office and had officially no budget for it, so it sounded like a good pretext to try Processwire for the first time. So it took last year static site, hammered on some new colors and images and then processwired it. Here it is:

http://dgp.conaculta.gob.mx/dml2015/

There are some things to fix in the frontend, and surely is nothing to be noteworthy as a site, but it will serve it's purpose. I was kind of surprised by the fact that the frontend is still taking way more time to do everything right than the backend. I had to learn a lot more php than I ever thought I would in my life, and my spaghetti code might be unreadable, but I managed to program and add all the dynamic content in about a day (and since receive changes almost daily, it's a blessing that we have a clear interface to edit it).

The most impressive thing for me was that if I tried to do something, it usually worked. Since it's my first try, that was something I never expected. Also, you need to publicize and document the Page field a lot better. It is incredibly powerful. I know I'm only scraping the surface with this site, but my guess is that this feature is what made making content dynamic in this such an easy feat.

However, I learned some things the hard way:

* Never use a title field inside a find selector. If it has quotation marks or other special character it will fail completely.

* You can't use the datetime filed to only write time --even if it seems you could--. This drove me crazy for a while, but then I discovered that about two weeks ago some kind soul created a module for a time field. Many blessing for that perfect timing.

* Some places you can chain selectors, some places you cannot. I have no idea why. I mean, I know its php related, but I guess I need to dive in a lot deeper to get it.

* Some things are case sensitive and some are not. Some things you have to always write in lower case. I'm still trying to get the hang of it.

* Migrating to production it's a pain. You get a lot of unexpected errors, which thankfully the forums helped me solve.

And two questions:

* In order to restrict the kind of template the children of a page could use, I ended up creating another template who's only reason to exist was said restriction. Is there an easier way to do this?

* I'm having some weird login problems. A user can't login or get's logged out after some minutes. How can I troubleshoot this? 

[tpr]

Looks nice! I guess it's informative too but I can't understand a word in it

In order to restrict the kind of template the children of a page could use, I ended up creating another template who's only reason to exist was said restriction. Is there an easier way to do this?

Check the parent template's "Family" tab, there's a setting "Allowed template(s) for children" near the bottom.

[DaveP]

There are some things to fix in the frontend, and surely is nothing to be noteworthy as a site, but it will serve it's purpose.

I don't know - looks pretty good to me. 

As far as some of your problems - chaining selectors etc., post some specific questions and I'm sure someone will help. It's a good way to learn, but you seem to be doing very well already.