Observable

@maria -- For product updates: 
#1 New Teams setting to allow admins to choose the default visibility of notebooks created in the team -- both new notebooks as well as forks. Either the whole team has edit access, or it is private to the author.

See this github issue for more detailed description: https://github.com/observablehq/observablehq/pull/6937

#2 -- we will have "self service delete" by end of week. Documentation link here: https://observablehq.com/@observablehq/deleting-your-account

@maria -- Let me know if this is enough info for you to update the product section of the newsletter. I will double check that self-service delete feature has indeed been released  when I do a final pass.

Deepti Srivastava

@deepti Thank you! Very helpful.
I have some q's - please lmk if these q's are for you or someone else.

1. Default Visibility
1a. In the newsletter, do we ever link to the github issue, or is that private to Observable employees? 
1b. If we do not link to github issue, is there another notebook in the works to link to so that people can learn more? (or are both of these going to be in release notes, and I should link to that for both?)
1c. On the github issue, I see a helpful screen recording Cobus created. We can't include vids in the newsletter, but I'd like our community to see it. SO - if we don't link to the github issue, can we please include this vid in the "release notes"?

2. Self Service Delete
2a. In the newsletter, I've linked to the notebook indicated. Before the newsletter goes out, I'll confirm that all comments are deleted and the notebook is ready for community viewing. 
2b. This is a helpful feature. Also, we want to make clear that we'd like people to keep using Observable. I've framed like so: "Time to delete your current account and start a new one? That's now possible. Keep in mind that deleting your current account will remove you from any current teams of which you are a member!" 
What do you think?

Maria Ciampa

@virginiapoltrack Again - not a must-have. 
I was thinking for the UNAVCO & Observable section: it might be nice to have the quote in bold as an image. What do you think? it's by Brooks Mershon, Software Engineer

Of course! I love it, and that will only take a minute to put together :)

Virginia Poltrack

Ok turns out we will not be releasing #1 so let's remove for July

For #2 -- self service delete. Here is what I recommend: 
Users can now clean up their accounts (duplicate accounts, or accounts created in error) without requiring an email to support, making the overall process smoother and faster. Learn more here<link to notebook>.

Does this work?

@ananya -- are there any other issues that we closed that you want to highlight?

@deepti Thank you! This all makes sense. Edits made.

Thank you @maria! Can we move that section down towards the second half of the newsletter? I don't want us to lead with (minor) info. 

I'd rather we start with excel users followed by the unavco customer story.  And then we could have ambassadors, and then product update, community survey and end with hiring.

@deepti, you read my mind - the order of news was my next question. Thank you!

I wonder if the call to action for the UNAVCO piece could be something like: "Are you interested in speaking with the press about how your company uses Observable? If so, let us know!"

Clint Bagley

@clintbagley I like this idea. What about framing it this way? "Are you using Observable to help make sense of data at your workplace? If so, we'd love to hear about it. Email clint@observablehq.com" Open to edits!
cc: @buchman whaddaya think?