Typecase publishing platform
A project to deliver a modern publishing platform that allows the University to create, guide and publish content on different digital channels.
The design and development of a modern digital publishing platform is critical to the University's ability to attract and retain the best and brightest students, engage future business and research partners, communicate our research power, and help staff and students to complete tasks online, reducing business costs.
The University Publishing platform called Typecase has been designed to meet these goals. Typecase is built around three key principles:
- ease of use
- seamless reuse of content
- building for future use
These principles help to guide the design and development of the publishing platform. This helps us to make sure that authors can focus their efforts on content creation. The information they create can be reused on bath.ac.uk and it is held on the platform so that it can be reused whatever the technological developments are.
Typecase is a decoupled content management system (CMS). A decoupled CMS separates the content management application and content delivery application so that it can make content easily accessible for display on any device or platform.
Typecase for content, and for courses
There are two versions of the platform. Typecase for Content (originally called the Content Publisher) is used by the University to create, and manage and update content on bath.ac.uk. Typecase for Courses is used to publish course information to www.bath.ac.uk/courses/.
Typecase can deliver the same content across online and offline channels, this is called multichannel. Typecase is also omnichannel ready. This means in the future the University will be able to deliver different content across channels to create a contextually appropriate and seamless experience.
How Typecase works
Typecase is based around a microservices architecture. This means is that instead of being a single application, it is system made up of four different applications that work together:
- dashboard, editor and content repository - this is the application which is seen and used by authors to create and manage content
- publisher and template repository - this is the application which gets the data from content repository and puts it into the website templates
- site generator - this is triggered by the publisher and generates the individual pages for the website
- web server - this handles requests for the pages and serves the pages and associated resources to the end user
Adopting a microservices architecture means that Typecase is easy for developers to understand, develop, test, and it is more resilient. This means the applications are less complex making it easier to maintain and develop.
The University's in-house Digital team has designed, built and developed Typecase. These are the benefits:
- the product is uniquely tailored to meet business requirements and user needs of the University
- we don't have to wait for a supplier to develop new features or fix bugs
The plan to develop Typecase is based on on four initiatives. These initiatives help to prioritise features and focus our effort on delivery. The four initiatives in order of priority are:
- Delivering a foundation
- Enhancing collaboration
- Optimising the user experience
- Improving integration
New business requirements and user feedback are weighted based on the following criteria:
- alignment with the current initiative
- alignment with the University strategy
- frequency of feedback from user
- performance of templates
New features or bug fixes are then prioritised, grouped by type and added to a backlog of work. This process happens weekly. View the Typecase roadmap.