Alternate hashtags to allow different content and actions

[daaronr]

I'm thinking some people might only want to see the summary content; others (especially our team) may want more detailed updates. This may also be relevant for #5 different platforms (e.g., Substack may permit longer-form).

Could we have

1. The original hashtag we used cues an action to push content to the 'basic' set of locations (e.g., the core email list)
2. If we use a different 'detailed content' hashtag it only pushes it to a different set of locations (e.g., emails for people who are on our team)

?

If this is easy to do (otherwise we can postpone this for later)

[fernandosmither]

Definitely!

Lets do it this way. Assuming we're always just sending the diff from updated files, lets have a set of defined flags, template and recipients. Add them to the Wiki and ping me so I can create them this week.

Right now we have:

Flag	Template	Recipients
#PushNewsletter	10073313	test

[daaronr]

What does 'test' mean above?

For now, as a useful MWE of a second flag, let's have the flag #PushManagementTeam send emails to the management team segment (1083513).

[fernandosmither]

What does 'test' mean above?

For now, as a useful MWE of a second flag, let's have the flag #PushManagementTeam send emails to the management team segment (1083513).

It's on the wiki. But answering your question, test is the test segment we created that only emails us for now.

It would be the third one on the picture below