How m-files/vaf.extensions.community works
Key Components to Include:
Core Framework Layer
• ConfigurableVaultApplicationBase at the center as it's the main entry point
• Inheritance from MFiles.VAF.ConfigurableVaultApplicationBase
Supporting Systems
• Logging framework
• Email handling
• Resource management
• Directive processing
Layered Structure (from top to bottom)
• [Client Applications]
• ↓
• [ConfigurableVaultApplicationBase]
• ↓
• [Core Services Layer]
• Configuration Management
• Dashboard System
• Task Queue Management
• Extension Methods
• ↓
• [Supporting Infrastructure]
Integration Points
• Clear interfaces between components
• Extension points for customization
• Where vault applications can hook into the framework
Configuration System with
• Upgrade rules
• JSON conversion
• Validation components
Dashboard System showing
• Content renderers
• Command resolution
• Asynchronous operations
Task Queue Management
• Background operations
• Task processing
• Queue management
• Clear symbols for interfaces, abstract classes, and concrete implementations
• Community-contributed components
• Version-specific features
• Test coverage scope
Remember to include a note about the community-driven nature of the project and that it extends the base M-Files Vault Application Framework functionality.