Ability to let the directory structure determine the tree's contents

[jasonvarga]

For users that are managing content by hand and not using the CP, it was handy in v2 to be able to just place the pages in the directory as needed.

It would be nice to be able to do that in v3.

I'm sure we could have some classes that override the default behavior of structures.

Looks like the bulk of the logic for building URLs is within the Stache's uri index. Rather than looking through the tree, maybe we can just look at entry paths. (It's fine to have entries organized into subdirectories)

Maybe as a small (unofficial?) addon at first, since doing this would probably leave the CP broken.

[mikemartin]

I’ve been wondering if bringing back Pages would help with the UX of V3. It seems to be the first thing that users look for when using a CMS.

[jasonvarga]

This is not about the CP though.

[efc]

I would love this even in the addon scenario where it leaves the CP broken. In my case I'd be happy to manage such a directory from the filesystem directly. I wonder, though, if there might be some way to single to the CP that is should not allow editing of files in such a collection from the UI.