Marketing Strategy for the Next Two Years
Tue, 01-Sep-2020 by
mdk
edit post
At the August monthly director’s meeting for the Perl Foundation, the marketing team presented a strategy for the next two years. This strategy is a broad look at where the team believes we should focus as the Foundation, the Foundation and community brands/products, move forwards.
The strategy can be read, in its current form, in the attached document: [The Next Two Years.pdf](_ra-rel-mnt_/simplecas/fetch_content/dfe84fc731d5b247c9dd6ac59e98017ecb6c562c/The Next Two Years.pdf). It is a living document, by which we mean that this is the proposed strategy and a very broad canvas. As we move through the next two years this may be updated to reflect any changes in Foundation focus.
Allow me to give you a brief TL:DR of the first year:
1. Identify the brand that is TPF.
2. Design and style the Foundation to match that brand.
3. Identify the core products, resources, groups (some of which are brands in their own rights) that make up the community. So Perl, Raku and the Foundation itself are different brands, and the same may be true of MetaCPAN, CPAN Testers, CPAN, Mojolicious, Dancer, etc..
4. Help all the elements identified in point 3, above, to recognise their brand identity, help promote their uniqueness and also have a clearer picture of how we all fit together.
This is all a 20,000 foot view. The committee has already started to do some of the work with a recent marketing survey; and by reaching out to projects and committees in the community who work with our various brands and products.
Our first task, approved by the board, is to correctly brand the Foundation itself. Our survey had some interesting results and responses. We looked at all the feedback and also asked outside of the survey. One thing was very clear, the current brand strengths of the Foundation (powered by volunteers, passionate about helping with software, trustworthy) do not match what is wanted or liked (passionate about helping, transparent and professional). The view from outside of the community is fractured, and in disarray with no understanding of how things relate to each other.
So we are going to start with the Logo and the Look. We are a marketing committee after all. The Onion logo is often associated with Perl more than with the Foundation (as is reflected in usage). One third of respondents to the survey didn’t associate it with the Foundation or Perl. The logo doesn’t reflect the Foundations current values, or the values we should be aiming to project. It is also too easily confused with Tor.
Therefore we have a budget to engage a professional organisation to design a proposed image/logo to match the brand values of the Foundation. This will then go to a consultation stage with the community. It is clear to us that having the feedback of the community is essential and we want to work with you all.
The revised marketing committee will be hoping to share more in the coming months, so please keep a look out for News here and in your usual feeds and channels. We value the feedback we have already received and welcome you to contact us with any comments or suggestions.
Category:
(none)
Comments (4)
I hate to be a PITA, but in addition to all this soft stuff, can we make it priority 1, no, sorry priority 0, to FIX BLOGS.PERL.ORG? I am trying re rebut two complaints about The Perl Challenge and the simple act of posting a reply fails to work. Repeated "submits' are ignored, or incorrectly rejected for not being logged in when I AM logged in. Marketing is good. Functionality is WAY more important. Sorry to hijack the post, but my frustration level is at an all time high with that site.
Therein lies the problem...
As far as I can tell, perl.org is a separate entity from the Perl Foundation. Even some of the sub-sites may be distinct entities. If you will note, blogs.perl.org does not have the same look as perl.org, so may be separate from it. It would be like asking for fixes to perl.com or perlmonks.org here. I do not think the Perl Foundation has much, if any, control over how those sites operate.
So asking for fixes to another independent site here will probably do nothing. I am sure there are avenues on blogs.perl.org one can go through to get something fixed.
I have found the issues page for the blogs.perl.org repository here: https://github.com/blogs-perl-org/blogs.perl.org/issues
matthewpersico: There is an infrastructure team and I know that the issue with Blogs.Perl is an issue that is being worked on, but I have no further info at this point. Hopefully someone in TPF can give more insight.
The list of resources that can/will be approved and used by the Foundation on behalf of the community and the brands is being drawn up, and if you look at the longer plan you can see we feel it is essential to capture a similar look and feel across approved resources and produce style and usage guides for brands and products (in association with the project/brand leaders and committees). Thanks for the questions hope that answers some of your queries.