New Content Approval Process
- Download the content request form.
- Submit the request to email@example.com
- Governance Committee will review the initial request and approve or deny it.
- If approved, the content needs to be built out in development.
- A final review of the completed product in development will be completed by the Governance Committee. The Committee may approve, deny, or request changes to final product.
- Once final approval has been obtained, the development team will submit release notes to Enterprise Systems and schedule new content for deployment with the upcoming release.
Deploying New WSU Mobile Content
Washington State University business offices and academic departments may work with their content development teams to provide users with new tile and content on the WSU Mobile app. To learn more about how to obtain a development account and training please visit WSU Mobile Developer Program. In effort to efficiently deploy the new content and notify users, the following process has been established.
Releases of the WSU Mobile application will deploy once a quarter; visit WSU Mobile Update Schedule to review the schedule. Scheduled releases will help ensure that support is available to troubleshoot issues with the release of new content during deployment. Additionally, scheduled releases will help ensure teams are aware and prepared for the deployment of WSU Mobile updates. New content made by the Washington State University (WSU) WSU Mobile community of developers must be completed and ready for deployment with final approval one month prior to the release date.
All releases will be accompanied by released notes published both on the ITS Confluence Knowledge Base and ITS website. Each WSU Mobile content development team will submit an outline of new content contributed to a scheduled release when the content has been submitted for deployment. Additionally, major releases will be accompanied by both email and social media campaigns from departments represented in the WSU Mobile Governance committee.
New Content Documentation
All new content must be accompanied by a content request form. Content development teams will be asked to provide both self-help documentation and a prototype user flow. The self-help documentation will be published by Enterprise System on the confluence Knowledge Base. The Knowledge Base is a multi tiered ITS reference tool. On the base level of the Knowledge Base are self-help documents available to the public. The goal of the self-help documentation is to answer common usability questions for the general user. When developing self-help documentation for new content development teams should narrow their scope to highlight the common uses and functionality of the new tile, content, and/or AEK, see Self Help - OneDrive for examples.
The prototype user flow is required with the submission of the initial content request form. This flow diagram will outline the services and information that the new content is intending to provide. The Governance Committee will be utilizing the prototype user flow diagram as a reference during the final review of the content.
DISCLAIMER - ANY CONTENT THAT IS REPORTED/IDENTIFIED AS BROKEN OR HAS NOT BEEN MAINTAINED WILL BE SUSPENDED FROM THE PRODUCTION WSU Mobile APPLICATION BY ENTERPRISE SYSTEMS. AN EFFORT WILL BE MADE TO NOTIFY THE ORIGINAL DEVELOPER ABOUT THE CONTENT SUSPENSION. ANY CONTENT THAT HAS BEEN SUSPENDED MAY BE REDEPLOYED ONCE THE CONTENT HAS BEEN UPDATED/CORRECTED IN DEVELOPMENT BY THE ORIGINAL DEVELOPMENT TEAM.