Short term (Big-Bang-for-the-Buck)

Here are a few short term goals I have in mind, but I haven't played with the latest from CVS yet. I was informed there was an expected commit today of some major innovations. Is that true, or is this already done?

* Branding
* Core Templates
* Core Stylesheets
* Core Plug-Ins
* Core Documentation
* Manager Refactoring
* Installer (I think you guys have this one under control already?)
* Outstounding Bug Fixes (got any that need working on?)

I'm sure we can think of a few more. I really think we should carefully consider our decisions regarding DB abstraction, and keep it on the longer-term list for the moment. I'll have more in this regards very soon.

Do we have a feature list? Other documentation in the works?

How easy do we want to allow rebranding?

I have some code in my copy that I could commit that does things like allowing the logo to be easily swapped by placing an alternate image in /assets/manager and that changes all occurances of what is now Etomite to a language variable.

The idea was that eventually all sites on the same server would run off the same manager codebase and so the backend managers could be customized to match the site by looking for a rebadge in /assets/manager.

If the swap-in files aren't there or are removed, the standard logos appear.

I was using it to make the manager branded for the end user:

I think that's perfect short-term. We can add additional swap-in/out options as we break the manager pieces out of their frames.

We can add additional swap-in/out options as we break the manager pieces out of their frames.

Long term, once we get rid of the frames I'd love to see the manager use the template system. If we made some standard tags, the actual layout/colors/design/etc could be completely customized for projects.

+1 on a template-based Manager, for sure.

From a big-bang-for-the-buck-prove-we're-serious-about-being-different standpoint, here's what I'd vote for:

• Travis' manager overhaul (frame-free if possible + FCK and widgEditors)
• Branding with the only required attribution to MODx buried in the credits somewhere
• Robust webuser login / account request suite
• Good base tutorials on converting a site into MODx
• If at all possible, front-end content editing (this would rock folk's world)
[/list:u]

Of course, our initial release will necessarily address all of Jason's suggestions above, especially the installer, but I'm thinking about earlier technology preview releases.

Hi,

Just a few things to note

* frame-free
I don't think we need to rush this one. If we remove the frames what will we use to replace adjustable side-bars? Is there a splitter component/control available?

* Branding with the only required attribution to MODx buried in the credits somewhere
This is something we must be careful about. If we allow users to fully rebrand the system we are just making it easier for some to rip other people off. They will be happy more than happy to package and sell the product to other "blind-folded" customers. Also, wouldn't changing the name (rebranding) make the rebranded product a fork?

Personally I would prefer to add "supported by" branding where the developer can add support information to the product but leave the Etmoite, MODx, GPL, etc information in tact.

* frame-free
I don't think we need to rush this one. If we remove the frames what will we use to replace adjustable side-bars? Is there a splitter component/control available?

Well, my layout still definitely uses frames, so I'm thinking the frame free will need to come further down the road once we have a good Ajax/SODA/something solution in place.

* Branding with the only required attribution to MODx buried in the credits somewhere
This is something we must be careful about. If we allow users to fully rebrand the system we are just making it easier for some to rip other people off. They will be happy more than happy to package and sell the product to other "blind-folded" customers. Also, wouldn't changing the name (rebranding) make the rebranded product a fork?

Agreed, I think. I personally prefer being able to swap out the graphic branding in the manager to "customize" it to the client, but I don't think the end user needs to necessarily change the text branding everywhere.

Personally I would prefer to add "supported by" branding where the developer can add support information to the product but leave the Etmoite, MODx, GPL, etc information in tact.

I like this idea and think it would be an ideal place to still have the graphic logo branding.

Does that make any sense to anyone else?

* frame-free
I don't think we need to rush this one. If we remove the frames what will we use to replace adjustable side-bars? Is there a splitter component/control available?

+1
I think the manager backend needs to be thought out pretty well before we throw frames completely away. Just about every big name commercial CMS I have ever used has resorted to frames, at least a "tree on the left, info on the right" format. I think we do need to break out the tree from the functions above it before anything else.