Marketing blog (P2) posts planning [Macro]

[abhansnuk]

(other than meeting notes and agendas)

To tie in with our discussion on planning posts / major blogs.

The spreadsheet probably needs reworking and a tab added for GitHub.

[abhansnuk]

GitHub error keeps unassigning people added to update the documentation on this area for future planning purposes.

[nalininsbs]

Done as part of migration:

• transferred with repo
• as board not updateable post transfer due to a bug, cards being transferred to Marketing Tasks board
• macro label added

To do:

• issue itself to be transferred as part of group when wiki / documentation is ready
• previous planner can be updated and linked to (to follow-up with Nicholas and Larissa)

[nalininsbs]

This transfer has not been successful and the documentation is missing. Reattempting the transfer.

[nalininsbs]

To assist the 2023 Marketing Team reps @sereedmedia @robinwpdeveloper @santanainniss with their onboarding and first month. I am copying below the information from the previous cards for organizational memory and help future progress and discussion on usage of the blog.

This card came from feedback from the team about having a place they could add suggestions for posts for the Marketing website.

In the longer past, Marketing posts were limited in what they could be on Marketing.

Below is the summary from older cards from the discussions in the team before and after the gathering of information from other teams and review for marketing posts.

It would be useful to have a clear and succinct explanation in the handbook of:

• what type of posts and subjects can be added to the Marketing blog (other than notes/ agendas and the routine posts)
• who does it, or for what topics does there need to be some kind of process, eg to avoid / be clear that it is not for a company posting something specific about a product launch or advertising
• when (a schedule of major campaign posts would be useful to avoid information overload or lots of feedback requests at the same time)
• recommending that posts for feedback give enough time for contributors in different timezones to respond and appreciating that not all contributors are online daily. Examples of short turnaround times were found in the research from other teams which may have been hard for contributors who have limited time they can give, particularly those who are not sponsored to work daily/ weekly in the team. Some contributors may also need time to translate the post before they feel fully able to respond
• not all contributors can use the comment facility in the Marketing blog due to accessibility barriers. This is where having an original GitHub card may assist and/or signposting who they can share their points with. Ideally, the accessibility issues will also reduce in time as, for example, dictation of text into the P2 has major issues including adding duplication of text in some instances; not all screen readers will read comment boxes
• how discussions on GitHub translate to a Marketing Team post. Reminding contributors to join up discussions by adding a link to the post on the relevant GitHub card [Trello reference removed], and summarizing any actions from the post before closing the GitHub card
• referring to some of the items in WordPress branding guide which team members contributed to about inclusive language, timezones in UTC etc.
• remembering that posts are also automatically sent out by the RSS feed, which has a very large audience. They are also regularly copied and reposted onto other websites. You can opt out of this facility per post, and there may be occasions where this may be appropriate
• being clear on what was a discussion, an idea, the equivalent of a 'blessed task', request for help, any deadlines (note there are differences where US puts month and day, and other places) and times in UTC, how it links into other parts of the project
• using tags effectively to help people find relevant content. Eg Marketing-Team for notes etc, Marketing for wider than the team
• x-posting to other teams sites only where relevant, not everything and adding a targeted note where helpful and if it is a specific call to that team
• adding an excerpt to particular posts to help search engines find the content and to summarize content for internal sharing/ Make WordPress blogs internal embedding of the link
• checking if the post is copied from an earlier version / an annual update, check the Slug and permalink.

Thank you to (I will edit names later if needed and add any others as close old tickets related to this): @murillol , @meherbala , @abhansnuk , @yvettesonneveld , @OlaIola , @vimes1984 , @courane01, Hauwa, Mike Reid, Maedah B, Harry, Mizanur, Ahmed Chaion, Estela, Mary B, who contributed to reviewing what worked well in other teams previously, learning points, and ideas to improve planning/ engagement.

@sereedmedia you may want to cross link this to the other handbook cards on GitHub.