Architecture

Each Datso component owns its own tables, administrator forms, site views, and service classes. Integration happens through shared user accounts, menu routing, extension records, protected downloads, payment state, and documentation links.

Component boundaries

• DatsoGallery owns gallery media, image display, categories, comments, reports, members, tags, uploads, favorites, and gallery search.
• DatsoShop owns commerce catalog and order workflows.
• DatsoHub owns customer portal workflows: subscriptions, licenses, protected downloads, payments, support tickets, API, webhooks, mail, and push notifications.
• DatsoDocs owns product documentation and should replace previous Joomla article based docs structures.

Frontend principle

Frontend output should inherit the active template. Component templates should avoid hard-coded visual systems that conflict with DatsoLumina tokens, typography, buttons, forms, and card styles.