MODx resource tree drawback

I've been following MODx from its 0.9.6Evo to Revo. I'm really digging much into MODx when I have a serious project, and I found that it's the right solution for scalable website, except for one problem, its Resources/Elements Tree.
When my documents gain a number, Resource Tree becomes vastly hard to find my document, and organizing documents seems harder. I know that I can use "Collapse All" button and stay away from heavy load of the tree. Otherwise, I can use "Search" to find my specified document (under v2.2) . But in my opinion, it's just not enough.
I've tried out DocManager, Batcher, but it's quite different from my point of view.
While every resource can be a container, it's rather good to organize things under some categories. IMHO, it'll be better if we can "dive" into each category so that we can view child resources, not to be distracted by other categories or places, just like some way of sub-tree navigating individually. However, it'll be much nicer if we have pagination of the tree.
By that way, we can use Resource Tree for more advanced data, just like using a custom table.
Hope that someone understand what I mean, for now, it'll try to be stay at old fashion way, ignore the tree, and pay my attention to custom table, custom manager page learning-curve.

Regards,

Great input! I have been using MODx for quite a few years and love the tree-based approach, but you're right that it doesn't work perfectly in all situations (big sites especially). However, after spending some time in Drupal's very tucked-away approach to page management, I still think it's one of the most straightforward UI techniques I've seen for accurately showing at a glance the scope and location of all of a site's pages.

My two suggestions for improving your experience:

1. Make good use of Categories, container resources, and possibly even multiple contexts. Although they don't solve everything, they do create a tiered system that is much quicker to navigate and easier to manage (especially with judicious use of form customization) than a flat hierarchy.
2. The beauty of Revo is its customizability. It's very easy to hide the tree completely. Creating your own separate manager that suits your specific needs exactly can be done with ExtJS, custom dashboards and CMPs. All the tools you'd need to do it are there; there's just an obvious time commitment and learning curve to pull it off.

Your suggestions are remarkable, but it'll take time to learn customizing the system from the core to extjs to obtain exactly what we need. MODx's steep learning curve is not really at the way using its template or other elements, but advanced customization. (Maybe it's time for me to take higher steps ).

My previous ideas are not new ideas at all, while I can see them have been done in ProcessWire (this CMS inherited many things from MODx, I think), it has a resource tree with pagination (if I'm not missing somewhere).
Sorry for pointing other CMS in the topic, but it's worth us taking a glance at. Pardon me, I'm not trying to convince our MODx developers to rework on the tree or somewhat, just a little attention about how to organize your resources and usage of resource tree that would make it more effective.

Otherwise, I think Articles can be a great extension to start digging, because it creates new resource container and doesnt mess the tree up.
One problem always comes to me, that, there're too many ways to achieve a purpose in MODx.

That's an interesting solution. We are considering the same approach for MODX Evolution. See this: https://forums.modx.com/thread/75556/modx-evolution-manager-restyle-project?page=3#dis-post-418713

with MIGXdb its possible to create a TV, with which you can manage child-resources and to resources related custom-table-records in a ext-grid. Will add a little Tutorial how to do so soon here:
http://rtfm.modx.com/display/ADDON/MIGXdb.Tutorials

@microcipcip: It's great to know that there're people having same ideas. I would love to pay attention to your project.
@Bruno17: I've been in love with MIGX so far. MIGX can help to design page structure with multi-block which I can post a little tutorial when I have time.

I only use MIGX as some container resources which wont save too many records, because I'm not sure how it would be look like, I scare that I'll have a long list above my content section (which one will find it awkward somehow, even though container resources often don't include any content).
Will MIGX implement ajax pagination in future?
[ed. note: nepheus last edited this post 14 years, 6 months ago.]

MIGX and MIGXdb are two different things.
And MIGXdb has pagination of course.
Read more about MIGXdb on rtfm.

@Bruno17: I'm looking forward to more tutorials on rtfm about MIGXdb. I'll try to work on screencast for more details of the configuration.