Lethbridge College – One Experience


The previous primary Lethbridge College site was built by North Studio using Drupal 6. For the new Drupal 8 site, Lethbridge College needed to migrate content from two WordPress sites into Drupal; import Course content from Elusian Colleague into Drupal on a recurring basis and integrate third party systems with Drupal.  The third party systems would include:  Muut, Instagram, Facebook, Twitter, Flickr, SoundCloud, EventBrite, YouTube and Vimeo.

North Studio was responsible for the overall website build, training and guidance.  And, the Lethbridge College Once Experience team was responsible for the creation of wireframes, designs and a style guide. Our teams maintained continuous communication throughout the project using a combination of regular weekly meetings for development and management which included:

  • Teamwork for client communication via email
  • Slack for instant communication
  • North Studio’s tailored JIRA instance to manage all tickets (an Agile development and robust Quality Assurance (QA) and User Acceptance Testing (UAT) processes)

What We Did

North Studio used Continuous Integration (CI) throughout the project to keep the various environments (Development, Test and Staging) up to date as work progressed, ensuring Lethbridge College’s ability to be ‘in-the-know’ at all phases of development. As a result, Lethbridge College was able to provide feedback on the latest work on a regular basis to increase efficiency.

During the project every measure was taken to ensure full transparency including a high collaborative effort between both the client and North Studio, resulting in daily communications through several venues. Lethbridge College was able to communicate directly with the developers and other team members assigned to their project, with the opportunity to review all of North Studio’s work prior to approval for release through the use of our tailored JIRA/Kanban process. This allowed for constant client integration through multi-layered revisions within the customized requirements of the project.

Throughout the project, the North Studio team oversaw both teams for the majority of development. They managed deliverables and requirements by reporting to both sides of management, utilizing a Project Manager as well as a Technical Lead or Technical Project Manager who worked side-by-side with Lethbridge College’s in-house team.

North Studio built two customized themes for the Lethbridge College website. The primary theme for the site implemented Lethbridge College’s standard branding and colours, while providing tailored experiences for alumni, prospective students, and faculty. The secondary theme extended the primary theme to provide customized styling specifically for Lethbridge College’s “Wider Horizons” digital magazine.


North Studio, through mutual collaboration with the Lethbridge College One Experience team built a customized Drupal 8 site for LethbridgeCollege.ca with a smooth upgrade path for both minor and major level upgrades including Drupal 8.2 to 8.3 as well as possible future releases of Drupal 9. They were also able to adapt and fit current modules within the site to meet the client’s existing needs which decreased possible budgetary strain.

By working with cutting edge frameworking solutions that empower content managers to build and scale their projects, North Studio was able to mitigate possible issues and to facilitate full project transparency. This included, but was not limited to, easily accessible information sharing, cohesive code, and tackling unforeseen development issues, ticket statuses, and bug fixes.

By implementing these custom changes, Lethbridge College content managers were able to independently make adjustments within the Lethbridge College main site and, “Wider Horizons” sub-site which was designed to be scalable and tailored to their in-house team needs.

The developers involved on this project also created patches for several Drupal modules to fix issues that were encountered while building the new site, and contributed these patches in the module issue queues on Drupal.org for the benefit of the Drupal community as a whole.

Download the full case study to learn more