Currently the Policy documents that are available for download to Adrian Flux, Bikesure are Sterling customers are handled via the (now legacy) customer portal. Since the migration to the WordPress based customer portal, the existing policy document is still being handled by the existing customer portal. The documents themselves are still being managed in the existing portal backed. The documents themselves are being delivered to the corresponding Brand sites via an API in the legacy portal. There is a front end client implementation for this, with a companion WordPress plugin.
Similarily, the FAQ and Privacy Policy statements were managed vai the customer portal, but these were migrated over to be amanged by a brand-unified service sitedata-service. The standalone Sterling sitedata-service, which was developed as part of the new Sterling site rollout in 2018 was also migrated into the unified service. This allows all brand FAQ and Privacy Policy / Metadata to be managed in a central location.
A project is underway to migrate the policy documents management and delivery to the unified service for all the brands. This will bring the benefits of the management as well as fully retiring the old customer portal instances.
The completed steps in the project are, at a high level:
- Develop and rollout a new unified sietdata service from the exisitng Sterling sitedata service
- Migration of FAQ and Privacy policy data from exisitng customer portal for Adrian Flux, Bikesure and satellite brands (such as Trinity Lane)
- Migration of FAQ and Privacy Policy data from standalone Sterling sitedata servce to the unified service
- Migration of user accounts from exising services to the unified service to give a seamless login experience
- Creation of front-end client code (javascript) to render information on the brand front-end sites
- Creation of “shim” client code to enable the existing Sterling cleint side code to use the new unified service without having to change the existing Wordpress code
- Creation of a wordpress plugin to configure and use the new sitedata service in Wordpress sites
- Policy documents API created in existing customer portal to deliver to new brand sites
- Sitedata plugin updated to deliver policy documents on the brand sites
- Shim created to handle existing Sterling brand implementation
- New models added to the service to handle the policy documents and related meta models (such as category, company).
The steps to complete the full project, and retire all exisitng services (bold steps are completed):
- Develop and configure AWS S3 storage to new service for existing documents
- Migrate existing policy document metadata to new service
- Client side code updated to deliver (new) service docs
- Update WP plugin to deliver policy from new service
The project is scheduled to be competed for testing end of July. Aim is to test early August and rollout mid August.