Grid images best approach

[tooth-paste]

On the front-end pages I want to build a grid of 5 x 10 images.

What is the best approach to keep the backend as user friendly as possible. It would be nice if the PW page would also be a grid and images could easily be changed.

Is there some sort of module or is there a different, beter solution? Any ideas?

[diogo]

Honestly, I don't think it's necessary to reproduce the grid in the backend unless there is a very spacial need. Users can take a certain level of abstraction and can easily understand that, in a list of images, te first five will be the first row and so on. You can limit the amount of images in the field to 50, but you can also do it at template level when calling the field ("limit=50"). Because this field will have many images, you can have "grid" as default view in the field settings.

If you think it's less confusing for the user, and since you'll have a fixed number of rows, you can also create 10 different multi image fields named "row1, row2..." and wrap them inside a field set.

[tooth-paste]

If you think it's less confusing for the user, and since you'll have a fixed number of rows, you can also create 10 different multi image fields named "row1, row2..." and wrap them inside a field set.

The rows are fixed but what do you mean with a field set?

[horst]

if you want to search the forum for interesting things, best is to use google with a search like this

site:processwire.com/talk -"Viewing Profile" fieldset

The part site:processwire.com/talk and the -"Viewing Profile" part are what I use every time, appended with my searchterms I actually looking for.

If you use this, you will get many useful links like:

• https://processwire.com/talk/topic/1057-template-editor-fieldset-indentation-and-checkbox-columns/
• https://processwire.com/talk/topic/176-fieldsetopen-fieldsettabopen-%E2%80%93-what-is-it/
• https://processwire.com/talk/topic/665-editing-fieldsets/
• https://processwire.com/talk/topic/7608-fieldset-grouping-in-admin/

The ip.board searchfield is not helpful. You can also use the google serach with /docs/ instead of /talk/, if you want to quick search in API and other docs.

Happy reading!