Documents
Plugn Repositories – Priority & Status
Plugn Repositories – Priority & Status
Type
Document
Status
Published
Created
Nov 5, 2025
Updated
Nov 5, 2025
Updated by
Dosu Bot

Repository Classification

Core (must be set up)

  • plugn
    This is the main codebase and central to the platform, likely containing the core backend, frontend modules, APIs, models, and documentation. It is essential for the initial setup and operation of the main product.

Supporting (used by some features)

  • plugn-microservices
    This repository likely provides microservices that extend the core platform with additional features or integrations. It is not strictly required for basic operation but is important for enabling certain advanced or modular functionalities.

  • plugn-dashboard-ionic
    This repository appears to provide a dashboard or frontend interface, likely for administrative or analytics purposes. It supports the main platform but is not required for the core setup.

  • plugn-ionic
    This repository is likely a client-facing or mobile application built with the Ionic framework, supporting user interaction with the platform. It is not essential for the backend or core platform operation.

  • plugn-store-sdk
    This repository likely provides SDKs for integrating with the store or platform APIs, enabling developers to build custom integrations or extensions. It is useful for some features but not required for the core system.

  • plugn-device
    This repository appears to provide device-specific plugins or integrations, supporting hardware or IoT features. It is not essential for the core platform but may be required for specific device-related use cases.

  • plugn-store
    This repository likely contains the main eCommerce store functionality for the platform. While important for store-related features, it is considered supporting unless the primary use case is eCommerce.

Auxiliary/legacy (can be ignored in onboarding)

  • plugn-store-community
    This is labeled as a community version and is likely an older or less critical version of the main store platform. It can generally be ignored during onboarding unless there is a specific need to support legacy or community-driven deployments.