XOOPS: Organisation and Projects of Xoops TEAM Design

Posted by: kris_fron 2007/9/30 12:02:07 5831 reads

Tasks Xoops Design TeamThis team in close collaboration with the other teams of Xoops, occupies the party “Design”. Composed regular members in workload daily newspapers, they also have (each one in its field) the management of Working Groups on the various projects of the team.

The current report (difficulties of personalization in a professional touch, absence of “design standards”) revealed the need for re-examining the writing “design” of the core, this task is not so important that we could think it for a team, even of reduced size, motivated and collaborators (between its members but also with other "Xoops Team").

This team has a work important to realize, we must take the aforementioned like a multitude of projects and set up management and the means to obtain convincing and fast results.
These Task Groups must appeal and be made up of volunteers of the various Xoops communities according to the projects to realize. They has there for all the temporary participation and qualification levels (indeed even two files to correct in certain projects, in fact already two of realising!).

Thus a Team for you, by you!



The role of the Design Team being only participative management in the Task Groups. Each group will have its space to communicate between them, the reading will be opened, on the answer by members of the other groups could be done only by their Team Leader.

The members of the Team Design will have a role of team leader in the tasks, the role of Chief of the Projects and coordinator, being allocated to the person responsible for the Design Team. In addition to a weekly point of work, each Task Team Leader will give a a report on work and planning for the 21 of each month so that the Chief of the Projects can work out the report with the council and the community for 1st of each month.

A project/task will finish, new will begin (ex: setting in conformity of modules - creation of themes for the admin - …), perhaps with the same group or not, according to their competence, of their available time, their motivation as of his members. The such waves on the beach, we will always have this movement of flow and backward flow, knowing that the core and the suggestions of the members will be our moon.

Currently we have 11 projects/tasks, some relate to only the Design Team : Task Themes Xoops Websites - Theme.Xoops.org - Daily Team task, the others are opened with the participation of the community within the service of the Working Groups. They exist existing work on which we can base ourselves:

  1. on Xoops versions 2.2 and 2.3,
  2. the themes zetareticuli, morphogenesis and css100
  3. proposals of hacks on the various sites of the communities
  4. the projects of each one of we on our websites tests are elements to be taken on account to facilitate work to us and to reduce the time of realization of this challenge essential in Xoops.

1. Task Core

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team.

  1. 1 - To count all the styles of the core and to draw up the style sheets corresponding (for the module system and its templates (style.css), for the core (xoops.css). That makes currently certain selectors (ex: #mainmenu) in xoops.css, whereas they should be (or are already) in the style sheet of the theme? Style.css of the module system should have only the style suitable for the administration and the core of Xoops.
    Currently we have too much code HTML and statement of style in the files php, they miss templates (ex: edituser.php, register.php,…). We must create, and limit of it code HTML in the php core.
  2. 2 - In xoops.css, we must put and create “general” selectors to help the Dev. Team, the programmers of module, as well as the designers of themes to facilitate the work of the latter in the respect w3c and a standardization of the namming/semantics of the selectors.For example, only:
    /*======== styles pour mettre des blocs "flottants" par exemple des images ======== */
    .floatleft {
    floatleft;
    margin-top1em;
    margin-right 1em;
    padding-left4px;
    border0;
    }
    .
    floatright {
    float:right;
    margin-bottom1em;
    margin-left1em;
    padding2px;
    border0;
    }
    /*======== classes d'alignement ======== */
    .left text-alignleft; }
    .
    right text-alignright; }
    .
    center text-aligncenter;}
    .
    justify text-align:justify; }
    .
    middle vertical-alignmiddle;}
    .
    top vertical-aligntop;}
    .
    bottom vertical-alignbottom;}

    /* for oriental language, just inverse */
    .txtleft text-alignleft; }
    .
    txtright text-alignright; }

    /*======== classes de largeur ======== */
    .width100 width100%; }
    .
    width95 {width95%}
    .
    width75 width75%; }
    .
    width66 width66%; }
    .
    width50 width50%; }
    .
    width33 width33%; }
    .
    width25 width25%; }
    .
    width20 width20%; }
    .
    width10 width10%; }

    /* ========= classe de police ========== */
    .small font-size.92em;}
    .
    normal font-size1em;}
    .
    big font-size1.17em;}
    .
    maxi font-size1.5em;}

    .
    bold font-weightbold;}
    .
    italic {font-styleitalic;}

    /*======== classes d'affichage ======== */
    .clear clearboth; }
    .
    block displayblock; }
    .
    hide displaynone; }

    already the developers working of the core and modules would facilitate.

  3. 3 - to put the core as far as possible validates XHTML 1.0 Transitional (to the maximum go to “strict”)
    1. To put the tables and forms as recommended in the standards:
      1. --> table, caption, thead, tfoot, tbody, etc… (to even elimninate the tables)
      2. --> form, fieldset, legend, label,
    2. To implement styles only by “class” and “id”.
    3. To eliminate the "target blank" (use potential of Javascript to open the page in a new window)
    4. to add the missing “title” and “alt” in the links and images of the core
  4. 4 - To help the Task Group “Documentation” to carry out documentation necessary on this point, because the aforementioned is necessary for the developers, but also to the end user to understand or personalize with facility its Xoops.

