Specialist depth · Articulate Rise

Making Rise more distinctive, reusable and governed.

Rise is fast because it is deliberately constrained. That is useful until an organisation needs a recognisable visual language, repeatable interaction patterns, accessible components and standards that survive beyond one course. I design the reusable system around the tool so teams can keep its speed without accepting every default.

The constraint

Fast to build. Easy to make interchangeable.

Rise's speed comes from a fixed set of blocks and a shared visual language. Across a programme or organisation, courses can start to look interchangeable and production standards can drift because recurring decisions have nowhere shared to live.

The useful response is not to fight Rise. It is to decide which constraints are helpful, then build a reusable layer of design, interaction and production governance around the places where the defaults are not enough.

Beyond theme customisation

Build the reusable rules around the tool.

The work connects the neutral eLearning Design System to branded production implementations. ISQ is one important implementation context: its brand and course requirements consume the core patterns and components without defining the core system itself.

Design systems

Reusable component libraries, interaction patterns, typography, spacing, accessible colour, layouts, image standards and content patterns create a shared production language rather than a collection of one-off courses.

  • Reusable component libraries
  • Branded implementation layers
  • Consistent typography and spacing
  • Accessible colour systems
  • Reusable layouts
  • Image standards
  • Content and interaction patterns

Technical enhancement

Custom HTML blocks, external CSS and reusable interaction patterns can extend Rise without making every course a bespoke software project. The guiding rule is to use the least complex implementation that fully supports the learning purpose.

  • Custom HTML blocks
  • External CSS architecture
  • Reusable interaction library
  • Accessible components
  • Responsive layouts
  • Reusable templates
  • xAPI statement integration where default telemetry is not meaningful enough

The useful deliverable is not only the course in front of you. It is a system the next course can inherit.

A strong Rise engagement should leave the organisation with more than a finished course. It should leave reusable decisions that improve the work that follows.

Outcomes

What this changes

  • Stronger visual and interaction consistency across a course suite
  • A more recognisable experience than the default Rise theme alone can provide
  • Reusable decisions that reduce repeated course-level design work
  • Easier maintenance because shared rules can be updated centrally
  • Accessible patterns designed into components rather than added after production
  • Clearer governance so quality depends less on who builds the next course

Adoption and efficiency claims need evidence; this page describes the production intent rather than inventing marketing numbers.

Work to inspect

eLearning Design System

How it holds together

  1. Foundations
  2. Learning patterns
  3. Components
  4. Platform implementation
  5. Governance

Design system · Independent Schools Queensland

eLearning Design SystemIndependent Schools QueenslandEducation · professional learning

Turning course-level solutions into a shared organisational system

A live framework connecting learning patterns, visual foundations, reusable components, Rise implementation, accessibility and governance across ISQ's digital learning.

  • Design systems
  • Platforms
  • Learning experience
  • Production systems

Explore the live system

Need Rise to do more?

If the requirement is a flagship course, a reusable component system or a wider production standard, I can help work out what should stay native to Rise and what genuinely needs extending.

Discuss a Rise project

Read how the practice works