Skip to main content

What I Built

My work on the project spanned frontend architecture, cloud infrastructure, CI/CD and developer enablement.

Ownership map​

┌───────────────────────────────┐
│ JavaScript platform           │
│ shared + form-specific code   │
└───────────────┬───────────────┘
                │
                ▼
┌───────────────────────────────┐
│ Runtime loading               │
│ loader + context resolution   │
└───────────────┬───────────────┘
                │
                ▼
┌───────────────────────────────┐
│ Shared runtime utilities      │
│ functions + timing control    │
└───────────────┬───────────────┘
                │
                ▼
┌───────────────────────────────┐
│ Azure infrastructure          │
│ Blob + Private Endpoint       │
│ provisioned with Bicep        │
└───────────────┬───────────────┘
                │
                ▼
┌───────────────────────────────┐
│ Azure DevOps CI/CD            │
│ Test → Acc → Prod             │
└───────────────┬───────────────┘
                │
                ▼
┌───────────────────────────────┐
│ Developer documentation       │
│ Docusaurus walkthrough        │
└───────────────────────────────┘

JavaScript architecture​

I designed the centralized library structure used to separate reusable functionality from form-specific logic.

Dynamic loading​

I worked on the lightweight loader that identifies the active Planon context and loads the required scripts.

Shared utilities​

I created and organized reusable helpers, including timing control for asynchronously rendered Planon elements.

Azure infrastructure​

I provisioned the storage and private networking infrastructure using Bicep, including a Private Endpoint.

CI/CD​

I implemented the Azure DevOps delivery flow across Test, Acceptance and Production, with automatic Test deployment and approval-controlled promotion.

Documentation​

I built the Docusaurus documentation site so other developers could understand the architecture, shared functions and deployment lifecycle.

Development span​

6 months

The value of the project came from connecting all of these layers into one system, not from any single file or Azure resource.