Community Infrastructure Migration

[Arlodotexe]

Overview

Comprehensive tracking issue for migrating from old backend infrastructure to new SDK-based system.

Background

From our planning consolidation (originally posted in `#staff-chat` and `#community-infra`):

#community-infra has progressed far enough that we can start implementing our code requirements for the Appathon. We need to close off #15 and consolidate our existing plans.

All docs from our old Wiki repo have been ported to the new meta repo. I have my high-level bearings on everything we need to complete for us to migrate away from the old backend.

Related Components

This issue tracks the following component migrations:

• Database Migration #18
• Hosting, Backup and Fallback Planning #19
• Appathon Event Tooling #20
• IPNS/IPLD/Unixfs path handling investigation #17
• Server Companion + Community SDK Integration WindowsAppCommunity.Discord.ServerCompanion#22
• Blog Generator Tooling (existing Planning static blog page generator for windowsappcommunity.com #12)
• Entity Profile Tooling (existing Planning generated SDK entity profile pages for windowsappcommunity.com #14)

Website Tooling Components

• Blog tooling - Static blog page generator for windowsappcommunity.com
• SDK entity profile website tooling - Registered projects showcase

Server Companion Components

• Non-SDK features - Bot improvements not requiring SDK integration
• SDK integration - Core SDK integration with sub-features:
  • CLI to Slash Commands
  • Backlinking and Invites System
  • User Isolation and Repository Ownership
  • Discord Roles Migration
  • Flexible Permissions System

Timeline

Our collectively promised deadline was "Summer 2025" but scheduling within that depends on individual capability and capacity. Task mapping to people will be determined once all components are properly broken down into manageable tickets.

Next Steps

1. Create individual tracking issues for each major component
2. Establish dependency relationships between components
3. Map tasks to team members based on capability and capacity
4. Begin implementation in dependency order, work in parallel where possible.

This issue will be updated with links to all component issues as they are created.