Enhanced Suffixes for friendly URLs with custom content types

I just added a new Feature Request to the Bug Tracker. Here’s a rundown:

This was touched on in a way by Raymond on the forum a while back (http://modxcms.com/forums/index.php/topic,471.0.html). However, the idea I have in mind is to combine the "Suffix for friendly URLs" feature with the "Custom Content Types" feature. My thinking is that we can have more than just one type of suffix for different documents. Documents of the type ’text/css’ would have a .css suffix and ’text/javascript’ documents would have a .js suffix. Of course this could be customizable to allow the ability to add new document types with a custom suffix. Such a feature should be implemented to Templates rather than to each individual document. That way a default document type could be set to each document when a specific template is chosen. After that, a user could override the document type at a per-document level should they choose to do so. The benefit would be that users will be able to greatly expand on the functionality of MODx and allow for such things as dynamically created CSS and Javascript files. In my opinion, a feature like this should be a priority since it will open up so many more doors for enhanced functionality (AJAX anyone?)

Looking through the core code a little bit, I think something like this could be relatively easy to add on. Only tricky parts to me would be altering the custom content type selection to allow for custom suffixes...that and altering the template capabilities to allow for a default content type. Raymond’s post had some icons associated with each document type...don’t know how far we would want to go with that but I think perhaps if we stick to the basics at first then we can always follow up on it later.

So...what do ya’ll think? Priority feature or not?

Jeff

It’s a great feature I think should be addressed for sure. As far as priority over internationalization and bugs, I don’t think so, but that’s why we’ve got multiple Devs.

Agreed. Yeah, internationalization and bugs are definitely things that need to be taken care of so...get those whipped out and then we can revisit this soon. In the meantime, I’ll probably look at the core and see how this possibly could be implemented and, if anything else, map out how I think something like this could work. Who knows...I might even be able to code this myself...certainly could be a challenge! But...I’ll have to wait a bit...got way too many other things going on right now. Heh heh!