suggestions - Joomla! Forum - community, help and support

hi,

i hope right forum this, i'd make suggestions. we've built number of sites mambo , joomla , think fantastic framework. types of customers set them businesses want manage medium sized website in easier , more structrued way.

suggestion 1: found complicated explain difference between content items , static content. suggestion rid of static content altogether, @ least frontend component manages in 1 piece anyway. (slightly) simplify menu manager, administration , main backend page.
to make easy users fill in 1 'box' (we have heard objection using content items), why not have javascript switch 1 editor setup of static content , 2 editor setup of content items.
i must admit have not gone through parameters both of these admin pages , there might conflicts.


suggestion 2: instead of using first entry of mainmenu load first page, can set in global configuration. see dropdown of menu entries , can select 1 go for.
this minor change , sites have 'home' @ end of 'main' menu. save double changing links , settings these 2 entries.


suggestion 3: might sound bit radical, why system distinguish between components , modules? speaking, couldn't put content module mosmainbody() sits , publish wherever necessary. of course, mambots have called on modules , somehow call structure have changed modules not have 'content' such. there mambots doing different things.


suggestion 4: sometime have sites use user modules excessively. usually, because of  client having large number of banners going own site, don't want overhead of banner module or because content of client unstructured. in both cases able have frontend editor user modules. i'm not sure @ how go this, frontend editor code seems structured content component.



any comments appreciated.

jochen

jdaum wrote:hi,

i hope right forum this, i'd make suggestions. we've built number of sites mambo , joomla , think fantastic framework. types of customers set them businesses want manage medium sized website in easier , more structrued way.

this correct forum , suggestions welcome..

suggestion 1: found complicated explain difference between content items , static content. suggestion rid of static content altogether, @ least frontend component manages in 1 piece anyway. (slightly) simplify menu manager, administration , main backend page.
to make easy users fill in 1 'box' (we have heard objection using content items), why not have javascript switch 1 editor setup of static content , 2 editor setup of content items.
i must admit have not gone through parameters both of these admin pages , there might conflicts.

absolutely agree overcomplication of things... have svn access? try here: http://dev.joomla.org/content/view/17/6 ... sion  things changing everyday.

suggestion 2: instead of using first entry of mainmenu load first page, can set in global configuration. see dropdown of menu entries , can select 1 go for.
this minor change , sites have 'home' @ end of 'main' menu. save double changing links , settings these 2 entries.

this interesting, going reworking menu system touch , i'll bounce idea around rest of team.  valid request.

suggestion 3: might sound bit radical, why system distinguish between components , modules? speaking, couldn't put content module mosmainbody() sits , publish wherever necessary. of course, mambots have called on modules , somehow call structure have changed modules not have 'content' such. there mambots doing different things.

actually, system architecture gets in way.  take @ diagram: http://dev.joomla.org/content/view/1137/80/

the main difference in system control.  you'll notice component called part of request, ie. option=com_whatevercomponent&...  big part of how system works, 1 component in control of main output per page request.  in theory module has no control on page request , reacts state of system.  module *owned* either application or component, whereas component owned application.

more interesting reading,

components: http://dev.joomla.org/index.php?option= ... components
modules: http://dev.joomla.org/index.php?option= ... ls:modules

those pages give basic description of how these extensions interrelate application.


in short, suggestion sound, immediate future not real possibility sub-application nature of components tightly built system know it.  changing mean not rewrite of system, entire rethought of architecture.  again, not bad idea sometime in future, not major release cycle.

suggestion 4: sometime have sites use user modules excessively. usually, because of  client having large number of banners going own site, don't want overhead of banner module or because content of client unstructured. in both cases able have frontend editor user modules. i'm not sure @ how go this, frontend editor code seems structured content component.

what editing? site template's calls include modules? or inside modules themselves?  if in fact talking editing things inside hte modules, modules job provide method of editing, goes system control, want done via component.


louis