After having got a bit of fun with 0.9.6, I intend to get into the 0.9.7 branch through a personal middle term project (personal blog, at last would say some ^^)
I know it is quite early stage, but the pretest I done of 0.9.7 just confirmed me it is already a robust branch for an alpha release.
I’m even now playing under SVN version since it seemed too safe otherwise
.
Just before jumping into the pool, I would like to check some of the current vision of the development on some, from my perspective, important points.
I already apologize if it:
1. has already have been asked billions times, but I didn’t seen it having crawled the MODx next forum.
2. seems a bit exigent/rude/early asked that way. Don’t hesitate to tell me if so. I’m known ambitious and impatient.
Coming from different background, and Drupal (I know it is not meant to be directly compare to massive editorial engine but...) for the most recent, I’m particularly attentive to
1. Internationalization
1.1. Currently ModX give a pretty thigh control of the content. How it is planned to bring translation ability to it. I’ve seen it is expected to be a feature, but also not really ready yet.
1.2. Current manager is already really document oriented in term of granularity, which is kind a good basis to integrate translation ability, without duplicating posts and having to bridge the translations relations aside of it.
1.3. If such system can be duplicated to all resources and elements (templates translation?), it can still be heavy and some rather indexing "content chains" to allow translating them one by one.
2. Versioning
2.1. For me, version management, at least on a selected part of the resources, is an important feature, to allow recovering editing issues as well as collaborating work with a proper history
2.2. Here again, the current set up seems pretty open to such feature even in the current manager, but not even already pencil marked (or I’m not really seeing it yet).
2.3. I can imagine the difficulty here regarding the version progress from elements called in content (i.e. Snippets, Chunks... etc... : which version of this chunk should be called in this version of this resource...?)
2.4. Still I should be easily management on selected part of content (another tick aside of cacheable...etc...) and maybe also manageable on more dynamic content (optional version parameter into tag?)
From these two points, you will see that I’m not really database friendly, as mixing all this brings quite a lot of crapping data.
But still I will need to implements these features, and I’m just wondering how it is expected to be implemented:
1. Core? (and it seems to me that it is quite open to that).
2. Plug-in? (Core needing to be quite ready for that since both need to impact quite in depth the system... and if it is ready for, then why not core?)
2. Snippets? (I can already imagine managing content translation/version with translation/version being sub docs of the document versioned/translated, but should be more tuff with other elements (templates...)
You would have understood that I more believe that such quite universal/fundamental features should be core.
Indeed, I believe that using a good part of the flexibility of a system to support translating/versioning is unfortunate.
Don’t misunderstand me; all the above is not a judgment on the current alpha release I have on hand. (my current state is more like "WOW"
).
I’m just lacking some perspectives on the current core potential or the stakes which is intent to address in the end and would love to be enlightened with the current vision of the current coding.
(And I’m sure they are not pre considered features).
Still if it is too early/not the right place to discuss a bit more in details these points, don’t hesitate to tell me.
I’ll bother you later with taxonomy and multi dimensional tagging: P.
Thanks for reading this, and even more for your replies.
Laurent
MODX Staff
☆ A M B ☆
