Use milo.adobe.com for updates communication

[elaineskpt]

Based in some discussions, we would like to used milo.adobe.com, more specific article-feed to share changes in blocks.
Right now we have a communication gap between dev changes and authors, this causes updates to be noted only when a block is used.

In place at the moment we have Slack notifications for high-impact changes, those are linked to the git. Our Idea would be to have a more visual and understandable update to non-tech users.

An sample done in the past and could be used as an idea is https://wiki.corp.adobe.com/pages/viewpage.action?spaceKey=adobedotcom&title=FEDS+News.

The goal is to have milo.adobe.com as one source of truth for the updates.

@narcis-radu @glasert

[overmyheadandbody]

I like the idea and GWP had good feedback for the Wiki page we've set up in the past outlining changes using "simple-speak" language. When do you envision this step happening during the release process? Before the change is pushed to production or after? If it's the former, we'd need a point of contact for someone that could do a write-up on the changes and this will add a bit of a bottleneck; the advantage is that we could already link the relevant GWP article in the PR, making things more traceable. If it's the latter, there will be a gap between feature release and authoring readiness.

Some filters or something similar might also be beneficial so that interested people can easily get to the latest changes from a particular block instead of scrolling through all the content.

It might be a good idea to set up a newsletter as well to outline the articles published in the last 2 weeks or so.

[mokimo]

we'd need a point of contact for someone that could do a write-up on the changes and this will add a bit of a bottleneck

We could alter our PR templates to auto generate release notes from. It should be a good sanity habit anyway to document any authoring related changes within a PR Imo. For substantial changes // net new blocks such as the notifications one, you could simply link to a new kitchen sink page

Authoring Changes

Add a description for any authoring related additions, changes or good to knows. Anything added here will end up in the release notes for GWP. For bigger changes, feel free to link to a new milo documentation page.

[mokimo]

Thinking about it, we'd also need to push the release notes somewhere - milo.adobe.com is a little inaccessible from git workflows, given content usually lives within sharepoint and we don't want to start writing into that from a workflow.

[overmyheadandbody]

I did think of this, but I think it's a bit "utopian" 😅 We've seen a lot of PRs where basic things are not provided, asking developers to provide authoring documentation will not be a general habit. Also, there is a communication gap between developers and authors, we need someone like @elaineskpt to bridge the gap.

[elaineskpt]

Hi @overmyheadandbody @mokimo
this is the basic set up
https://main--milo--adobecom.hlx.page/blog/ for article-feed

[elaineskpt]

adding the updates here as well

1. Set up is under: https://main/–milo–adobecom.hlx.page/blog/
2. We no longer use article-feed, the filter was not flexible for our use-case and code change would be needed.
3. We are using CaaS; Tags were added already for Milo Updates under (caas:milo-update-type) Tag Selector, covering milo-core and documentation.
4. Under Blog - Drafts we have 2 templates to be used drafts
5. Details how to share updates can be find under https://milo.adobe.com/blog/2024/08/27/new-milo-blog
6. Sample template for milo-core engineering updates were shared with Eng. and is under review/update on milo-core slack.