Tightknit Companion Site Update - June 21, 2024

June 21, 2024

Reading time: 2 minutes

Tightknit Release Notes (June 21, 2024) Finer Profile Field Controls You now have two ways display profile fields for members on your companion site. Each field can either be "Public" or "Restricted to Members". Public fields are shown to all visitors of the site. Fields that are Restricted to Members will display "🔒 Restricted to Members" for the field value to all visitors of the site, except for authenticated users (coming soon). Fields that are not designated in either category will not appear on the companion site at all. Updates:

When an Event is completed, a reminder is sent to the event owner to add a recap, and the Event announcement message(s) are updated to remove registration buttons
Added option to send notification DM to all event participants when a recap is added
The "About" section of a user's profile is no longer shown if no profile fields are synced to the companion site
Changed default event registration button text from ✅ I'm interested to ✅ Register
Improved sitemap for events on companion site
Now, when a user first installs the app, we create the Community automatically to reduce onboarding time

Fixes:

Fixed Events page layout bug on Safari
Fixed aspect ratio for Event thumbnails when resizing window
Fixed empty/blank updates to profile fields not reflecting on companion site profiles

3

4 comments

· Sorted by Oldest

Scott B.
·
·
Great changes! Appreciate the events fixes too! Would still love to see an option where folks can indicate if they want to be in the directory or not. My thought is a profile field in Slack, default is on, option is turn off.
👍1
Zach H.
·
·
Scott B., I don’t promise this will be the route we’ll take for profile visibility, but I have some follow-up questions just in case it is. Today, profile fields cannot be boolean values, so what would you expect the profile field to be? Would the field be named profile-visibility? Just doing diligence so we can weigh our options on this ticket
Scott B.
·
·
Stephen C. We have a profile field today which uses selectable options. In this case Yes or No. Example attached. I was thinking we might be able to use that field type, user selected, to drive the preference for the user. Overall, anything user related, I'd prefer to be in the hands of users, not us, especially when that information is PII.
Loading attachments
👍1
Zach H.
·
·
It makes sense. I’ll have to ponder a bit more how it could work architecturally
👍1

— Read More —

Tightknit Release Notes: Companion Site Customization and New Features (May 15, 2024)

2 min read

Stephen C.

May 15, 2024 10:28 PM

Tightknit Platform Update: Companion Site Now Optional

1 min read

Stephen C.

Apr 25, 2024 05:54 PM

Tightknit Release Notes: Site-wide User Display Name Settings & Event Updates

1 min read

Stephen C.

Jul 11, 2024 10:22 PM

Tightknit Platform Release Notes - June 6, 2024: Feed Updates and Event Fixes

1 min read

Stephen C.

Jun 06, 2024 02:08 PM

Scott B.
·
·
Great changes! Appreciate the events fixes too! Would still love to see an option where folks can indicate if they want to be in the directory or not. My thought is a profile field in Slack, default is on, option is turn off.
👍1
Zach H.
·
·
Scott B., I don’t promise this will be the route we’ll take for profile visibility, but I have some follow-up questions just in case it is. Today, profile fields cannot be boolean values, so what would you expect the profile field to be? Would the field be named profile-visibility? Just doing diligence so we can weigh our options on this ticket
Scott B.
·
·
Stephen C. We have a profile field today which uses selectable options. In this case Yes or No. Example attached. I was thinking we might be able to use that field type, user selected, to drive the preference for the user. Overall, anything user related, I'd prefer to be in the hands of users, not us, especially when that information is PII.
Loading attachments
👍1
Zach H.
·
·
It makes sense. I’ll have to ponder a bit more how it could work architecturally
👍1