Process Docs for Virtual Coffee Newsletter #412
Conversation
|
@adiati98 Working on making the newsletter process more visible, including tracking the info through an issue template (which should make it easier to do the PR to the website later) Let me know if this format fits in with the other doc projects. I've kept it all in one file for now but we can split up the content if we think it'll be easier for people. |
There was a problem hiding this comment.
@tkshill I really like this! Thank you!❤️
This format fits with the workflow to put the newsletter on the website. I normally will see how it looks best and easier to navigate on the website based on the email. So, there are a few of newsletters that have slight different appearance (headings, etc.) than on the email.
I think it's okay to have everything in one place because everything is in the flow. But we might want to consider having Table of Contents to make it easier for folks to navigate between sections.
Out of this PR but still related, because I've been working on putting the newsletter on to the website, can I be an Archivist? 😁
But I'm totally up to help other tasks for the newsletter whenever needed. ✨
| - label: All fields have been reviewed by editor for content, tone, accuracy, and completeness. | ||
| - label: Newsletter issue has been reviewed on launching platform for visual consistency. |
There was a problem hiding this comment.
question: As the initial issue submitter will be a Reporter, should these labels be filled by Editor?
suggestion: If so, we might want to add an info here, something like "To be filled by Editor".
There was a problem hiding this comment.
@tkshill just to make sure, based on your recent changes, these fields would all be filled by the Editor, right?
Co-authored-by: Ayu Adiati <[email protected]>
|
@BekahHW Do you see anything missing that we might want with the new Beehiv setup? |
resolves #411
Adds the following files: