Hi all,
just taking my first steps into the world of ModX (coming from an EE background) - and I have to say it’s a great product. However, I get the feeling that Modx is REALLY well designed to create hierarchical static pages. While it has the capacity to emulate a blog via Ditto - from an administrative perspective, if you blog daily - then you will inevitably end up with one folder on your resources tree absolutely rammed with posts. I don’t fancy trawling through a 365+ long article list - so am I missing something here? Is there a more efficient way to organise articles in the administration?
any thoughts/advice much appreciated
SWK
-
☆ A M B ☆
- 24,524 Posts
Ditto can be given a comma-separated list of containers in the &parents parameter.
You can also have multiple Ditto calls on the same page, each using a different container to generate the listing from.
And don’t forget the Reflect snippet for creating an archived listing.
The problem is not so much with how Ditto or a template handles the content of your post/archives, rather that the archives themselves, the directory tree, would get rather large.
Say I have a container, called "blog" - and two sub-containers: "foo" and "bar". Now, I’ve been blogging for quite some time, but only on those two subjects, and have accumulated a 1000 posts in each category. While I can limit and paginate the data sent to the blog page, as an administrator I have a rather large directory structure containing two folders with a 1000 articles apiece.
Do you see where I’m going?
-
☆ A M B ☆
- 24,524 Posts
Then break it up; put older blogs in another container. How you organize your site is up to you. It’s only limited by your imagination.
-
☆ A M B ☆
- 872 Posts
MODx Revolution will allow you to personalize more easier the way you want to organize your MODx Blog.
Creating a grid which contains posts is relatively painless. It’ll will allow users to manage their blog much more like Wordpress (table, search, limit, filter...).
The snippet Quip give a good exemple of what is possible to do with MODx and custom backend menu (managing comments on the back end).
@sottwell
I’m already aware of that option, I’m just illustrating a point:
What if the user does not want to archive posts in this way? Why should they? A "regular" blogging tool queries your posts and returns a result set base on your search - be it on date, name, subject etc. ModX gives you a physical representation of all the posts. This is great to a point, but the problem seems to be related to large volumes of content.
Don’t get me wrong, I love modX, I think it’s taken a really unique angle on CMS and one that suits a large sector of site design. - but it occurred to me that one of the factors that makes modX so good is also what seems to be a critical problem re:blogging.
It’s unlikely that I personally would ever want to post anything like 1000 articles in one subject, I just wanted to see if there was some other method of dealing with blogs from an administrative perspective.
Cool - I’ve been using Evolution - if Revolution solves this I’m stoked!
-
☆ A M B ☆
- 872 Posts
Don’t get me wrong, Revolution will allow to achieve this behaviour more easily, bot it is also possible to do with Evolution (I think with Manager plugin).
Nothing has been made yet on both system.
I’ve installed both now and tinkering about - so far can’t really see how one offers the capacity to do what I’m suggesting. Could you elaborate?
