Processes & Workflows - Overview
Document Purpose
This documentation suite establishes the development processes and workflows for the Kinana Content Hub platform. This section and its subsections outline the Ibtikar development workflow, code review process, change and release management procedures for the platform.
Platform Context
Kinana is a content hub platform enabling educational content management and delivery across multiple media types.
Technical Architecture
- Framework: ABP.io (backend) + Angular (frontend)
- Infrastructure: Microsoft Azure, Kubernetes, Docker
- Architecture Pattern: Microservices + Micro Frontends
- Version Control: Enterprise GitHub (22 repositories)
Platform Components
- Shell: Core application container
- Library: Document management sub-app
- Videos: Video content management
- Podcasts: Podcast content management
- Brokkly: Visual coding platform
Development Status
- Current Version: 1.0 (pre-production)
- Target Production Date: Q4 2025
- Current Environment: Development → Staging
Team Structure
| Role | Responsibility |
|---|---|
| Product Manager | Feature prioritization, stakeholder alignment |
| QA / Project Manager | Quality assurance, sprint coordination |
| Solution Architect | Technical direction, code review approval |
| Senior Developer | Implementation, peer review |
Note: Team recently transitioned from contractor support (3 senior developers offboarded).
Development Methodology
Agile Development with 2-week sprint cycles managed through GitHub Projects (Kanban board).
Core Ceremonies
- Daily Standups: Issue resolution and deployment coordination
- Bi-monthly Sprint Planning: Task prioritization and sprint commitment
- Sprint Reviews: Demo and stakeholder feedback
- Retrospectives: Process improvement
Branching Strategy
- Development Branch: Active development target
- Staging Deployment: Automated from dev branch
- Production: Not yet established (pending client project)
Process Documentation Structure
This documentation is organized into four key areas:
- Development Workflow: Sprint-based development lifecycle
- Code Review Process: Quality gates and approval requirements
- Change Management: Framework for production changes (future state)
- Release Management: Version control and release coordination
Guiding Principles
- Code as Documentation: Self-documenting code practices preferred
- Peer Collaboration: Knowledge sharing through code walkthroughs
- Quality First: Local testing before staging deployment
- Continuous Improvement: Regular retrospectives and process refinement
Document Maintenance
These documents reflect processes as of November 2025. Updates should be proposed through the standard development workflow and approved by the Solution Architect.
Last Updated: November 2025
Version: 1.0