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]

UNA Concepts

UNA CMS is based around a set of defined concepts. Before starting to work with UNA, it's a good idea to familiarise yourself with the following:

Content

User-generated content items like Posts, Videos, Discussions, Updates and Photos. Usually the Apps that allow publishing of content items are called Content Apps.

Context

Context refers to apps that can work as containers for content or context items from other apps. Groups, Spaces, Events are Context Apps. People and Organisations are Profile Apps and Context Apps, too.

Profiles

Profiles represent a user in the frontend. A profile is assigned a Membership Level and can perform actions based on the permissions granted to that level. Profiles can be administrators, moderators, standard members, or any custom level configured in the Permissions Builder.

Operators

Some accounts in UNA can be operators. Only operators have access to Studio. Operators can have their own roles, which define access to categories of apps in Studio. The full-access operator account is called "Master." Operator accounts can access site configuration; they don't need to have profiles.

Studio

Site configuration is done in UNA Studio. The Studio is a no-code interface designed for site operators. The Studio is intentionally separated from site administration and moderation, allowing for separation of concerns and greater operational scalability.

Apps

We call all UNA components apps. These may be content modules, context modules, profile modules, templates, language packs, service tools, integrations, and core apps. While we may use the word "apps" to refer to mobile applications or third-party software, generally in UNA, apps are the components within UNA CMS that can be found in Studio.

Pages

Pages represent data in the frontend. Page can have different page layouts, layouts consist of cells, cells contain blocks. All these is buildable using intuitive drag&drop interface.

Forms

Data in UNA is stored and displayed according to the structure defined by forms. Forms is actually a builder where you can add/edit/delete fields for different data.

Permissions

As a Community Management System, UNA heavily relies on its permissions system. Accounts and profiles are associated with membership levels that can be granted rights to perform specific actions. Membership levels are also used to define the visibility of menus, menu items, forms, form views, form fields, pages, blocks, contexts, and content instances.