Update workspace management to add impacted stakeholders

[klaraavo]

Also removing the "and event variants" here – this is more high level and I don't think we need to differentiate between the two or require the user to parse that concept on this page

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 18, 2024 11:56am

[klaraavo]

@logason I'm rejecting your changes to add a bunch of "and variants" to the copy here. Fundamentally, a variant IS an event, just a different shape of it. This article is more high-level and I don't want to complicate things with Avo features or functionalities that people might not get yet. It also just makes the copy more clunky. WDYT

[hugihlynsson]

📝 Changed routes:

…ace-management/domains
(view full size)

Commit cf83045d5bb6d5f9f4e20b20d01b4d34384070ba (https://docs-c1fsrgbxg.avo-dev.app).

[bragur]

I have to admit I find it slightly exclusive not mentioning variants, because event though, as you say, they are fundamentally just another event, at the moment we don’t recognize them as such in the UI, i.e. in the Events sheet. For now, I think it would be more useful to keep it in the copy but we could make a slight adjustment and say events and their variants instead of events and variants. I think that encompasses the meaning of what a variant is at the same time as including them.

[logason]

I have to admit I find it slightly exclusive not mentioning variants, because event though, as you say, they are fundamentally just another event, at the moment we don’t recognize them as such in the UI, i.e. in the Events sheet. For now, I think it would be more useful to keep it in the copy but we could make a slight adjustment and say events and their variants instead of events and variants. I think that encompasses the meaning of what a variant is at the same time as including them.

+1, at least I think it's very important we make it clear this functionality is available on variants somehow

[klaraavo]

My take is that this is mentioned everywhere on the actual page for domain stakeholders. So it is covered in more detail where relevant but I don't think we need to mention it in every single place as it just makes the text harder to read. Making a suggestion with a compromise:

• We add it in at the top of the article, saying Events (including event variants) and link to event variants in the text
• We add it in the section for attaching events to domains

@logason could you re-review?