<aside> đź’ˇ What is the Campaign Database? In order to keep track (and documentation) of a campaign we need to build a campaign/project database. It is important that this is curated by campaign managers and guild contributors. Not only larger campaigns should find a home in here, but also the little activities, and all scheduled content that goes via our channels.
Are you responsible? If you are in charge or a contributor to a specific project/campaign that includes services of the marketing guild, yes you are responsible to curate the documentation of your project in here.
</aside>
This type of content includes content from the bDAO itself, various guilds and campaigns or external requests.
<aside> đź’ˇ The Importance of an Item Briefing: A process could be created where a standardized input will require parties to enter the necessary information in order to receive marketing love. We would also make it clear that a 14 days heads-up period is required to plan, create and distribute the content.
</aside>
Because there is a big variety of content groups (i.e Guilds, bDAO, campaigns, etc.) it is important signal the type of content in a visual way. I believe that no social media post is complete without a corresponding visual asset (because of real-estate in the feed to name only one reason). The item briefing allows us to create assignments for a visual asset template based on the type of content. Example: Promoting the bDAO weekly rollup newsletter would have a slightly different visual appeal compared to a guild newsletter or podcast post. Users would immediately recognize the style and therefore the content type within after a while.
For the most important channels (Twitter, FB, IG) we would only need two template assets: A square JPG and mobile screen vertical. Those templates could be created by the design guild in Figma and easily adapted for the next post (replace text layer, etc.). This would make asset create very lean and fast.
This type of content includes all requests that do not meet the 14 days heads up period
This type of content includes urgent & unplanned requests from various sources. It has a lower priority compared to already scheduled initiatives. This is the “quick and dirty” version of distributing content, but should be aligned with the overall content schedule to avoid a timing overlap of content distribution.
Besides internal bDAO content, it is important to dig through websites and social feeds in the search for interesting web3 content that is relevant for interested users. Those elements should land in a queue and aligned with the already scheduled content and shared within 7 days of discovery. Ideally, the content supports everything else from a topic standpoint that is in the content calendar (i.e. Sharing interesting news about DAOs shortly before posting about the “State of DAO Newsletter”
<aside> đź’ˇ How to look at the campaign database? There are three main views of this database that you should know: The table view gives you a pretty raw view on the database with all kinds of properties attached. The Kanban Board is where we can keep track of the project status in order to make sure the projects are on track. The third view acts as our content calendar that helps to identify the surroundings of the content in a given timeframe.
Detailed Documentation of a specific campaign Besides the properties (link, status, manager, Date, etc.) you should place the complete documentation of a campaign within the item page. Click on one of the campaigns and it will open up an empty page that waits for information
</aside>