List view
- No due date•1/5 issues closed
Wishlist of options / extension for extending the CCCS web 'core'. CCCS Django framework Advantanges over common wiki systems: * Make posts 'draft' or 'published Wikis are meant to be open to everyone. For 'internal' wikis, there is only the ability to collaborate behind a private wiki. There's no option for publishing collaborativly-developed documents. That is, we can't have wiki articles 'visible only' to team members who are logged in, as we can have with the current CMS. Advantanges over common web management systems: * Able to diff the database The current CMS, by contrast, is not intended as a collaborative publication tool. Changes to we content are lost if one user changes something that should not have been changed. While good database backup protocol can help to avoid data loss and compromise, it would be better if the database maintained a record of changes (like wikis do) allowing Git diff functions.
No due date•9/23 issues closedTool to facilitate compliance audits by linking responsibilities and commitments to documented evidence. A future objective is to link this tool into a risk/assessment and/or performance evaluation framework.
No due date•0/1 issues closedThis milestone focuses on bringing together all aspects of web-based data and project management.
No due date•19/24 issues closed- No due date•0/3 issues closed
Items included under this sprint focus on improving the UI and data model for the CCCS Associate CV database.
No due date•41/57 issues closedWith our framework in order, one of our last steps prior to public launch is to style web template to respond aesthetically to changing browser sizes and to render well on mobile devices. This next sprint is all about prettification....
No due date•10/29 issues closed