RCC Institute of Technology: WordPress Front End Inside the Yorkville Group’s Integrated Stack

Christopher Ross

4 min read
RCC Institute of Technology: Local Web

RCC Institute of Technology, the former Radio College of Canada, founded in 1928, was one of the oldest private technology colleges in the country, teaching programs in electronics, information technology, and applied technology trades. By the late 2000s it carried both a long institutional history and the more recent task of serving prospects who were choosing between a traditional college, a polytechnic, and the trades-and-technology niche RCC actually occupied.

This was the WordPress front-end build for RCC during the Yorkville education group’s late-2000s technology integration. It sat on the same Moodle online-learning layer and the same custom Student Information System that served the group’s four schools across New Brunswick and Ontario. The companion portfolio entry for Yorkville University describes that broader architecture.

Where the WordPress front end meets Moodle and the SIS A layered system architecture. Above a dashed public boundary sits the public web: a prospective student reaches a copper-outlined WordPress front-end layer, the part this build owned, containing outcomes-led program pages and a per-program intake funnel for each technology stream. Below the boundary sit two shared systems the front end fed: Moodle, the group’s shared online-learning layer, and a custom Student Information System. The intake funnels hand into the SIS, tagged by technology stream; the front end also links out to the shared Moodle layer. Both systems were shared across the group’s four schools in New Brunswick and Ontario. INSIDE THE YORKVILLE STACK Where the WordPress front end meets Moodle and the SIS Copper is the public build I owned. Behind the boundary sit the shared systems it fed. Prospective student WordPress front end Program pages graduate-outcomes led Per-program intake funnels one funnel per technology stream THE PUBLIC BOUNDARY links out to the shared LMS intake handed to the SIS, tagged by technology stream Moodle Shared online-learning layer (LMS) Custom SIS Student Information System feeds admissions advisors One of four schools sharing Moodle and the SIS across New Brunswick and Ontario
I built the public WordPress front end, and its per-program intake funnels handed cleanly across the boundary into the shared SIS while the site linked out to the group's Moodle.

A front end that had to earn the long history

An institution that has been training Canadian technologists since 1928 is in a different position from a startup college trying to claim a place in the market. The front end had to read as serious about its lineage without feeling stuck in it: current in what it taught, current in how the prospective student experienced the site, but visibly grounded in a tradition the newer competition didn’t have. Program pages led with what graduates went on to do, because the trades-and-technology prospect tends to evaluate a college by where its graduates work rather than by how its brochure is laid out.

Per-program intake funnels handed cleanly into the custom SIS, so an admissions advisor could pick up the conversation already knowing which technology stream the prospect had been reading about. The publishing rhythm and the admin patterns matched the other three schools in the group, so a marketing or admissions coordinator could move between sites and find the controls where they expected them. A prospect reading the electronics-program page never had to think about the platform underneath, which is what an institutional site is for.

  • Platform: WordPress, custom theme
  • Period: 2008–2009, during the Yorkville group’s integrated technology build
  • Role: Director of Technology, Yorkville University, leading the technology team responsible for all four schools’ digital surfaces
  • Context: One of four institutions sharing a Moodle LMS and a custom Student Information System across two provinces

Where this pattern transfers

Any heritage-institution college: trades, technology, applied sciences, agriculture, has a similar buyer task. The website has to honour the lineage without becoming a museum piece, and it has to make the graduate-outcomes case directly because that is the case the prospect is actually evaluating. Whether the records system feeding admissions is unique to the institution or shared with a sister college matters far less than whether the front-end story matches what the prospect’s career-changer ear is listening for.

Working through something on your own site? Get in touch →