Bring customers together around your project

Reusable AI instructions. A skill is linked to a profile; an explicit /skill-slug command activates the connected skill for an AI Chat request. The AI Chat workflow manages execution.

A typed profile value: text, number, date or boolean. For example, an expert's area of work.

Describes a field's name, type, prefix and suffix. Defines the label and display format of its value.

An event record with data and expiry. In AI Chat, it can hold a prepared view of the assistant's work, such as knowledge lookups. Execution rules remain in the coordinating module.

Blocks for displaying profiles and authors. They connect Social data with page presentation; conversation authorization stays in RBAC.

Name, avatar or initials, description, and counts of linked articles and products.

An author's name and description with linked Blog articles. Open a heading to read an excerpt.

Topics inside a chat. Choosing a thread changes the heading and displayed discussion excerpt.

Conversation and document side by side. On a narrow screen, switch between them. Try sending messages in the example above.

Account, current-user and conversation access checks. An account and a public profile are separate records.

Avatars and attachments. Social links files to profiles or messages.

Author articles. Linking a profile to articles creates a list of its publications.

Sources for the AI assistant. In ordinary AI Chat, search them by including @knowledge.

Products linked to an author or thread. Orders and payments additionally use Ecommerce and Billing.

For example: a member opens an expert's profile and asks a question about their project.

Decide what guests see, which actions require sign-in and who can read a particular conversation.

Use profiles, threads and messages. Connect only the materials, files or products you need.

Open a profile, start a conversation and return to its history. Check access from another account and the mobile display.

Show the page to someone from your audience. Ask what it offers and how to register. Compare their answer with what you intended to communicate.

Ask participants to reconstruct their actions: what they were looking for, where they stopped and what they expected after clicking. Record specific difficulties and check them in the next version.

Class 1: audience, product task and main use case. You will need a laptop and a project idea. The result is an initial brief.

Who the product is for, which problem it solves and what users should do in the first version. Search this knowledge by including @knowledge in a message.

Helps describe the product's audience, task and use case. Asks follow-up questions, then turns the answers into a brief.

Checks preparation against the course programme and lists remaining steps. Add @knowledge to the same request to search knowledge.