Project Context

ABN AMRO uses Planon for workplace-service processes such as:

• parking reservations
• furniture requests
• meeting-room bookings
• other internal workplace workflows

Those forms can require custom JavaScript behavior.

The original problem

When JavaScript is maintained independently across many forms, the same problems repeat:

Form A ──┐
Form B ──┼── duplicated helpers
Form C ──┤   repeated fixes
Form D ──┘   inconsistent behavior

That creates friction in four places:

Problem	Effect
Duplication	Shared behavior gets copied into multiple forms
Maintenance	One fix may need to be repeated in several places
Consistency	Similar forms can drift into different implementations
Deployment	Changes become harder to release in a controlled way

The design goal

I approached the project as two connected systems:

1. Centralize the JavaScript

shared behavior
      +
form-specific logic
      ↓
one managed library

2. Build a secure delivery platform

repository
   ↓
Azure DevOps
   ↓
Test
   ↓ approval
Acceptance
   ↓ approval
Production

The result was a platform that connected frontend architecture, cloud infrastructure, security and delivery automation instead of treating them as separate problems.