From 5c25e90f0518ec7e08b9532b53675f1113533e12 Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Mon, 3 Jun 2024 15:25:11 -0600 Subject: [PATCH 01/12] Init newsletter.yml issue setup --- .github/ISSUE_TEMPLATE/newsletter.yml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/newsletter.yml diff --git a/.github/ISSUE_TEMPLATE/newsletter.yml b/.github/ISSUE_TEMPLATE/newsletter.yml new file mode 100644 index 00000000..07b06c94 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/newsletter.yml @@ -0,0 +1,14 @@ +name: "Monthly Newsletter Preparation Docs" +description: "Track the collection of relevant items for the Virtual Coffee monthly newsletter" +title: "VC Newsletter: {MMMM} - {yy}" +assignees: + - tkshill +labels: ["Newsletter"] +body: + - type: input + attributes: + label: Email Title + - type: input + attributes: + label: Email Subheader + From c5487cffe57996a2e0093106c22ac6a0725277a8 Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Mon, 3 Jun 2024 16:01:21 -0600 Subject: [PATCH 02/12] newsletter issue template --- .github/ISSUE_TEMPLATE/newsletter.yml | 101 ++++++++++++++++++++++++-- 1 file changed, 96 insertions(+), 5 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/newsletter.yml b/.github/ISSUE_TEMPLATE/newsletter.yml index 07b06c94..34da54a8 100644 --- a/.github/ISSUE_TEMPLATE/newsletter.yml +++ b/.github/ISSUE_TEMPLATE/newsletter.yml @@ -5,10 +5,101 @@ assignees: - tkshill labels: ["Newsletter"] body: + - type: markdown + attributes: + value: | + ## Monthly Newsletter Preparation Docs + + Use this issue to track the collection of relevant items for the Virtual Coffee monthly newsletter. This issue will live in the Newsletter project and help us work toward organizing everyone for publication day. - type: input - attributes: - label: Email Title + attributes: + label: Year + description: The year for which this newsletter is being prepared + placeholder: "2024" + validations: + required: true + - type: dropdown + attributes: + label: Month + description: The month for which this newsletter is being prepared + multiple: false + options: + - "January" + - "February" + - "March" + - "April" + - "May" + - "June" + - "July" + - "August" + - "September" + - "October" + - "November" + - "December" + default: 0 + validations: + required: true - type: input - attributes: - label: Email Subheader - + attributes: + description: What our recipients will see as the subject line of the email + label: Email Subject + - type: input + attributes: + label: Email Subheader + description: A brief subheader to the subject line, providing a bit more context or detail. + - type: textarea + attributes: + label: Email Introduction + description: A brief introduction to the recipient, with a brief synopsis of the month's major events and themes. + - type: textarea + attributes: + label: Gratitude Shoutouts + description: Shoutouts from community members to other community members or groups for suppor they've received or work they've done. + - type: textarea + attributes: + label: Recap + description: A brief recap of the last month's major events, themes, and milestones. + - type: textarea + attributes: + label: Upcoming Events + description: A list of upcoming events, including dates, times, and any other relevant information. + - type: textarea + attributes: + label: Community News and Monthly Challenge + description: Any news or updates from the community, including new members, new projects, or other relevant information. Monthly challenges should be included here. + - type: textarea + attributes: + label: Events + description: A list of events that are schedules to occur in the next month, including dates, times, and any other relevant information. + - type: textarea + attributes: + label: Member Content Highlights + description: A list of content created by community members that has been highlighted or featured in the last month. + - type: textarea + attributes: + label: Member Wins + description: A list of wins or accomplishments from community members in the last month. + - type: textarea + attributes: + label: Member Content Projects + description: A list of projects that community members are working on, including any relevant links or information. + - type: textarea + attributes: + label: Open Source Projects + description: A list of open source projects that community members are working on or VC endorses, including any relevant links or information. + - type: checkboxes + id: qa-checklist + attributes: + label: QA checklist + description: "Check off/fill in the items below as they are received/updated. Any notes or attachments should be added as comments on the issue." + options: + - label: All fields have been filled in. + - 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. + - type: markdown + attributes: + value: "### Additional Info" + - type: markdown + attributes: + value: | + Any additional discussion, information or attachments should be added as comments on this issue. From 60169675f4155f9efce4b12646aab30a6a0b7b0f Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Mon, 3 Jun 2024 16:03:46 -0600 Subject: [PATCH 03/12] fixed extra field --- .github/ISSUE_TEMPLATE/newsletter.yml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/newsletter.yml b/.github/ISSUE_TEMPLATE/newsletter.yml index 34da54a8..b96f082d 100644 --- a/.github/ISSUE_TEMPLATE/newsletter.yml +++ b/.github/ISSUE_TEMPLATE/newsletter.yml @@ -59,10 +59,6 @@ body: attributes: label: Recap description: A brief recap of the last month's major events, themes, and milestones. - - type: textarea - attributes: - label: Upcoming Events - description: A list of upcoming events, including dates, times, and any other relevant information. - type: textarea attributes: label: Community News and Monthly Challenge From d57e86abf23a565b4a597e4aa2e1571177b72ed9 Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Mon, 3 Jun 2024 16:46:20 -0600 Subject: [PATCH 04/12] added section for podcast --- .github/ISSUE_TEMPLATE/newsletter.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/newsletter.yml b/.github/ISSUE_TEMPLATE/newsletter.yml index b96f082d..3b75177d 100644 --- a/.github/ISSUE_TEMPLATE/newsletter.yml +++ b/.github/ISSUE_TEMPLATE/newsletter.yml @@ -54,7 +54,7 @@ body: - type: textarea attributes: label: Gratitude Shoutouts - description: Shoutouts from community members to other community members or groups for suppor they've received or work they've done. + description: Shoutouts from community members to other community members or groups for suppor they've received or work they've done. We use FIRST NAMES ONLY here to preserve member privacy. - type: textarea attributes: label: Recap @@ -67,6 +67,10 @@ body: attributes: label: Events description: A list of events that are schedules to occur in the next month, including dates, times, and any other relevant information. + - type: textarea + attributes: + label: Podcast Episodes + description: A list of podcast episodes that have been released in the last month, including any relevant links or information. - type: textarea attributes: label: Member Content Highlights @@ -74,7 +78,7 @@ body: - type: textarea attributes: label: Member Wins - description: A list of wins or accomplishments from community members in the last month. + description: A list of wins or accomplishments from community members in the last month. We use FIRST NAMES ONLY here to preserve member privacy. - type: textarea attributes: label: Member Content Projects From e25423dc5a3acd1e0c1114fac5d2c964adf6ccd9 Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Mon, 3 Jun 2024 16:59:48 -0600 Subject: [PATCH 05/12] newsletter readme page --- newsletter/README.md | 138 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 138 insertions(+) create mode 100644 newsletter/README.md diff --git a/newsletter/README.md b/newsletter/README.md new file mode 100644 index 00000000..f3f20322 --- /dev/null +++ b/newsletter/README.md @@ -0,0 +1,138 @@ +Welcome to the Virtual Coffee Newsletter docs! **Thank you all for supporting Virtual Coffee!** + +## What is the Virtual Coffee Newsletter? + +The Virtual Coffee Newsletter is a monthly publication that shares updates, news, and resources from the Virtual Coffee community. + +The newsletter is created by the Newsletter Team Leads and our Maintainers. + +The newsletter is shared with the Virtual Coffee community via email and is also available on the [Virtual Coffee website](virtualcoffee.io.) + +The newsletter is typically published on the first Monday of each month. The newsletter is usually put together in the week leading up to publication. + +>[!NOTE] +> A word on platform. The newsletter is currently published using Mailchimp, however, the platform may change in the future. These docs have purposefully been written to be platform-agnostic. Platform specific instructions may be added in the future by the newsletter team. + +## What Roles are Required for the Newsletter? + +The following roles are required for the newsletter: + +### Newsletter Team Lead(s) + +The team lead is responsible for coordinating the newsletter team, setting deadlines, and ensuring the newsletter is published on time. They oversee all aspects of the newsletter creation process and report to the Communications Maintainer. The team lead gives the final approval for the newsletter before release. They support the other members of the team in helping them complete their tasks and ensure the newsletter is of high quality. + +### The Editor + +The editor is responsible for editing the newsletter content, ensuring it is clear, concise, and free of errors. The editor works closely with the team lead and contributors to ensure the newsletter is of high quality. The editor checks both the content of the newsletter and also the design, accessibility, and formatting of the final publication. The editor also coordinates with other relevant contributors to ensure content is accurate and up-to-date. + +### Reporters + +Reporters are members of the Virtual Coffee community who submit content for the newsletter. Reporters can submit articles, updates, resources, and other content for consideration in the newsletter. Reporters work with the team lead and editor to ensure their content is suitable for publication. + +### Designer + +The designer is responsible for creating the visual design of the newsletter. The designer works with the editor and team lead to create a visually appealing and accessible publication. The designer ensures the newsletter is easy to read, engaging, and shares the design principles of Virtual Coffee. + +### Engineer + +The engineer ensures the content distribution process is working correctly. They ensure the newsletter can be easily edited, and modified, and that the publication process is smooth. The engineer works with the team lead and editor to ensure the newsletter is published on time and without errors. They may develop tools, automations, or processes to streamline the newsletter creation process. + +## Who do I contact if I have questions about the newsletter? + +If you have questions about the newsletter, please reach out to the Newsletter Team Leads or the Communications Maintainer. They can help you with any questions you may have about the newsletter, the publication process, or how to contribute. + +## How can I contribute to the newsletter? + +If you would like to contribute to the newsletter, please reach out to the Newsletter Team Leads or the Communications Maintainer. You can submit articles, updates, resources, or other content for consideration in the newsletter. You can also volunteer to help with editing, design, or engineering tasks. + +## Newsletter Creation Procedure + +The newsletter creation process typically follows these steps: + +### Step 1: Issue Creation +The Editor creates the next month's newsletter issue in the contributors repository right after the current month's newsletter is published. This issue has a template with the sections that need to be filled in. + +### Step 2: Content Submission +The Reporters submit content for the newsletter in the issue discussion thread. The Editor and Team Lead review the content and provide feedback if necessary. At the time of writing this guide, there are several recurring content sections which get updated each month. These include: + +#### Meta Text + +This includes the email Header, Subheader, and Introduction. Typically written by the Editor, this section welcomes readers to the newsletter and provides an overview of the content. Usually mentions the monthly challenge and a call to action. + +#### Recap of last Month + +A summary of the last monthly challenge and any major community highlights + +#### Current Monthy Challenge + +A description of the current monthly challenge, with a link to the challenge page on the website and any other relevant resources. Coordination with the Monthly Challenge Team is required to obtain this information. + +#### Upcoming Events + +A list of upcoming events, workshops, and other community activities. Coordination with the Events Team is required to obtain this information. + +#### Gratitude Shoutouts + +A list of shoutouts from the community to other members. These are typically submitted by members and are included in the newsletter to show appreciation for the community. Usually sourced from the community Slack, especially the #gratitude, #happiness, and #general channels during async check-ins. + +#### Weekly Events + +A summary of the weekly events that are going to take place in the community. This includes a summary of the weekly check-ins, coffee table groups, and other community activities. Coordination with the Events Team is required to obtain this information. + +#### Member Wins + +A list of member wins from the community. These are typically submitted by members and are included in the newsletter to celebrate the achievements of the community. Usually sourced from the community Slack, especially the #goals-and-wins channel during async check-ins. + +#### Member Content + +A list of content created by members of the community. This includes blog posts, podcasts, videos, and other content. Members can submit their content for inclusion in the newsletter. Usually sourced from the community Slack, especially the #member-content channel. + +### Podcast Episodes + +A list of podcast episodes featuring members of the community. This includes episodes of the Virtual Coffee Podcast and other podcasts that feature Virtual Coffee members. Coordination with the Podcast Team is required to obtain this information. + +### Step 2.5: Less Frequent Content + +Some content sections are not updated typically updated every month because they change less frequently or are dependent on external factors. These include: + +#### VC Affiliated Open Source Projects + +A list of open-source projects affiliated with Virtual Coffee. This includes projects that are maintained by Virtual Coffee members or are related to the community in some way. Coordination with the Open Source Team is required to obtain this information. Typically edited and updated during the Virtual Coffee Hacktoberfest Initiative, or at the request of a member*. + +>[!NOTE] +> Any open source project featured here **must** be approved by the VC team according to our open source checklist and guidelines. + +#### Member Ongoing Initiatives + +A list of ongoing initiatives by members of the community. This includes projects, collaborations, and other activities that members are working on. Members can submit their initiatives for inclusion in the newsletter. Usually sourced from member requests or proposed additions by the newsletter team. + +>[!NOTE] +> The above sections are subject to change and may be updated based on community feedback and needs. The Editor and Team Lead will work with the community to ensure the newsletter content is relevant and engaging. + +### Step 3: Content Review and Editing + +The Editor reviews the content submitted by the Reporters and provides feedback. The Editor ensures the content is clear, concise, and free of errors. The Editor also ensures the content is suitable for publication and aligns with the Virtual Coffee values and guidelines. + +### Step 4: Upload Content to Newsletter Platform + +The Engineer uploads the content to the newsletter platform. The Engineer ensures the information has been placed in the correct sections and that the newsletter is ready for publication. + +### Step 5: Design and Layout + +The Designer makes any necessary design changes to the newsletter. This includes any styling, layout, or visual elements that need to be added. + +### Step 6: Final Review + +The Editor reviews the final version of the newsletter to ensure it is ready for publication. The Editor checks for any errors, inconsistencies, or other issues that need to be addressed. Once done, the Editor hands is off to the Team Lead for final approval. + +### Step 7: Publication + +The Team Lead gives the final approval for the newsletter to be published. The Engineer publishes the newsletter on the designated date and time. The newsletter is shared with the Virtual Coffee community via email and is also available on the Virtual Coffee website. + +- +## Additional Notes + +### Member Privacy + The newsletter team must respect the privacy of all Virtual Coffee members. Personal information should not be shared in the newsletter without the explicit consent of the member. If you are unsure about whether something should be included in the newsletter, please reach out to the Communications Maintainer for guidance. Every member has the right to privacy and should feel safe and respected in the Virtual Coffee community. Any member can request that their information not be included in the newsletter. + +### From 50e8d2f5dae5572ad75a8953b10e12939a60c561 Mon Sep 17 00:00:00 2001 From: tkshill Date: Mon, 3 Jun 2024 23:00:11 +0000 Subject: [PATCH 06/12] Prettified Code! --- newsletter/README.md | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/newsletter/README.md b/newsletter/README.md index f3f20322..4593cd51 100644 --- a/newsletter/README.md +++ b/newsletter/README.md @@ -10,7 +10,7 @@ The newsletter is shared with the Virtual Coffee community via email and is also The newsletter is typically published on the first Monday of each month. The newsletter is usually put together in the week leading up to publication. ->[!NOTE] +> [!NOTE] > A word on platform. The newsletter is currently published using Mailchimp, however, the platform may change in the future. These docs have purposefully been written to be platform-agnostic. Platform specific instructions may be added in the future by the newsletter team. ## What Roles are Required for the Newsletter? @@ -50,14 +50,16 @@ If you would like to contribute to the newsletter, please reach out to the Newsl The newsletter creation process typically follows these steps: ### Step 1: Issue Creation + The Editor creates the next month's newsletter issue in the contributors repository right after the current month's newsletter is published. This issue has a template with the sections that need to be filled in. ### Step 2: Content Submission + The Reporters submit content for the newsletter in the issue discussion thread. The Editor and Team Lead review the content and provide feedback if necessary. At the time of writing this guide, there are several recurring content sections which get updated each month. These include: #### Meta Text -This includes the email Header, Subheader, and Introduction. Typically written by the Editor, this section welcomes readers to the newsletter and provides an overview of the content. Usually mentions the monthly challenge and a call to action. +This includes the email Header, Subheader, and Introduction. Typically written by the Editor, this section welcomes readers to the newsletter and provides an overview of the content. Usually mentions the monthly challenge and a call to action. #### Recap of last Month @@ -97,16 +99,16 @@ Some content sections are not updated typically updated every month because they #### VC Affiliated Open Source Projects -A list of open-source projects affiliated with Virtual Coffee. This includes projects that are maintained by Virtual Coffee members or are related to the community in some way. Coordination with the Open Source Team is required to obtain this information. Typically edited and updated during the Virtual Coffee Hacktoberfest Initiative, or at the request of a member*. +A list of open-source projects affiliated with Virtual Coffee. This includes projects that are maintained by Virtual Coffee members or are related to the community in some way. Coordination with the Open Source Team is required to obtain this information. Typically edited and updated during the Virtual Coffee Hacktoberfest Initiative, or at the request of a member\*. ->[!NOTE] +> [!NOTE] > Any open source project featured here **must** be approved by the VC team according to our open source checklist and guidelines. #### Member Ongoing Initiatives A list of ongoing initiatives by members of the community. This includes projects, collaborations, and other activities that members are working on. Members can submit their initiatives for inclusion in the newsletter. Usually sourced from member requests or proposed additions by the newsletter team. ->[!NOTE] +> [!NOTE] > The above sections are subject to change and may be updated based on community feedback and needs. The Editor and Team Lead will work with the community to ensure the newsletter content is relevant and engaging. ### Step 3: Content Review and Editing @@ -115,11 +117,11 @@ The Editor reviews the content submitted by the Reporters and provides feedback. ### Step 4: Upload Content to Newsletter Platform -The Engineer uploads the content to the newsletter platform. The Engineer ensures the information has been placed in the correct sections and that the newsletter is ready for publication. +The Engineer uploads the content to the newsletter platform. The Engineer ensures the information has been placed in the correct sections and that the newsletter is ready for publication. ### Step 5: Design and Layout -The Designer makes any necessary design changes to the newsletter. This includes any styling, layout, or visual elements that need to be added. +The Designer makes any necessary design changes to the newsletter. This includes any styling, layout, or visual elements that need to be added. ### Step 6: Final Review @@ -127,12 +129,14 @@ The Editor reviews the final version of the newsletter to ensure it is ready for ### Step 7: Publication -The Team Lead gives the final approval for the newsletter to be published. The Engineer publishes the newsletter on the designated date and time. The newsletter is shared with the Virtual Coffee community via email and is also available on the Virtual Coffee website. +The Team Lead gives the final approval for the newsletter to be published. The Engineer publishes the newsletter on the designated date and time. The newsletter is shared with the Virtual Coffee community via email and is also available on the Virtual Coffee website. + +- -- ## Additional Notes ### Member Privacy + The newsletter team must respect the privacy of all Virtual Coffee members. Personal information should not be shared in the newsletter without the explicit consent of the member. If you are unsure about whether something should be included in the newsletter, please reach out to the Communications Maintainer for guidance. Every member has the right to privacy and should feel safe and respected in the Virtual Coffee community. Any member can request that their information not be included in the newsletter. -### +### From 9bd1a5d9aef12b1bbcbcf6d706eab7fb7b1825a8 Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Mon, 3 Jun 2024 17:03:29 -0600 Subject: [PATCH 07/12] small copy edits --- newsletter/README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/newsletter/README.md b/newsletter/README.md index 4593cd51..2a08b50b 100644 --- a/newsletter/README.md +++ b/newsletter/README.md @@ -19,7 +19,7 @@ The following roles are required for the newsletter: ### Newsletter Team Lead(s) -The team lead is responsible for coordinating the newsletter team, setting deadlines, and ensuring the newsletter is published on time. They oversee all aspects of the newsletter creation process and report to the Communications Maintainer. The team lead gives the final approval for the newsletter before release. They support the other members of the team in helping them complete their tasks and ensure the newsletter is of high quality. +The team lead is responsible for coordinating the newsletter team, setting deadlines, and ensuring the newsletter is published on time. They oversee all aspects of the newsletter creation process and report to the Communications Maintainer. The team lead gives the final approval for the newsletter before release. They support the other members of the team in helping them complete their tasks and ensure the newsletter is of high quality. The team lead can recommend other members of the community in the newsletter creation process as needed. ### The Editor @@ -137,6 +137,7 @@ The Team Lead gives the final approval for the newsletter to be published. The E ### Member Privacy - The newsletter team must respect the privacy of all Virtual Coffee members. Personal information should not be shared in the newsletter without the explicit consent of the member. If you are unsure about whether something should be included in the newsletter, please reach out to the Communications Maintainer for guidance. Every member has the right to privacy and should feel safe and respected in the Virtual Coffee community. Any member can request that their information not be included in the newsletter. +The newsletter team **must** respect the privacy of all Virtual Coffee members. Private information of any individual should not be shared in the newsletter without the _explicit consent of the member_. If you are unsure about whether something should be included in the newsletter, please reach out to the Communications Maintainer for guidance. Every member has the right to privacy and should feel safe and respected in the Virtual Coffee community. + +Any member can request that their information not be included in the newsletter. -### From fc9422366bce7b2dc3dfba6c274966a960cd998f Mon Sep 17 00:00:00 2001 From: tkshill Date: Mon, 3 Jun 2024 23:04:54 +0000 Subject: [PATCH 08/12] Prettified Code! --- newsletter/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/newsletter/README.md b/newsletter/README.md index 2a08b50b..9c893bb5 100644 --- a/newsletter/README.md +++ b/newsletter/README.md @@ -137,7 +137,6 @@ The Team Lead gives the final approval for the newsletter to be published. The E ### Member Privacy -The newsletter team **must** respect the privacy of all Virtual Coffee members. Private information of any individual should not be shared in the newsletter without the _explicit consent of the member_. If you are unsure about whether something should be included in the newsletter, please reach out to the Communications Maintainer for guidance. Every member has the right to privacy and should feel safe and respected in the Virtual Coffee community. +The newsletter team **must** respect the privacy of all Virtual Coffee members. Private information of any individual should not be shared in the newsletter without the _explicit consent of the member_. If you are unsure about whether something should be included in the newsletter, please reach out to the Communications Maintainer for guidance. Every member has the right to privacy and should feel safe and respected in the Virtual Coffee community. Any member can request that their information not be included in the newsletter. - From bb480bda8a9efd337dd22614f418f81f10e1dc42 Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Mon, 3 Jun 2024 17:08:11 -0600 Subject: [PATCH 09/12] add note for push to website --- newsletter/README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/newsletter/README.md b/newsletter/README.md index 9c893bb5..9b11a977 100644 --- a/newsletter/README.md +++ b/newsletter/README.md @@ -37,6 +37,11 @@ The designer is responsible for creating the visual design of the newsletter. Th The engineer ensures the content distribution process is working correctly. They ensure the newsletter can be easily edited, and modified, and that the publication process is smooth. The engineer works with the team lead and editor to ensure the newsletter is published on time and without errors. They may develop tools, automations, or processes to streamline the newsletter creation process. + +### Archivist + +The archivist ensures the newsletter content is also shared on the Virtual Coffee website. The archivist works with the team lead and editor to ensure the newsletter is archived and accessible to the community. The archivist may also help with other tasks related to the newsletter publication process. + ## Who do I contact if I have questions about the newsletter? If you have questions about the newsletter, please reach out to the Newsletter Team Leads or the Communications Maintainer. They can help you with any questions you may have about the newsletter, the publication process, or how to contribute. @@ -131,7 +136,9 @@ The Editor reviews the final version of the newsletter to ensure it is ready for The Team Lead gives the final approval for the newsletter to be published. The Engineer publishes the newsletter on the designated date and time. The newsletter is shared with the Virtual Coffee community via email and is also available on the Virtual Coffee website. -- +### Step 8: Post-Publication + +The Newsletter content is also shared on the Virtual Coffee website. The Archivist submits a PR to the Virtual Coffee website repository to add the newsletter content to the website. ## Additional Notes From 2dbb8209655f0fd1c8c29d6ac430d46ddf40b978 Mon Sep 17 00:00:00 2001 From: tkshill Date: Mon, 3 Jun 2024 23:09:01 +0000 Subject: [PATCH 10/12] Prettified Code! --- newsletter/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/newsletter/README.md b/newsletter/README.md index 9b11a977..bc121dfa 100644 --- a/newsletter/README.md +++ b/newsletter/README.md @@ -37,7 +37,6 @@ The designer is responsible for creating the visual design of the newsletter. Th The engineer ensures the content distribution process is working correctly. They ensure the newsletter can be easily edited, and modified, and that the publication process is smooth. The engineer works with the team lead and editor to ensure the newsletter is published on time and without errors. They may develop tools, automations, or processes to streamline the newsletter creation process. - ### Archivist The archivist ensures the newsletter content is also shared on the Virtual Coffee website. The archivist works with the team lead and editor to ensure the newsletter is archived and accessible to the community. The archivist may also help with other tasks related to the newsletter publication process. @@ -138,7 +137,7 @@ The Team Lead gives the final approval for the newsletter to be published. The E ### Step 8: Post-Publication -The Newsletter content is also shared on the Virtual Coffee website. The Archivist submits a PR to the Virtual Coffee website repository to add the newsletter content to the website. +The Newsletter content is also shared on the Virtual Coffee website. The Archivist submits a PR to the Virtual Coffee website repository to add the newsletter content to the website. ## Additional Notes From b889fb20088cdb808e68259e84794eecaddc4766 Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Tue, 4 Jun 2024 07:09:46 -0600 Subject: [PATCH 11/12] Fix date placeholder formatting Co-authored-by: Ayu Adiati <45172775+adiati98@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/newsletter.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/newsletter.yml b/.github/ISSUE_TEMPLATE/newsletter.yml index 3b75177d..629c3ee5 100644 --- a/.github/ISSUE_TEMPLATE/newsletter.yml +++ b/.github/ISSUE_TEMPLATE/newsletter.yml @@ -1,6 +1,6 @@ name: "Monthly Newsletter Preparation Docs" description: "Track the collection of relevant items for the Virtual Coffee monthly newsletter" -title: "VC Newsletter: {MMMM} - {yy}" +title: "VC Newsletter: [MM] - [YYYY]" assignees: - tkshill labels: ["Newsletter"] From 94f22a7adbb805a49a635f52e74c74bc9b0220cc Mon Sep 17 00:00:00 2001 From: Kirk Shillingford Date: Tue, 4 Jun 2024 07:21:29 -0600 Subject: [PATCH 12/12] fixed QA checklist --- .github/ISSUE_TEMPLATE/newsletter.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/newsletter.yml b/.github/ISSUE_TEMPLATE/newsletter.yml index 629c3ee5..26ca0c89 100644 --- a/.github/ISSUE_TEMPLATE/newsletter.yml +++ b/.github/ISSUE_TEMPLATE/newsletter.yml @@ -93,9 +93,10 @@ body: label: QA checklist description: "Check off/fill in the items below as they are received/updated. Any notes or attachments should be added as comments on the issue." options: - - label: All fields have been filled in. - 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. + - label: Newsletter was successfully launched and successfully make it to subscribers' inbox + - label: Newsletter was uploaded to the virtualcoffee.io website. - type: markdown attributes: value: "### Additional Info"