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!