Anke

I didn't mean to question PW's concept in general, although I don't share your opinion that a content management system ought to be concerned as little as possible with the way content is being presented. IMO content and layout are equally important, more so a convincing layout can sucessfully sell poor content (one of the simpler marketing rules). But that's not the point. By calling the handling kind of "behind the times", I was referring to the fact that files a) have to be created and hardcoded by hand and b) reallocated on the server (requiring FTP or other connection types). What is keeping PW from providing a little file manager and a code editor, ideally providing field variables and other snippets, so that everything can quite comfortably be achieved right in the backend?

Thank you for your instant reply. In fact at first glance this handling appears a bit middleagean, but I'm sure there's a good reason for it ;-) .

Hi all, I'm an absolute PW rookie, but starting to work my way through this alternative way of handling websites, thanks to your great documentation. Coming from the "regular" CMS world, where most systems provide something like editable layout templates and/or CSS editors in the backend, I'm trying to understand the concept of PW. Am I getting this right, that In the PW backend I "only" set up the fields, like e.g. headline and body, and then those field variables have to manually be added to a template file ($headline, $body) wrapped in the required hard-coded HTML markup and CSS ids and classes? Anke