Plan and Build a WebPac Site
Configuration and Customization
We have built WebPac to meet a wide range of needs for units within the Faculty, but we recognize that additional configuration or customization may be needed. Below are the options available within WebPac.
EXISTING FEATURE CUSTOMIZATION
While the standard design provides a robust offering of features and configuration options, some unit specific customizations can be accommodated within WebPac. Customizations fall under two categories:
Units may request customizations to any of the standard feature displays included with WebPac. This is limited to simple changes such as headers, number of items on a page, the way items are ordered for the display filters.
CONTENT BLOCK CUSTOMIZATION
Content blocks represent a collection of content (e.g. Quick Links, Events on the homepage) which is placed within a specific section on the page. Units may request additional content blocks be created and these can be added to the site where content blocks already exist.
Feature customizations are not included in the base cost of WebPac and will be quoted for approval prior to the start of development. In addition to the one time development cost, there is an ongoing maintenance cost. Feature customizations need to be updated manually each time the WebPac backend is updated – approximately 6-8 times a year. Each feature customization will result in an additional 30
minutes of labour per WebPac update, which will be chargeable at the current Discovery Commons cost recovery rate, and is over and above the standard hosting and maintenance agreement. All customization will be detailed in the project brief and approved by all parties prior to development.
NEW FEATURE REQUESTS
A new feature is any request for functionality that doesn’t exist in WebPac. New features can be requested by submitting a request form. For a request to be considered, it must be technically possible within the existing WebPac framework, meet the needs of more than one unit and improve user experience. Once the request is received and accessed, it will then be submitted to the WebPac Advisory Committee for review. If approved by the committee, it will be placed into the development sequence. All new feature requests will be detailed in the project brief and signed off on by all parties prior to development.
Inital request is recieved and a WebPac Request Form is created
Request is sumbitted for technical review/feasability
2. Community Review
The request is submitted to the WebPac listserv for comment.
Feedback is added to the request document.
Request is sent to Discovery Commons for feedback and cost estimate.
3. Committee Review
Request is presented to the WebPac Advisory Committee, with full details including technical specs, cost, ranking information and community feedback.
If approved, a ticket is created for the feature, and development is initated.
Once a test version is available it will be sent to the unit that made the request, the committee and listserv for feedback and review.
Sign off on the feature will be provided by the committee once testing is completed.
A schedule is created for launch and documentation is created by Discovery Commons.
Once the feature or update is available the requesting unit, WebPac Advisory Committee and listserve will be informed