To sum up in short what has already been said, tasks of our group with priority ONE will be [1] to train XOOPS theme- (and module-) designers and improve skills in any aspect, [2] to be responsible for the default themes shipped with XOOPS core releases and [3] to maintain the XOOPS theme repository.

Besides these tasks there are many topics which should be discussed, many ideas, visions and opinions I hear while talking with others, but let’s not start too many tasks at once. This was my personal fault in the past.


Here is the list of names of the group member:

DefianceB0y
incama
JMorris
kris_fr
Philou
sato-san
studioC

If I forgot someone, please let me know! If not done already, every group member should pm me her/his valid contact details. Thanks!

michael

following the idea of the core devs on sf, i thought it would be nice to have a chatroom online for the team.

http://xoopsdesign.campfirenow.com/

To team: Please send me a pm if not got an invitation !

Might I also suggest you evaluate the current pages and templates with the core and included themes (at least the default) for W3C, xHTML and CSS validation?

thanks you for this suggestion. Not a direct answer, but ... W3C, XHTM and CSS validation is priority ONE on my (personal) list! We will sure look into the themes you’ve mentioned …. But !!! … My personal opinion: NO!, it shouldn’t be a desigers/theme creators job to dig in the mood of templates and to rewrite all of them (not to offence anyone). In my vision, in the (mid-) long term there should not be a real need of modultemplates but smartys output we can use from the module. Today there is too much stuff in these templates (and too much events to make mistakes). While we are using a CMS, the modules output is the content and this should not be filled with layout or positioning stuff. Module Devs should take care of their modules to work and get the result they want, theme devs should take care how to display these results. Many theme creator fail to take care of all modules output. Today, many themes itself are already valid xhtml and css and eg. don’t abuse tables for positioning stuff, but when it comes to display “invalid” output of modules, the layout crashes or strange things are displayed which are not intended. We (theme creators) already have visions for some years now how things could be handled easier. It is time now to work on achieving these visions. But it will be a process … and there are things which have to be done before. … to calm down … There will be some additional templates for at least the “most used/wanted” modules, as far as I know today! still dreaming ... michael edit: perhaps i misunderstood the suggestion and I shoot to much on modultemplates ... CORE themes and templates will have prio1 on my list as said above

Yes, I was pointing at the core and included themes.

See patch 1712443 and this post

Oh, and patch 1730229 and the changes to user.php, register.php and search.php to give them page titles

Curious,

Is there any plans to create a template for the register.php page? There have been many cases in which I needed to customize some things on that page, and without a template, I have to dig through PHP - yuk

As a side note, it would be nice if you could easily add/customize fields that were asked for on the register page...but perhaps that issue is best for another thread...

Also, I'm pretty keen on W3C compliance...I've rewrote many XOOPS module blocks to validate for our sites... any way I can help?

Quote:

added:

Daniel aka technigrafa [contact by pm]