How kong/konnect-portal works
Main Components
a. Frontend Architecture (Core):
• Vue.js Application Layer
• Views Layer (src/views/*)
• Components Layer (src/components/*)
• Store Layer (src/stores/*)
• Router Layer (src/router/*)
• Services Layer (src/services/*)
b. External Services:
• Kong Konnect Backend API
• Authentication Services
• Portal API Service
• LaunchDarkly Feature Flags Service
Key Architectural Elements
a. Client-Side Architecture:
• Core Components
• Authentication Flow
• API Documentation Rendering
• Application Management
• Analytics Components
b. Data Flow Layers:
• API Services Layer
• State Management Layer (Pinia Stores)
• Component Communication Layer
• Internationalization System
Specific Implementation Details
[Frontend Application]
• Core Components
• Authentication (AuthCard, Login, Registration)
• API Documentation (ApiDocumentation/, Spec Renderer)
• Application Management (Applications/)
• Analytics (vitals/)
• Service Layer
• AuthApiService
• PortalV2ApiService
• SessionCookie
• State Management
• App Store
• i18n Store
• Permissions Store
• Product Store
• External Services
• Kong Konnect API
• Feature Flags Service
• Authentication Provider
Interaction Flows
• User authentication flow
• API documentation retrieval
• Application registration process
• Analytics data flow
• Internationalization content delivery
Technical Stack Indicators
• Vue.js
• Vite
• TypeScript
• Cypress
• Pinia (State Management)
• Kong Konnect Integration
Integration touchpoints with Kong Konnect
Keep the abstraction level high enough to be understandable but detailed enough to show the important architectural decisions and patterns used in the application.
Remember to highlight the self-hosted nature of the application and its customization capabilities, as these are key features mentioned in the README.