Focus on keeping your existing content fresh and up to date. Don’t make any major changes or start any new projects.
Please use the link to our Jira ticketing system to submit All Web Content Update Requests.
Email firstname.lastname@example.org and the Web Team will be here to support you in a timely manner. We’ve hired additional student workers to make sure that all web tickets are addressed promptly.
Yes, the web team will have access and maintain this asset during this time.
The web team will have access to Siteimprove during the prelaunch phase of the website relaunch. A select group of chosen editors also have access to update aid, admissions and other essential support areas.
During the prelaunch phase, the web team will rebuild Siteimprove to match our new sitemap and align it with our new permissions and governance system.
Yes. The working group is moving forward with an intranet as part of the web redesign project.
No. There is more guidance to come and we will keep you updated on the latest developments with the intranet.
As part of the website redesign project, ITS is in the early stages of intranet development in collaboration with MarCom. The intranet will provide a secure online platform for internal communications, collaboration, sharing of internal resources and information among authorized SU users. The intranet will have dedicated sections catering to specific internal audiences’ needs, such as students, faculty and staff. The plan is to launch the intranet when the new website launches in December 2023.
The development of the intranet adds strategic value to Seattle University in several ways, including streamlined internal communications, ease of access to internal information, increased productivity and collaboration. The intranet also helps keep the external site, SeattleU.edu, focused on critical institutional priorities like student recruitment.
The intranet will be a SharePoint intranet.
The intranet is going to be built on SharePoint that has its own search. The public search (google) that we currently use will only index public webpages. These might include certain pages for the intranet that are on SharePoint but still outside authentication. Although, we are doing a deep dive into our search platform and talking about switching to something more customizable.
No, the new website will remain in the Terminalfour CMS.
Currently we expect the T4 login experience to be the same as the new website.
Our project kickoff is Friday, September 9th. There will be two days of on-site discovery to occur in early October 2022.
There are several phases of this project: Discovery and Strategy, which includes two days on Seattle University’s campus; Information Architecture; Visual Design; Front-end development; Implementation in Terminal Four, User acceptance testing, Content Migration, and Launch.
These milestones and general timeline will be added to our project timeline and phases after our project kick-off meeting on Friday, September 9th. Our current goal is to go live by Fall Quarter 2023.
Watch for periodic updates in SU Today as the progress continues.
For now, continue to update and maintain your content as you always have. The content freeze begins June 30, so June 29 will be your last day maintaining your old pages.
With the announcement of a new intranet as part of this project, some of your pages will live on an intranet for internal audiences, and some will be dedicated to external audiences. The process for installing our existing pages on either the intranet or external site will be different. Please stay tuned as we expect to have more detailed information on the migration process later this summer.
Yes, the new website will be fully responsive, so users will have a great experience on all devices.
The website redesign working group plans to put out announcements in SU Today for key milestones. We will also post updates here and on the project blog.
During our onsite discovery last fall, campus stakeholders participated in interviews with OHO. If you have suggestions, please contact the web team by email at email@example.com.