The development process
Work process
- Template developer selects a template to work on and updates the
TWG (Template Working Group) on your choice by updating template list. Alternatively, Rogier will assign templates by updating the template list.
- Template developer begins by reviewing the Style Guide. Develops
template and does a final check using the HTML, CSS, template code and javascript checklists.
- Developer submits back for review by updating the status of the
template to "review". Please send an email too to your preferred Reviewer, or post it on the forum.
- QA group offers feedback and makes any needed changes (maybe
developer/maybe reviewer). The reviewer sends feedback to original
template developer for learning purposes.
- If bugs or enhancements are discovered, the developer or reviewer
submits a bug or RFE to webgui.org (work it out yourselves). The status in the template list should be updated. Seek help
from group if needed (see forum).
- When template is complete, reviewer submits template to committers Colin or Doug. In the webgui.org design wiki, you can find the submitting requirements. Once the template passes their tests, status is updated to "committed/done".
Tasks
- Andy
- will make a draft for the form templates;
- rest of the group gives feedback;
- inline search boxes;
- dataform template
- Tabitha
- gather & manage stylesheets, locate in a single location,condense IE styles into asset stylesheets;
- add to FilePump with Patrick's help,
- asset controls
- CS template
- Rory
- manage javascript checklist;
- Javascript support;
- dashboard template
- Diona
- best practices documentation;
- html, css and templating code checklists;
- prod for updates from group
- Tessa
- QA and bugfixing;
- style and gallery templates
- Rogier
- manage templates site;
- html, css and templating checklists;
- QA and bugfixing;
- theming webgui;
- userlist templates
- Patrick
- theming webgui;
- Javascript support;
- Carousel template;
- FilePump magic