Migration Documentation Archive¶

Documentation about the repository separation strategy and S5 client cleanup migration.

About¶

This archive contains documentation about the strategic migration of S5 Slidefactory from a monolithic application to a thin Azure client using the slidefactory-core package.

Migration Timeline¶

November 2025: Repository separation and S5 client cleanup

• Split monolithic S5 repository into:
• slidefactory-core: Core platform package (reusable across clients)
• s5-slidefactory: Thin Azure client for SportFive
• eddy-slidefactory: Thin client for Eddy (planned)

Key Documents¶

Repository Separation¶

• Repository Separation Implementation Guide - Complete guide for separating repositories
• Repository Separation Quick Reference - Quick reference for repository structure

Core Migration¶

• Core Migration Phase 1 Complete - Initial core package setup
• Core Migration CLI Plan - CLI command migration strategy
• Core Documentation Setup - Core repository documentation

Client Setup¶

• Eddy Client Setup Plan - Plan for Eddy client
• Eddy Client Setup Status - Eddy client progress

Migration Benefits¶

1. Code Reusability: Core functionality shared across all clients
2. Independent Branding: Each client can have custom branding
3. Simplified Maintenance: Bug fixes in core benefit all clients
4. Easier Testing: Core package tested independently
5. Clean Separation: Client-specific configuration separate from core logic

Current Status¶

Completed: - Core package created and published - S5 migrated to use core package - Documentation reorganized - CI/CD updated for both repositories

Active: - S5 running in production using slidefactory-core v1.0.8

Note¶

These are archived migration documents for historical reference. For current S5 documentation, see:

• User Guide
• Azure Infrastructure
• Configuration
• Operations

For core platform development, see the slidefactory-core repository.