Private institutional systems

University Drupal Platform and CMS Framework

Krystian builds and maintains Drupal components, templates, modules, content models, and editor workflows for public university sites.

Internal Systems Active 2019 - Present
Read the case study
University of Arizona News homepage with featured and recent stories
Arizona News is one public surface supported by this active Drupal platform work. I built and maintained CMS patterns, components, modules, and implementation guidance across university sites.
  1. Content model
  2. Drupal template
  3. Frontend component
  4. Editor workflow
Content structure, rendering, reusable components, and editor behavior are handled as one CMS workflow.

Exact role

Senior Web Developer (CMS and platform engineering)

University of Arizona

Current status

Active

2019 - Present

Problem

What needed to change

University web properties needed reusable CMS, component, template, and workflow patterns so teams could ship and maintain content-heavy public sites without repeating engineering work.

Users

Who the system serves

Campus web teams, content editors, developers, communications teams, and public audiences using university web properties.

Team context

Where I fit

Worked with developers, campus web teams, communications teams, content editors, and public-site stakeholders.

Important technical decision

Connected content models, templates, components, documentation, and editor behavior instead of handling each request as isolated frontend work.

Tradeoff or limitation

Editor flexibility, accessibility, performance, and maintainability often pull in different directions; platform work requires balancing all four.

Implementation

What I personally owned

  • Built and maintained CMS framework patterns, templates, components, custom modules, Views integrations, and implementation guidance.
  • Built and supported public platform work including news.arizona.edu.
  • Contributed to the Arizona.edu homepage redesign using Single Directory Components.

Constraints

Hard parts that shaped the work

  • Content models had to support editor flexibility without making frontend behavior unpredictable.
  • Reusable platform work had to continue alongside production support for public sites.
  • One-off stakeholder requests had to be evaluated against patterns other developers and editors could reuse.

Current platform work

What exists now

  • CMS-integrated frontend patterns and Drupal-connected components.
  • Custom modules, Views integrations, AJAX-powered interfaces, templates, and paragraph-driven layouts.
  • Implementation guidance and documentation for campus web teams.
  • Production support across university web properties.

Result

Verified result and current state

  • The platform remains active across public university web properties.
  • Developers and editors have reusable templates, components, documentation, and content patterns for ongoing work.

Technical scope

Tools used

DrupalPHPViewsAJAXJSON:APIGraphQLReactTypeScriptTemplatesCMS content modeling