Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Overview
Resources
Notes
| Phase | Requirements | Notes |
|---|
| Phase 1 | - New site creation using the public affairs distribution
- Apigee modules installation
- Transfer current site content
- Setup and transfer workflow and rules
- Migrate user accounts
- Home page design
| - Phase 1 will include the migration of the site "as-is" from Drupal 7 to Drupal 8.
- We estimate the project to take about 160 hours
- The Apigee team has limited resources that will be available to assist, provide guidance, and testing for the migration.
|
| Phase 2 | - Site redesign to accommodate additional areas
- Automate the lookup to check for Apigee module updates
- Automate the application of Apigee module update
- Connect to campus SSO
- Implement Apigee Teams feature
| - There is a need for a web presence for the campus DevOps initiative. The developer portal was created initially as a generic developer resource site (developer.ucsb.edu). With the API platform being the main purpose of the site initially, it's design centers around this function. We are hoping we can redesign it to better fit the vision of serving the developer community in a wider capacity.
- In addition, in Phase 2 we want to implement some site improvements, such as SSO integration, the Apigee teams feature, better integration with the campus identity system, and automation of the Apigee Drupal module updates.
- The resources for some of these tasks will be different as they will require direct involvement from the Apigee and other campus teams.
|
| Phase 3 | - Account cleanup automation
- Move all components to AWS (database, existing code)
- Develop account cleanup code
- As part of the AWS migration we can migrate the Heroku components for the chatbot
| - This task is not directly related to the Drupal migration and will require different resources.
|