→ back to New Admin Area Project
These are just the first proposals to develop the admin area in a well organized way. Please add your thoughts and improvements.

1. Extract as many reusable code as possible from ADMIN.php to helper classes methods
2. Build documentation using phpDocumentor for these files:
   • ADMIN.php
   • ENCAPSULATE.php
   • showlist.php
   • all helper classes
3. Group ADMIN methods by objects[1] and types[2] to analyse:
   • similarities
   • parameters and returned values consistency
4. Conclusion:
   • report code needs and improvements
   • list needed classes and libraries
   • define some code standards

• see admin_refactoring
• see Functions that should be deprecated, moved or changed
• see New Admin Area Classes documentation

1. Define a complete list of actions performed inside the admin area
2. List possible behaviors for each action (on success, on fail…)
3. Group the actions by objects[1] and types[2] to analyse them
4. Conclusion:
   • report code needs and improvements
   • define a features set for the first version of the new admin area. once defined, don't add new features until the first version is complete

• see actions

1. Define a complete list of screens used by the admin area
2. Describe purpose and necessary elements for each screen
3. Group the screens by objects[1] and types[2] to analyse them
4. Conclusion:
   • define design goals and needed visual and navigational elements (roel's and rakaz' earlier thoughts about the admin area usability and design will be very useful - see the links at the end of this page)

• see screens

• [1] 'objects' are: blog, item, comment, category, misc etc.
• [2] 'types' are categories of actions/screens: 'list', 'add', 'edit', 'batch delete' etc.