From e01d9fbe9471d7004af68fa84dbeb24e86187ab8 Mon Sep 17 00:00:00 2001 From: mik-tf Date: Tue, 28 Jan 2025 14:21:10 -0500 Subject: [PATCH] add content distribution procedures --- docs/content_distribution_procs.md | 60 ++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 docs/content_distribution_procs.md diff --git a/docs/content_distribution_procs.md b/docs/content_distribution_procs.md new file mode 100644 index 0000000..13ff1d6 --- /dev/null +++ b/docs/content_distribution_procs.md @@ -0,0 +1,60 @@ +# Content Distribution - Procedures and Documentation + +## Introduction + +We provide the basic content distribution procedures and documentation. Concretely, this means that we provide guidelines to distribute content created by ThreeFold. + +## Overview + +- There is an issue created (Story/Task) on [Comms Circle repo](https://git.ourworld.tf/tfgrid/circle_comms/issues) about creating a piece of content + - The specs of the content is laid out in the story + - This includes + - What the piece of content is about + - Which platforms will we distribute the content + - Who is assigned to write the content + - An ETA for the content to be written + - An ETA for the content to be published +- The assignee writes the content in the [Comms Circle Content Distribution Folder](https://drive.google.com/drive/folders/1XhFvGhO9ee6xAj_zL1log3Gm94_D_0rU?usp=drive_link) + - We have different formats for different platforms + - The work is commented by its peers + - From other comms circle members + - When the content is done + - We distribute the content on the platform + - We make sure to document this in the [Content Distribution Checklist](https://docs.google.com/spreadsheets/d/1iIC7d2yeauJNW_7Hhe9Rm1gXVkQhbaF1gtmm2pcKNMM/edit?usp=sharing) + - We indicate the status in the original issue and close it. + +## Example + +- Issue Name: Create 3.16 Release News Content + - Specs + - Goal: communicate the new features of the grid 3.16 release to the world + - Features to announce + - Solana bridge + - Zos v4 + - Assignee + - Sam + - Platform + - TF Forum + - TF Blog + - TF Newsletter + - X +- Procedure + - Sam writes the basic content + - He asks comms circle for review + - After review + - Sam creates versions for each platform + - Comms circle publish on 4 platforms stated above + - Sam closes the issue + +## Content Distribution Checklist + +The [Content Distribution Checklist](https://docs.google.com/spreadsheets/d/1iIC7d2yeauJNW_7Hhe9Rm1gXVkQhbaF1gtmm2pcKNMM/edit?usp=sharing) will be ever-evolving with new content. + +- Contains the name of the article +- Contains the link to the original issue +- Contains the links to the platforms + - e.g. if for TF Blog only, we just have the TF Blog entry for that line + +## Ongoing Process + +We start with this and build from it. It doesn't have to be complex. We just need to make sure we distribute the content to different platforms efficiently and we keep track of all content. \ No newline at end of file