Seeking feedback: Improving the Atlas update composer

[#1]

Hi community! 

I'm Rachel, a product manager on Atlas and I'm back seeking some more feedback from this group. We're currently exploring how to strengthen the experience of writing an update in Atlas, so that it is easier for a project owner to curate their updates and resultantly, be a more meaningful update for followers to consume.

We know status reporting sucks - so how might we make it a better experience overall for you? 

We'd love your feedback on the problem space and some early conceptual designs. If you have some time, please take a look at the Loom and drop your reactions and comments inline in the video (only 7 minutes long!): 

https://www.loom.com/share/2023-Sep-13-Update-Composer-community-feedback-212cda3bf9c74f51ac1a751658685464?sid=1a8d7e67-8b60-4508-87c5-ce3f47894dd7

We really appreciate it and hope you enjoy getting a peek into the early thinking process! 

[Amanda Barber]

This was a great way to provide a peek at what's to come! 

[Ruby]

These look like helpful improvements but they don't address our biggest pain point which is the updates always being on Friday. Admins should be able to to change the default update day so that people are prompted at the right time, and so that updates are distributed when they are most needed.