While I am just initializing the structure I ran through the ToDo list once more and found screendesign / design to be one of the next steps. I am not sure what the documentation should look like but as said before it should be a CMSMS best practice and as far as I am concerned I would like best practice in design and technology.
wishy, since you are Mr. CMSMS himself, I would like to ask you to let us all know what you would like to see. Otherwise I would provide a layout (taking the corporate design of CMSMS into account) and the HTML for the template as well. Shouldn't be too difficult. Only think we should discuss is whether we use PHPlayer-Menu or bulletmenu. I prefer bulletmenu since I prefer webstandards and accessibility. But that is just my 0.02 EUR in here ...
What about the rest of you?
Regards,
Nils
Design
-
Steve_a
Re: Design
Just a thought
With the modules and extensions the help implementation is good
But I have 1 small gripe
Some of these list various options but don't show exactly how to implement them (It took me about 20 min to figure this out)and diffrent extensions use diffrent syntax
I'd like to sugest that you should always include a basic example and if various options are avalible you have an example that expands the basic usage with the various options.
With the modules and extensions the help implementation is good
But I have 1 small gripe
Some of these list various options but don't show exactly how to implement them (It took me about 20 min to figure this out)and diffrent extensions use diffrent syntax
I'd like to sugest that you should always include a basic example and if various options are avalible you have an example that expands the basic usage with the various options.
