Tightknit Release Notes: Enhancements for Journeys and Internal Pages
Reading time: 2 minutes
Tightknit Release Notes (Jan 29, 2025)
Tightknit Release Notes (Jan 29, 2025)
@here
⏱️ Time-Bound Journeys
We've made a few changes to the relationship of Milestones and Journeys and gave Journeys a powerful boost. Journeys are now our first-class citizen for gamification. All Milestones must be a part of a Journey.Journeys can now be time-bound to a specific Completion Window for your members. Only actions performed by members within this time interval will count towards Milestones in the Journey. You can leave the end date blank in order to keep the window open indefinitely.Need some setup time to prep your Journey? No worries! We've also added an activate/deactivate feature in order to launch the Journey once it is ready. Once active, the Journey will be visible to your members. Note that the Journey must both be active and be within the completion window in order for your members to make progress. Read more⬈
📄 Internal Embedded Pages
Last time we released custom navigation items in the site sidebar. If you add a URL slug to the configuration, such as Terms of Service | [https://example.com](https://example.com) | terms-of-service
, something magical happens ✨...When you include a slug, a custom internal page is added to the site that contains an embed of the specified URL. This is a powerful feature that lets you embed your external resources directly in the companion site, such as your main site's Terms of Service page, your community calendar, etc! Read more⬈
Updates:
[Slack] Added pagination to the Events List modal
[Slack] Increased character limit for Journey and Milestone names
[Slack] Members receive a private ephemeral notification when completing a Journey in a channel (if applicable)
[Slack] Changed order of Gamification module on app home
Fixes:
[Slack] Fixed bug where image settings would be reset when modals with file uploads were submitted (i.e. affecting badge create/edit, event create/edit, etc)
[Slack] Replaced error warnings with more accurate descriptions when using the Manage Content shortcut on invalid message threads
[API] Fixed examples in the API docs for events-related APIs