What system-wide features should be available?
Last Edited: on 18/2/10
- When a user goes to 'legacy/system', they will be able to configure the settings of how Project Legacy works.
- Settings that are system-wide should be available here, and should not likely
pertain to individual groups (except for cleanup purposes)
- A list
of what options should be configured site-wide needs to be created such as website name, length of time
before a group expires, etc
- Once a list of features is made,
visit 'legacy/system' in your browser and try to locate broken links,
dead pages, and specify which features aren't already there or
navigation links that would be helpful to add
- System-wide
settings should include (added settings are updated constantly):
Payments, Board of Directors, By-laws, Integration to Office of Student
Life (OSL) documents, etc...
