
We've been hard at work implementing some of the remaining high-priority features in Mephisto. The most notable missing feature is Asset/File management. Well, we've started hammering away at getting this implemented the past couple of days and have the basics of it working, with that said, it's no where near finished.
Update: Major progress has been made in the trunk, check it out!
From the screenshot you can see we're gonna be sporting an OS X style search feature. Also, the last 5 or so images you upload will be shown on the new article page allowing you to quickly have access to these files.
When we were discussing how we wanted to implement assets, I didn't want to implement it like other systems have: Files are attached to articles. There really isn't any benefit of having a file belong to an article. If you want to use a file system wide, why shouldn't you be able too? Of course, other systems never prevented you from direct-linking these files (I suppose), but that defeats the purpose of attaching files to articles. Files belong to a site, they are merely used in articles or the design.
I would speculate the only reason files have always been attached to articles is because you can upload files directly from the same interface from which you create the article. I guess it only seemed right that the files belonged to that article. Not true--this is just the most natural process for publishers working with assets. You don't want to have to leave the article page to go to some separate assets area just to upload an image.
Although you can't see it in the screenshot above, we plan on also having an upload form on the new article page that allows you to do just this. But what if you like to prepare before you write? Lets say you would rather upload your assets from the separate assets area. It wouldn't be all that intuitive if you couldn't access those images you just uploaded from the interface which you write your article. Having the assets area open in one tab while having the article form open in the other tab is far from ideal. We're gonna solve this problem by showing the last few files you just uploaded on the new article interface so you can quickly access these images.
It can be assumed that if you just uploaded a few files, you plan on using them. But, what if you don't? What if you've uploaded a bunch of files, and the files you want to use in your new article are a month old? Well, we're gonna solve that problem too. We're also planning on implementing a search interface in the new articles area so you can quickly find the files you've lost long ago. I also have another really cool idea on how to handle these situations too that I'll talk about more once I get the details hammered out.

Your probably wondering with all this stuff going on the new/edit article interface, won't it be cluttered? Well, it sure sounds like it could be, but I've thought about this one myself and have come up with a fairly simple solution. Tabs. Simple, effective, and it works well.
With all that said, it should be noted that none of this is complete and the SVN trunk is under heavy development. You will run into bugs under Mephisto edge. It's only recommended you run edge if you're wanting to help bug hunt, you're really brave, or you don't mind the occasional hiccup.

This looks really cool. I've got a few projects in the queue that I'm about to use Mephisto on and this will be some added goodness.
What is keeping me from switch to Mephisto is the lack of xmlrpc api. I never use admin interface to post my articles. Hope you add this feature soon and keep up with the great work.
I like the integration into the articles section, that was one thing i missed in other engines.
Kent: Yeah, we gotta get the XMLRPC stuff in. I too use an editor like Ecto to publish so it's pretty high on the priority list and hopefully will be coming down the pipeline soon.
awesome! looking forward to it, I have been looking for a rails cms with this feature set, for a few projects I have and also to learn more about rails in the process of implementing them. Thanks for writing it!
forgot to ask: any plans to include flash files in the list of possible assets?
re: Flash. Sure, why not? Though, I'm thinking they'll get clumped in with 'Documents' because they can't really be classified as Photos, Movies, or Audio from the content type alone. The goal with this is to easily manage any file that's served from your website.
I'm sure the last thing you need is another random opinion, but here you go anyway! :)
I think this Assets management stuff looks awesome, but I would much prefer to leave the "types" as just another filter. I don't know about anyone else, but I just dump all of my uploaded files into one directory... in the "files" directory no less!
What I'd imagine being the most flexible system for managing Assets would be to have the menu on the far left more like this:
All | Images | Audio | Video
And those views (I guess - I don't know much about Rails) would just filter the "all files" by type if that would be useful for display. Am I making sense? This is just me being really... really bored at work, but I think that would be the best non-limiting way to organize things.
You'd dump all uploads into a folder called "files" and then have a spiffy way to filter/search through them.
Anywhoot - I'm going to stop bothering people in weblog comments now. I think this looks great. I'm going to start toying around with it and see if it'll work for me.
Files are dumped in folders like 2006/8/15/foo.jpg. The filters are only for content types really.
I see, I hadn't thought of the categories as file content-type filters, that makes sense. Just upload whatever, and the system will organize it for you. very cool :)
but as an implementor it feels weird that flash would be included in Documents... I guess I see media files classified as audio, movies, photos and then flash as its own weird, standards-unfriendly beast. since designers like it so much (at least the ones I've worked with do), I end up using it as an asset much more than other movie and audio files, so see it as deserving of its own category to be easily accessible. If not, perhaps it'd fit better in Movies?
Of course, that's just my use case and I'm also using the blog comments to give a random opinion! ;) I should really add myself to the mailing list...
What about archives - ZIP, RAR, TAR.GZ ? I can imagine that they would be quite a popular thing to include as assets - in fact, I'd be more likely to include a ZIP that I would be to include any movies. In the end, you could end up having too many types available, cluttering up the UI and hamring usability. I wouldn't call a ZIP file a document, but where else would it go?
How about replacing 'Documents' with 'Other Files'?
I like the idea of adding flash to Movies and replacing documents with Other.
Take this as it is - a comment left by a guy with way to much time on his hands at work - but I don't see the point of organizing Assets into date-based folders. Isn't the date another bit of information that you can get from the file system? Maybe it's just me, but I think it makes the most sense to simply upload all files into one directory and make a front-end for browsing them. Anyway, I'm looking forward to trying this out very much.
Trevor: It's an optimization technique for the most part. If you have a large folder with every file you ever upload in one folder, it can really slow down a site depending on the amount of files you have. This also keeps from name clashing in most cases.
Justin, thanks for posting how you have tackled this obstacle. I am currently implementing a 'blog' type component for a project. The UI for assets/uploading is a very slippery problem. I was waking up every few hours last night thinking about how to upload in the 'new/edit' UI without having them belong to an article. Never did come to a conclusion (half asleep) and then found this post this AM.
Whew. Thanks for the great description. Really food for thought. Off to download the trunk to learn form some code....
Does, or will, Mephisto support for enclosures/podcasting etc?
Great product - keep up the good work! Tim
TimH: Of course! Not in 0.6. Perhaps 0.7 will have enclosure support.