From another thread, how about changing the name of "Snippets" to "Code Blocks" or something along those lines -- something to denote it can contain programming logic and is evaluated in the parser. Which is pretty much exactly what it is, and should also be pretty intuitive to both techies and non-techies alike.
Similarly, we could call a chunk an "Static Block". "Placeholders" are pretty well named already.
"Plugins" alter or extend the way the core system behaves. Intutive on its own.
"Packages" are groups of co-dependent plugins/modules/snippets/chunks/pages and even DB queries that install into the system to create a custom behavior or application. We need an installer for these that is internal to the Manager. This should be a priority for TP4, in fact, I think. Should also be able to uninstall as well.
Speaking of "Manager", should it be called that or the "Control Panel" or "Control Center"?
In the short term, it’ll be painful even for me. But as we go farther along, we really need to be as clear, straightforward and "non-clever" as possible when talking about the core technology and operating parameters. Read Jeff Veen’s article, also mentioned in teh opensourcecms.com interview, for more insight into my thought process.
http://www.veen.com/jeff/archives/000622.html
I couldn’t agree more with what he says.
In a similar vein, we need to seriously rev our "blank state" install. There’s no reason why we couldn’t preconfigure the site as a simple blog, with a simple marketing/contact page and so on. We could even have the default text be an explanation of the basics of how to use the system.
MODX Staff
MODX Staff