2. Task System Mod

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team.

  1. 1 - To put the "system" module as far as possible validates XHTML 1.0 Transitional (go to the maximum close to “strict”)
    1. To put the tables and forms as recommended in the standards:
      1. ---> tables, caption, thead, tfoot, tbody, etc… (to even eliminate the tables)
      2. ---> form, fieldset, legend, label,…
    2. To implement styles only by “class” and “id”.
    3. To eliminitate the "target blank" (use potential of Javascript to open the page in a new window)
    4. To add the missing “title” and “alt” in the links and images of the core
  2. 2 - To create the missing templates
  3. 3 - To help the Task Group Documentation to carry out documentation necessary on this point, because the aforementioned is necessary for the developers, but also to the end user to understand or personalise with facility its Xoops.

3. Task Admin Redesign

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team.

  1. 1 - To count the suggestions of the users and programmers of modules, to work in a collegial way with the Dev. Team on a reorganisation and a redesign of the administration (user-friendly, functional, web 2.0, etc…)
  2. 2 - From work of the Task Groups “Core” and “System Module”, to write a list of features to be integrated and to carry out the redesign administration of Xoops.
  3. 3 - To help the Task Group Documentation to carry out documentation necessary on this point, because the aforementioned is necessary for the developers, but also to the end user to understand or personalize with facility its Xoops.

4. Task Theme templates

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team.

  1. 1 - From the standards of naming/semantics defined by the Design Team (on the basis of work completed by the various groups), to produce a basic template of theme (ex: default_simple) and another the most advanced with the use of the professionals or experienced designers (ex: morphogenesis)
  2. 2 - To help the Task Group Documentation to carry out documentation necessary on this point, because the aforementioned is necessary for the developers, but also to the end user to understand or personalise with facility its Xoops.

5. Task Themes Core

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team.

  1. 1 - To carry out a set of 3 or 4 themes in conformity with the Xoops standards for the core of xoops, in order to replace the old ones, a vote of the community could be planned to select the forwarded themes
  2. 2 - To help the Task Group Documentation to carry out documentation necessary on this point, because the aforementioned is necessary for the developers, but also to the end user to understand or personalize with facility its Xoops.

6. Task Documentation

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team. In close cooperation with the various Task Groups and Doc. Team, these members will have to compile and organize documentation relative to the “design” of Xoops following an objective set of themes. Ungrateful work I must recognise it, but so much enriching for the writter and useful for the Xoops community.

7. Task Theme Xoops Websites

Task Group made up members of the Design Team. In charge the realization of the themes and personalization of the templates for the sites of the foundation, work to be carried out in close cooperation with the various existing teams. The themes must have the adoption of the Xoops Council.

8. Theme.Xoops.org

Task Group made up members of the Design Team.

  1. 1 - They will have to define the quality criteria of the themes suggested and forwarded, we can for example create a “label” Xoops for the themes answering completely the criteria, once defined, the adoption of the council will be necessary before publication.
  2. 2 - They will have to carry out the presentation and the setting in downloading (or link to site of the authors) of the themes “labelized” on the theme.xoops.org site, as well as the creation of a portfolio “design”, news and rss infos on the design, xhtml html, css and Javascript. Documentation will be on the site of Doc. Team.
  3. 3 - In addition, they will have in charge the administration of the theme.xoops.org site and the support on the forum of the Xoops community.

9. Update Old Themes

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team. This group will have to off put at the new Xoops standards the “best of" the existing themes.
It could be carried out a vote near the communities to select the themes which deserve to be upgraded in a first turn. Then, each group member will undertake the amendment of a certain number of theme according to his available time. The remainder will be it, if this Task Group decide to continue its existence after the first phase.
This exercise is excellent for a user wishing to learn how to make a theme. This team will also write a documentation and/or FAQ on the updating of the old theme.

10. Test Work Task

Task Group made up voluntary and motivated members Xoops communities and directed by a member of the Design Team.

  1. 1 - To test the work of various Task Groups
  2. 2 - To check the relevance of documentation

11. Daily Team Task

Task Group made up members of the Design Team.

  1. 1 - To bring aid and support to the Dev. Team, programmers of modules, end-users on the aspects of the design of the themes, templates and design…
  2. 2 - To carry out a FAQ and/or tutorials with “Doc Team” on the recurring questions
  3. 3 - Regular publication of topics carried out by the Design Team
  4. 4 - To maintain a waking state before “design” to anticipate as soon as possible the Xoops development towards those, if relevant