Block design - question re strategy1 user found helpful
For public browsing I will need a page to show a list of these items, with a clickable button or something on each item that allows the browser to go to a page that shows full details of the item. This must be a very common requirement, but I haven't been able to find any add-ons other than e-commerce, which this is not - there will be no sales via the website.
For editing/maintenance I will need the same two views, with extra capability to support editing. So, do I need 1 block or 2? It seems to me that maybe I need 2 - one for the list view and one for the single-item detail view. But maybe not - I have been using Concrete5 for a while but this is my first serious foray into developing custom stuff. Do I need a new block(s) at all, or is this a place for Single Pages?
Any pointers to the appropriate strategy will be much appreciated. I am quite comfortable in PHP/mySQL, but the Concrete5 ecosystem is very large and complex!
The editing you want is accomplished by going to the detail child page and editing that particular page.
Have a read here:
Or better yet, just add a Page List block to a page that has some child pages below it and play around with it.
I've been doing some reading about Single Pages since I posted the question, and it does sound like this may be a job for one or more of them. But I will also give further thought to the PageList approach.
Its been used in this way before (may take a bit of searching the forums, here and in eCommerce)