Notes 3-16-2006
—-
Comments Thoughts taken while working on things today. Note the menu for modules should be consistent – inlcuding the following:
Main/View | Add | Configure
Note, Category manager fixed, look at blocks module – it is still mixed up.
Groups: View | New | Modify Configuration Should be: Main | Add | Configure
Note, there is a difference in the Censor module – what happens when there is not a module menu as in censor.
Note, those breadcrumbs should be active links to navigate through the different levels on the module.
Modules: View | Regenerate | Modify Configuration Should be: Main | Regenerate | Configure
For the modules that don’t have a menu bar – it should still be there for visual consistency – but won’t have any links other than configure, i.e., see legal statements configure
PostNuke mailer needs a main link to go back to navigate to the top of the module.
These notes are taken randomly and noted here for future reference.
Note, screen cap taken to illustrated.
* The ability to edit the text/language files for each of the modules
* Provide the admin with the ability to edit the terms of use, privacy policy, and usabaility statement files frome backend. For example, have the form open into another window so the administrator can edit the text and save to the site instead of having to edit the files directly.
Notes about usability
In the settings file the ability to check all at once or un-check all at once would be useful. Also adding color to the settings - like “not allowed” = red, Allowed = green, allowed with parameters = “yellow” or something else. Note, screen cap taken to illustrated.
The ability to edit the text/language files for each of the modules
Note, when moving into the layers of the module i.e., example categories. You don’t have a way to navigate through the levels you’ve just accessed. There needs to be a ‘bread crumb’ trail so people are able to move around without using the back button. Also, the categories form should be refined, the buttons can be styled (note IBO style sheet).
Form fields should either text description for the field, right aligned, this should be the quick fix. Ideally moving forward the fields should have the text above the input field, see here: (registration IBO).
Category manager form field naming needs to be more descriptive. What is a “data field”? There should be examples for people – maybe a pop-up with an short how-to to step the people through the form and field defines. I think we can use clearer more understandable language then add the how-to for other who don’t get it.
The hack for this is to add the number of spaces before the name for them to show up in the order you’d like to see.
The more the spaces the first in line for example:
Content: Tools and resources that control the content display and input for the site. Users: Modules and tools that relate to the site members and users. Site Layout: Tools that control how the site content is displayed to the users. Community: Tools and applications that offer features and benefits to the community. New Modules: This is where you’re new modules will be displayed and ready for you to apply them to the correct tab category. Stats: Site statistics System: Controls for setting web site defaults. Utility: Things that don’t fit into any of the other categories.
Admin tabs should be ordered according to the administrator. Give the admin the ability to ‘order’ the tabs in the sequence they want. i.e., define the title, description and the order. Currently it is alpha order.
Is there a way to standardize three/four sets of categories, then assign a module to this tab when the module is installed.
Referrers should be called statistics – or something that is more descriptive.
_ What’s not included in .8 – where did it go? AutoLinks AvantGo Banners
For each module to style the backend:
_ Immediate template under the tab menu admin_admin_menu: <div class=”adminbox”> <h3> <div class=”moduledescription”> <div class=”pn-menu”>
_ Immediate template under the admin menu _ admin_admin_view <div class=”admincontainer”>
admin_admin_menu
<!--[* $Id: admin_admin_menu.htm,v 1.4 2006/02/21 11:12:32 markwest Exp $ *]--> <!--[admincategorymenu]--> <div class=”adminbox”> <h2>(To be done) Tab Name: <!--[pnml name=”_ADMIN_TITLE”]--><h2> <span class=”statusmsg”><!--[pngetstatusmsg]--></span> <div class=”moduledescription”>Description of module: <!--[pnml name=”_ADMIN_DESCRIPTION”]--></div> <div class=”pn-menuitem-title”><!--[moduleadminlinks modname=Admin]--></div> </div>
admin_admin_view (note this is the last template for the admin module)
Admin Templates
Admin - OK Administrator Messages - OK ADODB - OK AntiCracker - OK LDAP - OK AuthPN - OK Blocks - OK Categories - OK (need to look at the sub links styled by pn-menuitem-title) Censor - OK – note the formatting is not consistent with the other modules Errors - OK (note need to change the formatting of the table)