Filed under: CMS
We’re getting deeper invested in the new CMS project that is underway. But what does it mean?
The web presence on campus is decentralized. Our colleges, departments, and organizational units are all using different programs and software to create their web sites to showcase what an amazing place USF is. However, it is important to centralize these services and unite our web sites to create a congruency from a brand perspective. We are USF and by implementing a CMS everyone will be using, we will highlight the leadership and support the university has for its colleges and departments.
Who are they and what will they be doing?
The CMS workgroup is comprised of members from across USF Tampa. Each member brings his/her own unique style and perspective that will be used to help guide the project. These members have been specifically chosen based on their backgrounds and their current positions with USF (meaning, brilliant, savvy, and most importantly – experienced)
- Kathleen Long, Information Technology
- Stephanie Harff, University Communications & Marketing
- Christopher Akin, Information Technology
- Charlotte Koh, University Communications & Marketing
- Anne Scott, University Communications & Marketing
- Roger Ali, Information Technology
- Jason Lehman, Information Technology
- David Soniat, Information Technology
- Eric Pierce, Information Technology
- Carol Tufts, Information Technology
- Brandy Frey, Information Technology
- Alisha Ales, Information Technology (that’s me!)
- Valerie Laconto, Information Technology
- Carolyn Mourey, Information Technology
- Uma Dhavileshwarapu, Information Technology
- Michael Sink, Information Technology
This workgroup will be working closely with the Web Rebranding Advisory Committee. That group consists of 4 technical and 4 non-technical members who will serve as the oversight committee, meaning as we move forward with the project, the Advisory Committee will provide feedback and direction. The Web Rebranding Advisory Committee will be meeting monthly from now on.
Now that we have our workgroup and committee in place, we’re going to start getting to the meat of the project: defining requirements and developing templates.