

The Processwire API is very, very powerful and has a huge amount of very simple phrases that dig out your data from your pages for you.īut, and this is very important, it does very, very little formatting. For instance, if you want to loop through all the children of a page, you need to use a little php foreach to do it.

Yes, but only in so far as you want to do something complicated.
Ide for processwire full#
All I do is rather than add the full path, I put I put my structural images in a directory called images. I put my CSS in a directory called css within the template directory. Oh, one thing: When you reference JS or CSS files, then you need to point them at the correct directory. You do NOT have to have a special PW version, you don't have to do anything different to you would do if this was a static site. Use any JQuery, javaScript, Perl, anything you like. You can now go off and design a website! You can use any CSS framework you like, straight out of the box. Where you want a field to display, add a tiny bit of PHP and the PW API stuff. Open your template file and write ordinary HTML. One is for creating pages, the other is for DISPLAYING them. NOTE: templates and template files - two different things doing two different things. If you go to URLs, you will see that it is now using your template file. Run back to the admin, go to setup, templates and edit the template you made earlier. Oh, easier still, create the file FIRST, then create the bloody template. Actually, you can associate any file with any template, but for the moment this is easier. So if you called your template my-nice-little-template, create a file called my-nice-little-template.php.

Forget the techy why, it just is.Ĭreate a file with same name as the template. This directory is, for all intents and purposes, like your web root if you were writing a static site. Open up your directories and go to /site/templates/ This is because you haven't written any html, fool! This is a website - it needs HTML! You now have a page, the address to which is something like /mypage/īut you cannot see anything. You create a new page as a child of the Home page and you select the template.Title, couple of text fields, image fields, anything you like. This is not a looky-feely thing, but basically a structure for any page you want to create. You create a "template" in the Processwire admin.What I liked was that I did not have to learn a templating language. But that was not what attracted me to the system. It is powerful, the API is deep, clever and sensible and the back end is rock solid. Now, a lot of people say a lot of good things about PW, and they are all completely right.
Ide for processwire update#
What I have always wanted was a system that gave me the update ease of a Content Management System, but let me put the site together, the shape, look and feel, like I would with a bit of basic coding.Īlong trots Mr Processwire (or Ryan Cramer, to be fair, but I like Mr Processwire). The problem is that sometimes sitting and writing a bit of HTML/CSS or using a system like Dreamweaver is not just more powerful and versatile, but simpler too. Basically all the usual suspects and, to be honest, I hated them all. I have used all kinds of systems over the years - PHP Nuke (bit formative that), Mambo, Joomla, Word-depress. Messing with the intraweb, the little HTML thingies that get stuffed in page sort of thingies and so on. (See also: Creating a single template blog with Processwire and Hanna Code) A little bit of web development is good for the soul
