How sparkdevnetwork/slingshot works
Main Components
a. Source Systems Layer:
• Separate modules for each supported system:
• CCB (Church Community Builder)
• F1
• ACS
• PCO (Planning Center Online)
• Breeze
• ServantKeeper
• ElexioCommunity
b. Core Processing Layer:
• Slingshot.Core module
• Data transformation utilities
• Model mapping system
c. Export Layer:
• .slingshot file generator
• Rock import format handler
Component Relationships
[Source Systems] → [Translators] → [Core Processing] → [Export Layer] → [.slingshot file]
Detailed Component Breakdown
a. For each source system module, show:
• API/Database connectors
• Authentication handlers
• Data extractors
• System-specific translators
b. For the Core Processing layer, show:
• Model definitions (from Slingshot.Core/Models)
• Data transformation utilities
• Validation handlers
• Extension methods
c. For the Export layer, show:
• File format handlers
• Data serialization
• Import package creation
Key Integration Points
Highlight:
• API interfaces (CcbApi.cs, F1Api.cs, etc.)
• Model translators (in each source system's Translators folder)
• Core data models (in Slingshot.Core/Models)
Technical Details
Specific components for:
• WPF UI interfaces (MainWindow.xaml, Login.xaml)
• Authentication handlers
• Data transformation utilities
• File format processors
Architecture Patterns
Emphasize:
• Modular design (separate projects for each source system)
• Common core library (Slingshot.Core)
• Translator pattern implementation
• Extension method utilities
Export Generation
• Component types
• Data flow directions
• Integration points
• File formats
This system design should emphasize the extensible nature of the platform, showing how new source systems can be added while maintaining the core processing and export functionality.
Remember to include notes about the Creative Commons ShareAlike license requirements, as this is an important aspect of the project's architecture and usage terms.