Better view for pages list

[OffLine911]

Hello and thank you for this amazing work, i want to ask you if we can we have better view for pages list because the tree is good for small sites only and we need something that are more easy and modern and can handle big sites

[sgirard84]

See this post
#758

It reslulted into new feature

You can use subtree: true in page scheme to avoid listing all children on the main page tree (read doc here https://getformwork.org/documentation/page-schemes/ )

For instance, this is how I setup the blog example

blog scheme:
children:
templates: [post]
reverse: true
orderable: false
subtree: true

post scheme:
options:
default: false
children: false
num: date
imagePreviewField: coverImage

[OffLine911]

ohh thanks bro i did not see it

[OffLine911]

okay i add new view to pages list called cards here is some photo for it:

what do you thinks

[sgirard84]

Indeed, I had the same thinking for my photography portfolio website.

I would add an option on the parent scheme, to enable this view. Something like
subtree: true
subtreeGridDisplay: true

[OffLine911]

yeah i will upload it to my formwork fork as soon as possible the problem is that you need to add some tweaks here and there to get work. my Fork

[giuscris]

@OffLine911 thank you for this exploration!
I am a bit too used to the tree view I actually didn't think to alternatives.
I'd still prefer a hierarchy for large sites (I've tried with ~150 pages), while with cards I'd need more clicks.
Personal preference apart it would be a nice to have as an alternative view (like we do with files) users can toggle.

Would you like to propose a pull request targeted to this specific feature? It could be released with Formwork 2.4 (I'm working on plugins and other enhancements under the hood for 2.3).

I'm open to discussing the other tweaks you are exploring for the overall interface. I'd treat them separately and component by component and would appreciate community feedback.

I'm converting the issue to discussion, it's more appropriate for this type of threads.

[OffLine911]

i don't have problem in that , i will do pull request but i need to be honest here i did not do this alone off course i use AI to help achieve it so you need to look good for any problems it came with it

[sgirard84]

I was also seeing this as an alternative view. And only if the alernate view is enabled within a scheme option.

I don't think it make sense to enable this view for main tree. But when used in combination with "subtree: 1" and with child content that has images (and not sortable), then yes it make sense.

Like an image gallery, portfolio, product list, blog posts, etc.

[giuscris]

Indeed I was thinking this as a different view you can switch to like in a file explorer/finder.
I'd keep the possibility to reorder pages, technically is absolutely possible.
While it makes sense to have subtree a scheme option (you're changing behavior for single pages) I'd avoid adding another option and leaving to the user the choice from the UI.

[OffLine911]

i think that way too, the idea came form if i want to open store or portfolio the tree schema is good but not for that type of projects

[OffLine911]

i add pull request all good you can test it