agaric/documentation
10
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Start to reorganize into content and channels

Browse source
This commit is contained in:
benjamin melançon 2020-06-30 23:01:59 -04:00
parent a5b47d3417
commit 3d3c6404f1
1 changed files with 19 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
marketing.md
View file

@ -5,28 +5,38 @@
[Agaric's content styleguide](styleguide)
```
## Content
### Case studies
Proposals/contracts should include a clause permitting use of the project in case studies. Case studies should be their own, visually distinct content type; blog posts can then be tagged to them. Case studies should also be posted to Drupal.org.
### Blog posts
We collectively commit to have at least one post a week to our blog; that means each of us should produce at least one blog post a month.
## [Agaric.coop](https://agaric.coop)
The flagship of our marketing efforts, where we control both content and presentation.
From conversation led by Mauricio. An open question includes setting a marketing budget (5% revenue?)
All content of any substance must also be here, not only places where we do not have full control.
## Online
## Channels
Primary online marketing includes areas we control fully in content and presentation, such as newsletter and web site / blog.
### Newsletter
14 years in, still haven't sent one. But that needs to change.
Secondary online marketing includes places not fully in our control, such as Facebook, Twitter, and LinkedIn.
Content for Twitter in particular (aside from announcing and discussing our own blog posts) can include events we are organizing (global training days in Nicaragua), places we will be (cons and camps), links to other people's blog posts which we find useful. Stefan prefers posts by Agaric on any social network have some real connection to us.
## Drupal.org
### Drupal.org
Drupal marketplace is sorted by issue credits (which can include testing/review as well as code commits) in the past 90 days; at present 20 from all at Agaric will get us onto the front page.
## Content
We must follow through with our collective commitment to have one post a week to our blog.
Proposals/contracts should include a clause permitting use of the project in case studies. Case studies should be their own, visually distinct content type; blog posts can then be tagged to them. Case studies should also be posted to Drupal.org.
## Events
@ -46,3 +56,5 @@ Our current social media presences:
* Twitter - https://twitter.com/agaric
* Peertube -
* YouTube?
Content for Twitter in particular (aside from announcing and discussing our own blog posts) can include events we are organizing (global training days in Nicaragua), places we will be (cons and camps), links to other people's blog posts which we find useful. Stefan prefers posts by Agaric on any social network have some real connection to us.