Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

[Matthew M. <ma...@tu...>]

After reading Michaels Hjemmeside's article, here are my thoughts and
suggestions as they apply to 1.x. Some of these points will make more
sense when I can get a demo running.

Titles
-------------------
Currently I am using the Control Panel (which is pure line item CSS)
wrapped around each of my modules.

Looks something like the following

----------- ------------------
| Content | | Administration |
|         ---------------------------------------
|                                               |
|  [pic] Blog   [pic]Categories                 |


Once you get into a module, like Blog, you see this:

----------- ------------------
| Content | | Administration |
|         ---------------------------------------
|                                               |
| -------- -----------                          |
| | New  | | Archive |                          |
| |      -------------------------------------- |
| |                                           | |
| | NEW BLOG ENTRY                            | |
| | [form]                                    | |


I like this format because:
1) You don't have to click on Control Panel every time you want to go
   to another module. Just click back on Content. 

2) It allows us to have the same options on every page in the same
   place.

3) It eliminates the Back to Main junk. The tabs always take you where
   you want to go.

As for what is contained IN the embedded panel, it's template looks
like this:

<h1>{TITLE}</h1>
{CONTENT}

This template houses all administration done within the module.
The control panel is common. You CAN have your own control panel for
your module, but I am opting not to.

In reference to the Add [something], Edit [something], etc. In all my
new modules 'New' is used to create a new item. I think all my mods
have that same tab and I would support use of this word for English
modules. We can discuss whether 'New', 'Create', or 'Add' is the
better word and whether the name of the item should be suffixed to the
command.

I would also like to agree on a standard for the listing of items. I
am using Archive in Blog and List in Categories. We can agree on a
standard for this tab. For editing and deleting however, those options
are listed along with the items. When chosen, the edit form opens
within the List tab. 


Submenus
----------------------------
I think this is covered by the Control Panel method.


Lists
----------------------------
For empty lists, I vote for showing the column headings basically
because the DBPager (a new listing class for 1.x) works well with this
option. Also, DBPager uses only one template file.

Pattern
--------------------------
I would say most lists will look like the first example. All the
options for an item should appear together and to the extreme
right. If there are too many options per item, icons can be
substituted.

Also the second example is from Users, which has its own
listing class. Hopefully, we can get everyone to use the one listing
class in 1.x. 

Narrow Lists
-------------------------
Menu is an old module and its interface is definitely clunky. I think
we can steer clear of such things in the future.


Input
----------------------
I have no problem with the first form style:

Name
_____________
|            

Address
_____________
|

I will say, however that the grid format is, imho, easier to
navigate. I will leave this open to debate. I could go either way.

I agree with no background color, no enumeration, no colons,
and no emphasis on the form labels.


Checkboxes
----------------------
I agree with everything here. Checkboxes should be placed before
statement phrased as a question.

I also agree with only using checkboxes for boolean questions.


Buttons
---------------------
I tend to prefer the button being set flush to the left. Because forms
are often in a table, I like dropping the submit button after the
closing of the table. The second example puts the button in the second
column of a half completed row. I don't like that.

Buttons as links
--------------------
Agree 100%. Anything that does not pass form elements, doesn't need
to be in a button.


Tabbed Navigation
--------------------
See Control Panel info above. This has been implemented in 1.x. and
the class is easily accessible by other modules.


Tree Lists
-------------------
Agree here as well. Lists should be lists, not tables.



Conclusion
-------------------
I appreciate Michaels information. In our defense, many of the
examples are from older modules. We have learned a lot about CSS,
organization, interface, etc. since they were written years ago.

Since 1.x is getting closer to release, we have the opportunity to set
new guidelines benefiting developers and users alike.

Thanks,
Matt


-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu