-
Notifications
You must be signed in to change notification settings - Fork 59
M> Create Brand Platform Document #371
Comments
Hey all, please see here the first version of the brand platform document. Executive summary: What's included in the document:
The document also has appendixes to align with other co-branded entities, such as Holdings/Pithia, and Reflective Ventures and Pyrofex. What's next?
Again, here's the document. |
Looking at the doc, I think we can remove the brand guidelines for RhoLang and have an "about" page for it was a short description. The brand guidelines will be in the master style guide which is yet to be produced. |
.COOP Global Cooperative Marque branding was discussed and agreed upon during the Co-op's January 26 staff meeting. Full adoption of the Marque was applied for and granted to the Cooperative to use under these Terms & Conditions. coop MarqueCoop_marque.zip (2.31 MB) coop Marque with sloganEnglish_slogan.zip (2.66 MB) coop Marque with key messagesEnglish_key_messages.zip (19.21 MB) coop Marque CustomEnglish_custom.zip (5.07 MB) Signature images – largejpg_hr_1.zip (16.05 MB)jpg_hr_2.zip (22.96 MB) Signature images – mediumjpg_mr.zip (29.61 MB) Signature images – smalljpg_lr.zip (7.39 MB) |
@drbloom this isn't the document for that information. The .coop brand alliance will be included in the brand style guide. I looked for the approval decision you were referencing, can you provide a link(s) to this text/video? I haven't heard or read that it was decided if we would use it for application/promotion or if it was to be a full logo-adoption. |
@pmoorman @AyAyRon-P please see feedback from the telegram audience compiled by @Mervyn853 in #291 (comment) . Let us know when you've seen it (e.g. with a reaction on this comment). |
@pmoorman this is good start. I made some comments in the document. Having a consistent way of doing things will help unify us and reduce the barrier for entry for new members. |
Taking a look now at Mervyn's comments and will leave feedback there. |
Sigh. Jan 26 staff meeting, attended by all Co-op officers had no minutes. @patrick727 was there as well, and can confirm. After the recent logo confusion, I understand your hesitation, so I'll also check in on this with the Exec-Committee. |
Note also: and discussion in #marketing-launch-plan-proposal-feedback. |
I'm don't mean to muddy the water, but my take away from that meeting was less absolute consensus on the .coop and more of vague "that seems like a good idea" type of comments. I actually don't see if fitting seamlessly into a logo or branding scheme and doesnt seem like every major co-op is doing that. even rei uses there own stylized co-op for there own branding and doesnt adhere to the full adoption requirements. [..braces for impact] |
@patrick727 - What do you mean by saying that you don't want to "muddy the water"? (The following is transcribed from the Jan 26 staff meeting) Ian:
Greg:
Ian:
Pat:
Greg
Pat
Greg
|
Pre-P.S. this issue is spun out of the #234 marketing audit
Problem:
The seems to be growing unrest within the coop about the branding. Many discussions in #exec-committee and #members-only revolve around branding issues. Some clarity is needed.
Also, more and more people come onboard through the Bounty Program (or otherwise) to help spread the word about RChain. This is great... but they need some guidelines to represent RChain properly, and stay on-brand.
Finally, @patrick727 asked me — based on the marketing audit I did before — to compile all the thoughts on branding so-far, and make it ready for an external branding agency to expand on. It is important that the document also takes into account the relationships to partners such as Holdings, Ventures & Pyrofex.
Scope:
Compile all the key brand components into a single document, get feedback within the community, and prepare it for an external branding agency to iterate on the visual components.
NOTE: the scope does not include the visual assets, as they already have their own place in the brand guidelines. From this document, we link to relevant external sources
Tasks / Deliverables:
--
NOTE: We already started working on this together with @AyAyRon-P. To avoid a flood of opinions in a pre-mature stage, we'll get a draft ready before we push it out to the community.
We'll wait a little for the Governance Forum, to see what comes out of that, and try integrate that immediately into the document.
Budget: $5000
The text was updated successfully, but these errors were encountered: