PaulAik

Possibly answering my own question here... will wireRenderFile do the trick? https://processwire.com/blog/posts/processwire-2.5.2/#new-wirerenderfile-and-wireincludefile-functions

Wondering if I can render out partial content via the API, and pass through either the current page, or a set of variables. E.g. instead of this: $content = "<h1>This is the content</h1>"; I'd love to do this: $content = $something -> render('/site/templates/views/partials/partialcontent.html.php', $page); I've seen in the API docs the ability to render pages as partials, but I think this is a bit different (e.g. partialcontent isn't a page itself).

Ahh, found it - thanks!

I'm wondering if there's any way to achieve template field inheritance in ProcessWire in order to enable 'common fieldsets'? An example might be, for example, Page Titles or SEO Meta Tags. I'd like to include this functionality in a common header file instead of on every page I code up, but in order to do this I'd ideally need a way to ensure these fields are present on every template. Having a look at the options, the closest I've seen so far is the option to clone fields from an existing template when creating a new one.

Appreciate the replies guys. I was like "where are these fields they speak of?!", then realised they were there... I just had to install 'em!

I'm looking at choosing ProcessWire as my 'go-to' PHP CMS came up with a couple of site architecture/CMS feature type questions along the way. I'd be grateful if someone with some ProcessWire experience could weigh in on some things I queries/assumptions I up with... Content: If I have a repeated data item (e.g. such as an image slider with the fields Image, Title and CTA Link), how do I represent this in ProcessWire? The options I've seen so far appear to be...Fake Pages: Creating a structure under the page containing the image slider data nodes (maybe in a container folder, so HomePage > Slider > Slider Item 1... etc) Custom Field: Building a custom field with the properties I need. This doesn't seem to be 'the ProcessWire way' for this sort of requirement? Preview Function: There's no 'preview' functionality baked into ProcessWire. API: The ProcessWire API is pretty powerful, with functions to access the entire CMS content tree. Controllers: I don't think there is a concept of controllers (in an MVC sense) in ProcessWire, but 'Modules' could be a viable alternative? I'm thinking about those moments where there's business logic that needs to be taken care of (form processing, etc). Thanks!