Changes between Initial Version and Version 1 of opc/notes/2013-13-03


Ignore:
Timestamp:
May 13, 2013, 10:50:54 PM (12 years ago)
Author:
Stephen Mahood
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • opc/notes/2013-13-03

    v1 v1  
     1
     2== Outcome from March 13, 2013 Meeting ==
     3
     4=== LOWDOWN PROPOSAL ===
     5
     6
     7==== PROJECT: ====
     8
     9We have identified that the Lowdown newsletter has untapped potential
     10to assist organizational growth, political and media outreach, and
     11membership development.
     12
     13==== PROBLEM/ISSUE: ====
     14In it’s current incarnation, the Lowdown is falling short of it’s
     15potential.  It is difficult to navigate online, does not have a user
     16friendly web interface, email distribution is not optimum, there’s no
     17clear visual identity, etc.  It doesn’t look like a newsletter.
     18There’s not an easy process for generating content.   The name does
     19not currently translate internationally.  It’s unclear who reads it,
     20what people think about it.  Great content is being generated but not
     21necessarily well utilized for outreach or promotion.
     22
     23==== GOAL: ====
     24To revamp and revitalize the Lowdown
     25
     26==== PLAN: ====
     27Create a dedicated area for the Lowdown articles that resembles more
     28of a blog format.
     29Stephen offered some great examples of how this could look:
     30http://solidarity-us.org/ http://www.labornotes.org/
     31The blog will feature columns –
     32Draft ideas include:
     33tech resources – reviews of open source software with comparisons of propriety
     34software and open source alternatives.
     35Reports from LC or committee structure
     36Reports on work with partners/allies/associations/collaborations– to be more
     37transparent about our participation in these forums
     38Member profiles/news
     39News and Political reporting
     40Events and announcements
     41Webinars/tutorials of software use
     42A job board for tech support/design resources
     43Other ideas?
     44
     45Articles can possibly be opened up for comments or discussion
     46
     47A searchable database of past articles that can serve as a resource.
     48Ideally users could search by date, topic area as well as customizable
     49search terms.
     50
     51We could also create a team to solicit and develop content – ideally
     52pulling on members who are journalists, artists and organizations that
     53can collaborate on content production.  This idea would require some
     54labor/time to manage and needs to be fleshed out.
     55
     56Considering the need for a name change – we could do some outreach to
     57come up with a new name as a way to build interest and help
     58pre-promotion.  W e can also organize special outreach to
     59relaunch/announce the website with the new name – perhaps with some
     60kind of party or special content or something.
     61
     62==== OUTREACH: ====
     63This blog style has a number of benefits:
     64We can use to extend a visual identity
     65Can link to social media for outreach
     66Can be used to outreach to media
     67Can be used in recruitment  (we could also open up subscription to non members)
     68
     69We still need to utilize email outreach about new issues and articles.
     70But need to reconsider options for what this could look like.  This
     71section needs ideas and detail.
     72
     73==== TECHNICAL DETAILS: ====
     74Civicrm might have most functionality for our purposes, esp. translation
     75Development can be set up in stages to slowly integrate new options
     76and to allow for expanded ideas such as revised email newsletter
     77formatting.
     78Process should be considered along with larger web redesign for visual
     79and functional consistency
     80
     81Need tech guidance on what this job will entail in terms of time and
     82labor to figure out how extensive the plan can be, where we can set
     83limits, what’s feasible and in what timeframe we can accomplish the
     84transition.