hortus:communication:notifications
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| hortus:communication:notifications [2026/04/01 14:28] – created savino.frisardi | hortus:communication:notifications [2026/04/07 17:53] (current) – savino.frisardi | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| HORTUS includes a notification system to keep users informed. | HORTUS includes a notification system to keep users informed. | ||
| - | ---- | + | Notifications are the platform’s routing layer for recent activity. They are especially useful after comments, moderation changes, invitations, |
| - | ==== Notifications ==== | + | {{: |
| - | Notifications alert you about: | ||
| - | * comments in discussions | + | * Open notifications from the bell icon when you need to know what changed recently. |
| - | * updates | + | * Use Mark all as read to clear the visible unread state once you have processed the list. |
| - | * moderation results | + | * Use favourites to preserve a personal shortlist of people, projects, resources, tools, or saved searches. |
| - | * system events | + | * Use follows where available when you want updates |
| - | + | ||
| - | They help you: | + | |
| - | + | ||
| - | * resume work quickly | + | |
| - | * avoid missing important | + | |
| ---- | ---- | ||
| - | ==== Favourites ==== | ||
| - | Favourites allow you to: | ||
| - | * save items for quick access | ||
| - | * build a personal shortlist | ||
| - | |||
| - | Applicable to: | ||
| - | |||
| - | * resources | ||
| - | * projects | ||
| - | * experts | ||
| - | * events | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Follow ==== | ||
| - | |||
| - | Following an item means: | ||
| - | |||
| - | * you subscribe to updates | ||
| - | * you receive notifications when it changes | ||
| - | |||
| - | Typical use: | ||
| - | |||
| - | * tracking projects | ||
| - | * monitoring resources | ||
| - | * following experts | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Communication workflow ===== | ||
| - | |||
| - | A typical interaction flow: | ||
| - | |||
| - | * Discover a resource or project | ||
| - | * Evaluate content | ||
| - | * Ask a question (discussion) | ||
| - | * Contact user (messaging if needed) | ||
| - | * Follow item for updates | ||
| - | * Receive notifications | ||
| - | |||
| - | This creates a **continuous interaction loop**. | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Best practices ===== | ||
| - | |||
| - | * Use discussions for content-related questions | ||
| - | * Use messaging for private communication | ||
| - | * Follow items you care about | ||
| - | * Regularly check notifications | ||
| - | * Keep communication clear and contextual | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Summary ===== | ||
| - | |||
| - | HORTUS communication tools: | ||
| - | |||
| - | * support collaboration directly inside the platform | ||
| - | * keep discussions tied to content | ||
| - | * reduce reliance on external tools | ||
| - | |||
| - | Users can: | ||
| - | |||
| - | * communicate efficiently | ||
| - | * stay informed | ||
| - | * engage with research communities | ||
| - | |||
| - | ---- | ||
hortus/communication/notifications.1775046536.txt.gz · Last modified: by savino.frisardi
