Getting Started

Configuration

Administration

Modules

Templates

Integrations

Development

Getting Started

  • πŸ‘‹ Introduction
    High-level overview of UNA CMS: what it is, who it’s for, and what you can build.

  • βš™οΈ How UNA Works
    Explains the underlying architecture and relationship between front-end, Studio (admin console), and apps.

  • [πŸ’‘ Key Concepts][key-concepts]
    Covers essential terminology (Profiles, Context Modules, Permissions, etc.) that power UNA.

  • πŸ“• Glossary
    Alphabetical reference for important UNA terms.

  • ✊ Principles
    The guiding philosophies behind UNA development and community management.

  • [πŸ’» System Requirements][system-requirements]
    Details on hosting environment, server configuration, and prerequisites.

  • [πŸš€ Installation & Setup][installation-setup]
    Step-by-step instructions for installing UNA on various platforms (shared hosting, VPS, Docker, etc.).

  • [πŸƒ Quick Start Tutorial][quick-start-tutorial]
    A hands-on approach to spin up a basic UNA site with minimal configuration.

  • [πŸ“‹ Launch Checklist][launch-checklist]
    A structured guide (43 steps or more) to configure essentials before going live.

  • [❓ General FAQ][general-faq]
    Frequently asked questions for newcomers.

Building & Managing Your UNA Site

  • [πŸ”§ Studio Basics][studio-basics]
    How to navigate and use Studio: Pages, Forms, Navigation, Permissions, Languages, etc.

  • [πŸ“‘ Site Structure][site-structure]
    Understanding page layouts, blocks, and how modules interact.

  • πŸ—‚ Content Management
    Managing posts, media, categories, and moderation workflows.

  • [πŸ‘€ User & Profile Management][user-profile-management]
    Handling user accounts, profiles, activation, and roles.

  • [πŸ”’ Permissions & Roles][permissions-roles]
    Configuring membership levels, access controls, and custom permissions.

  • [🏷 Customization & Theming][customization-theming]
    Applying templates/themes, styling pages, and basic design tweaks.

  • [πŸ”€ Navigation & Menus][navigation-menus]
    Configuring menus, site navigation, and user interface structure.

  • [πŸ’¬ Language & Translations][language-translations]
    Setting default languages, editing language keys, and creating multilingual sites.

  • [πŸ”” Notifications][notifications]
    Customizing email templates, push notifications, and in-site alerts.

  • [πŸ›  Maintenance & Upgrades][maintenance-upgrades]
    Updating UNA core and apps, backups, cron tasks, and overall site health.

  • [πŸ“ˆ Analytics & Reporting][analytics-reporting]
    Integrating external analytics, built-in stats, and best practices for measuring growth.

Apps (Modules)

Click to expand all official UNA Inc apps

  • Core β€œContext” Modules

    • [Groups][app-groups]
    • [Events][app-events]
    • [Spaces][app-spaces]
    • [Organizations][app-organizations]
    • [Channels][app-channels]

  • Core β€œContent” Modules

    • [Posts][app-posts]
    • [Discussions][app-discussions]
    • [Albums][app-albums]
    • [Photos][app-photos]
    • [Videos][app-videos]
    • [Files][app-files]
    • [Wiki][app-wiki]
    • [Polls][app-polls]
    • [Blogs][app-blogs]

  • Communication & Messaging

    • [Messenger (Jot Server)][app-messenger]
    • [Conversations / Chat+ (if separate)][app-chatplus]

  • Membership & Monetization

    • [Paid Levels][app-paid-levels]
    • [Market][app-market]
    • [Ads][app-ads]
    • [Payments][app-payments]

  • Engagement & Interaction

    • [Timeline (Feed)][app-timeline]
    • [Reactions][app-reactions]
    • [Comments][app-comments]
    • [Notifications][app-notifications]

  • Administration & Utilities

    • [Permissions][app-permissions]
    • [Developer][app-developer]
    • [Helpdesk][app-helpdesk]
    • [Maintenance Tools][app-maintenance-tools]

  • E-Learning & Specialized

    • [Classes][app-classes]
    • [Courses (if separate)][app-courses]

Remote Storage

Remote storage engine allows to store files on remote storage. For now the following storage engines are supported:

  • Local - files are stored locally in storage folder
  • S3 - Amazon S3 compatible storage with signature v2 authorisation
  • S3v4 - Amazon S3 compatible storage with signature v4 authorisation
  • S3v4alt - Amazon S3 compatible storage with signature v2 or v4 authorisation, use this storage only when others don't work, since it reuploads file to the storage when file privacy is changed, when v4 signature is used then it will work with Amazon S3 storage only, if other than Amazon S3 storage is used then it will switch to v2 anyway.

Storage engine can be changed in Studio > Settings > Storage:

  • Default storage engine - storage engine to use by default, when changing this setting, then storage engine is changed for storage objects which don't have any files uploaded, if storage object has some files uploaded then manual files transfer to the new storage engine is required, after manual transfer is completed then manually change engine for the storage object in engine field in sys_objects_storage table. Note that when transferring data from Local to S3 or S3v4 you need to make all files public to make it accessible, however all newly uploaded files will be marked as private for private ones.
  • AWS access key - access key provided by storage engine, for S3, S3v4 and S3v4alt only.
  • AWS secret key - secret key provided by storage engine, for S3, S3v4 and S3v4alt only.
  • AWS bucket - bucket name, for S3, S3v4 and S3v4alt only.
  • AWS custom domain - custom domain to use for file URLs, requires proper DNS setup on your custom domain, leave empty for default domain from particular storage engine, for S3 and S3v4 only.
  • Endpoint - particular storage endpoint domain, for Amazon leave empty, for Google storage use storage.googleapis.com for Wasabi storage use s3.wasabisys.com, for S3, S3v4 and S3v4alt only.
  • Signature version - signature version, for S3v4alt only, S3 supports only v2, S3v4 supports only v4.
  • Region - region, such as us-east-1, for S3v4 and S3v4alt only.

Not all storage providers works with all storage engines, here is a table to show which one to use:

Provider S3 S3v4 S3v4alt(v2) S3v4alt(v4)
Amazon OK (some regions FAIL) OK (some regions FAIL) OK (some regions FAIL) OK
Google OK FAIL FAIL FAIL
Wasabi OK OK OK FAIL

How to generate keys: