Hi Chad,

There is some excellent goals you have set there.  ACLs, N-Level Content, File Manager Integration, LDAP, Multi-Site Management are some real key ones that I think people have been waiting so long to see.  It is great that they are on the list and ways to implement them will be looked at.  They are all some key areas to being able to use a CMS to suit your needs, rather then change your needs to suit the CMS.  I am really looking forward to seeing Mia grow.

Regards,

.Joel

First, let me say that on Monday, I was just in the process of installing Mambo for a new site I'm building for an IT company, when I heard about the fork.  I spent a day playing with Mia before recommending to my clients that we go with the talent on this one since we hadn't gotten very far with the site yet.  The improvements, thus far, are already amazing, and you guys have my sincere thanks for getting these features out so that the community can actually take advantage of them.

As for features for the next release, I have a couple of suggestions:

List:
·N-level Content

·Content Versioning

·SEF URL Rewrites

Speaking as someone who has developed CMS sites with the original code base (Out of respect, I'm not going to say the name.) for several years, the absence of these features makes it very difficult for larger, more critical web development projects to adopt this codebase. 

For my current Mia project, I'm using a plugin for the rewrites, but it would be a lot better to have a transparent, built-in Rewrite function that you could turn on or off in the Global Configuration, with customization available in the content edit screen over in the advanced parameters accordian.

N-level Content doesn't really require much elaboration.  I know we all know the value of this.  I'll just say that in larger-scale projects, it's a big deterrent to using this script in its current form.

Content Versioning - same as above.

Thanks again, guys.  I'll try to post regularly on my experience using Mia on my current project in the hopes that it will provide you and potential users with new feedback.

Best,
Scott

Indeed.  I'll code up the RESTful hooks to support writeable REST once you finish oAuth

get a real archive system and kill sections in favor of infinite categories/subcategories with content able to be assigned to multiple categories. and rethink the whole thing in light of folksonomy, tagging and that semantic web whatzit. and what might be done with opensocial and social networking as a co.re concept in CMSes which need not go on carrying the vestiges of newspaperlike/print publishing structures. oh, and be sure to borrow all the good ideas in joomla 1.5.

for the vast host of people not so technically inclined or simply unwilling to wade through forum threads, PLEASE do yourselves a favor and make it very clear on your front page who is in charge of what, and what they are doing. Post a roadmap, post news, and show your progress in a clear and unambiguous way. Many visitors are SHOPPING for an open source CMS. Give them the vital facts about current health, past achievement, and future goals. "Release early, release often" implies this kind of Public Relations strategy.

Last edited by dpk (2008-05-19 12:06:45)

Do you have an example of something you like?

These two, OpenID & content versioning, will be in your hands before long