LearnCard Documentation
GithubStatusSupportLaunch App
  • 🚀Introduction
    • What is LearnCard?
    • Use Cases & Possibilities
    • Ecosystem Architecture
  • ⚡Quick Start
    • Setup & Prerequisites
    • Your First Integration
  • 📚Tutorials
    • Create a Credential
    • Create a Boost
    • Create a ConsentFlow
    • Create a Connected Website
    • Send xAPI Statements
    • Listen to Webhooks
  • ✅How-To Guides
    • Verify My Issuer
    • Connect Systems
      • Connect a Website
      • Connect a Game
    • Implement Flows
      • Claim Data after Guardian Consent
      • Connect via CHAPI
        • ⭐CHAPI Wallet Setup Guide
        • ↔️Translating to CHAPI documentation
        • 🖥️Demo Application
        • 🔰Using LearnCard to Interact with a CHAPI Wallet
        • 📝Cheat Sheets
          • Issuers
          • Wallets
    • Deploy Infrastructure
      • Remote Key Management
      • Generate API Tokens
      • Signing Authority
      • Connect to Independent Network
      • Build a Plugin
  • 🛠️SDKs & API Reference
    • LearnCard Wallet SDK
      • Authentication
      • Usage Examples
      • SDK Reference
      • Plugin API Reference
      • Integration Strategies
      • Deployment
      • Troubleshooting
      • Changelog
    • LearnCloud Network API
      • Authentication
      • Usage Examples
      • Architecture
      • Notifications & Webhooks
      • Profiles
      • Profile Managers
      • Credentials
      • Boosts
      • Presentations
      • Storage
      • Contracts
      • DID Metadata
      • Claim Hooks
      • Auth Grants
      • Utilities
      • Models
      • OpenAPI
    • LearnCloud Storage API
      • Authentication
      • Usage Examples
      • Architecture
      • Storage
      • Index
      • User
      • Custom Storage
      • Utilities
      • Models
      • xAPI Reference
    • Plugins
      • Crypto
      • DIDKit
      • DID Key
      • Dynamic Loader
      • VC
        • Expiration Sub-Plugin
      • VC-Templates
      • VC-API
      • Ceramic
      • IDX
      • VPQR
      • Ethereum
      • CHAPI
      • LearnCard Network
      • LearnCloud
      • LearnCard
      • Simple Signing
      • Claimable Boosts
    • LearnCard CLI
  • 🧠Core Concepts
    • Identities & Keys
      • Decentralized Identifiers (DIDs)
      • Seed Phrases
      • Network Profiles
      • Signing Authorities
      • Trust Registries
    • Credentials & Data
      • Verifiable Credentials (VCs)
      • Credential Lifecycle
      • Schemas, Types, & Categories
      • Building Verifiable Credentials
      • Boost Credentials
      • Getting Started with Boosts
      • Credential URIs
      • xAPI Data
      • General Best Practices & Troubleshooting
    • Consent & Permissions
      • ConsentFlow Overview
      • Consent Contracts
      • User Consent & Terms
      • Consent Transactions
      • Auto-Boosts
      • Writing Consented Data
      • Accessing Consented Data
      • GameFlow Overview
    • Network & Interactions
      • Network Vision & Principles
      • Key Network Procedures
      • Core Interaction Workflows
    • Architecture & Principles
      • Control Planes
      • Plugin System
      • Auth Grants and API Tokens
  • 🔗Development
    • Contributing
Powered by GitBook
On this page
  • What is this section about?
  • Why is this important for you to understand?
  • What you'll learn:
  • 🧱 Modular & Extensible by Design
  • 🎯 User-Centric & Principled Foundation

Was this helpful?

  1. Core Concepts

Architecture & Principles

Overall LearnCard philosophy, Plugin system, Control Planes

What is this section about?

This section offers a high-level view of the LearnCard system's design, its core architectural components, and the guiding philosophies that shape its development and functionality. It's about the "big picture" of how LearnCard is built and why it's designed the way it is.

Why is this important for you to understand?

Understanding the overall architecture, the design principles (like the "LearnCard philosophy"), how the system is made extensible (through the "Plugin system"), and its main operational components (like "Control Planes") helps you make more informed decisions when building with or extending the platform. It allows you to align your own development with the system's capabilities and anticipate its behavior. This is like understanding a city's master plan, its key infrastructure, and its zoning laws to see how everything fits together.

What you'll learn:

You'll gain insights into the foundational design choices of LearnCard, how its plugin architecture enables flexibility, and the roles of major internal components like Control Planes.


🧱 Modular & Extensible by Design

LearnCard is architected with modularity and extensibility as core tenets. This approach ensures the platform is adaptable and can evolve to meet diverse needs. Key aspects include:

  • Plugin System: Allows for new features and integrations to be added without altering the core, fostering a flexible ecosystem.

  • Component-Based: Built from distinct components (like Control Planes), promoting separation of concerns and easier maintenance.

  • Adaptability: Designed to support a wide array of use cases by allowing customization and extension.

This design makes LearnCard robust, maintainable, and ready for future innovations.

🎯 User-Centric & Principled Foundation

Our architectural decisions are driven by a strong philosophy centered on key principles that ensure LearnCard is a trustworthy and empowering platform:

  • User Sovereignty: Empowering individuals with control over their data and digital identity.

  • Security & Privacy by Design: Integrating security and privacy considerations into every layer of the architecture.

  • Openness & Interoperability: Committing to open standards to ensure broad compatibility and prevent vendor lock-in.

  • Decentralization: Leveraging decentralized technologies where they enhance user control, security, and resilience.

These principles guide the development of LearnCard, aiming to create a fair and transparent digital credentialing ecosystem.

PreviousCore Interaction WorkflowsNextControl Planes

Last updated 10 days ago

Was this helpful?

🧠