Versions Compared

Old Version 12

changes.mady.by.user Steven Maglio

Saved on

compared with

New Version Current

changes.mady.by.user Steven Maglio

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scope of Work

Phase

Requirements

Notes

Phase 1

  • The contractor can create an account at developer.ucsb.edu, so we can set him them up with permissions on the current Drupal site.

  • Our Drupal site(s) are all hosted within Pantheon, providing:

    • a Git based code version control system

    • 3 tiered (Dev, Test, Live) system

    • database migration between Dev, Test, Live

  • Project will include the migration of the developer.ucsb.edu from Drupal 7 to Drupal 8.

  • The upstream within Pantheon will be the UCSB Public Affairs SIS&T Distribution, which provides:

  • The UCSB Campus API team will be available to assist, provide guidance, and testing for the migration.

  • Useful UCSB Pantheon Documentation:

Phase 2

  • Connect developer portal authentication to the campus SSO system to allow developers to login to Drupal based developer.ucsb.edu with their campus ID login credentials.

  • Implement Apigee Teams feature (Teams allow developers /portal users to share responsibility for an app with other developers.) See: Apigee Docs on Teams

  • In addition, 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 team and other campus teams. 

Roadmap

...

Communication / Team Organization

  • The contractor will attend daily meetings with a Campus API Team representative to look over the progress of the prior day and plan the next steps.

    • There will be weekly meetings with the Campus API Team which will serve as a chance to get feedback on the previous weeks accomplishments and derive input on the upcoming work. Campus API Team to provide project oversight.

  • Jira will be used to organize project work, and an account will be provisioned so the contractor can access and work within that system.

    • Some work will fall outside of the Jira system and will be handled on an “as needed” basis. (For cases where input/requirements are being discovered on the fly.)

  • The majority of work will be on a Pantheon hosted Drupal application. The contractor will be provisioned an account which will have access to the Pantheon dashboard(s).

Contractor Requirements

  • Performs analysis, conceptual modeling, design, implementation, and troubleshooting of Web Applications and technical routines to automate new or existing business processes using the Drupal framework.

  • 5+ years' experience developing applications and websites using the Drupal framework including working with Content Types, Field API, Entity API, Form APl, Taxonomy, Views, etc., or equivalent combination of education, training and experience.

  • Ability to consistently develop clean, semantic, valid markup, accessible and responsive websites

  • Experience in Drupal backend and frontend development including module and theme development.

  • Experience in modern PHP web development (PHP, RESTful APls, JSON)

  • Experience programming web solutions using JavaScript, JQuery, CSS and HTML

  • Understanding of Drupal best practices

  • Experience using best practice version control methodologies and tools such as GIT

  • Comfortable with Drush and Composer

  • Performance tuning/understanding of Drupal caching layers

  • Experience in application security roles and authentication practices.

  • Active in Drupal community (Drupal.org profile, module issue tracker, local user groups, etc,)

  • Experience with SSO

  • Experience with Pantheon platform