Auto Batch Lock
User journey and system logic for automatic batch locking.
User journey and system logic for automatic batch locking.
Platform architecture and logic for scheduled tasks.
Platform architecture and logic for batch UI locking functionality.
User journey and system logic for coach session requests.
Enriched API documentation with examples for creating batches.
This journey walks through the GrowthKit batch editor: opening a batch from a program configuration, adjusting batch settings and the program schedule, configuring surveys when enabled, coordinating coach dates, sharing the overview, managing participants, and publishing or unpublishing.
Internal team how-to guide for CRM integration.
Technical guides for engineers who contribute to the DeepSkill platform and its documentation. This section complements Features, Processes, and User Journeys, which are aimed at product and operations teams.
This guide explains how technical process documentation works in the DeepSkill docs repo and gives a step-by-step workflow for developers who add or extend a process.
Platform architecture and logic for frontend feature triggers.
Internal team how-to guide for module management.
User journey and system logic for module reminders.
This hub groups process documentation for turning a GrowthKit program configuration into confirmed settings, batches (learning groups), and publish / lifecycle behaviour on the backend. Use it when you work across confirmation, handover, publish, and batch locking.
Enriched API documentation with examples for requesting sessions.
Internal team how-to guide for setting up batches.
Platform architecture and logic for Strapi CMS extensions.
This section documents how Team Learning (and, where noted, Team Sales) staff use internal tools—starting with GrowthKit—to configure programs, manage batches, and support operations.
Application repositories ship one tested release per week. Feature work is integrated on staging, exercised there, and promoted to production together. Urgent fixes between those releases use a hotfix-* branch cut from production.