pipe-cd / pipe-cd/pipecd

📢 Standardizing PipeCD Community Outreach & Branding Assets

Open
#6,527 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.4k
Forks
364
Avg merge
1d 4h
Merged PRs (30d)
84

Description

What would you like to be added:

Standardised community outreach and branding assets for PipeCD, including:

🔗 Figma Link:
https://www.figma.com/design/d98dzEhqEJYDFzgy1OcWnt/PipeCD-Community-Assets?node-id=0-1&t=EfebIGDOczGydTQD-1

✅ Assets Created So Far

  • Organisation Values Representation (Cover Image + Footer Branding)
  • Official Backdrop / Virtual Background
  • Social Media Post Templates (including 2 example posts)
  • Technical Documentation UX Improvement – Wireframe

🚧 Currently In Progress

  • Social Media Presence Guidelines
    • Typography
    • Brand Colours
    • Iconography
  • Short, high-impact video for the PipeCD YouTube Channel

Why is this needed:

Currently, the PipeCD community outreach and branding materials are not standardised, leading to inconsistencies across social media, posts, documentation visuals, and community-facing content.

These assets aim to:

  • Establish a consistent and recognisable visual identity
  • Improve communication clarity and outreach efficiency
  • Provide contributors and maintainers with ready-to-use templates
  • Strengthen PipeCD’s visibility, professionalism, and community growth

Community and mentor feedback will help refine these assets to ensure they align with PipeCD’s vision and long-term outreach strategy

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Figma design and review the listed completed and in-progress assets, including the outreach templates, branding, documentation wireframe, and video. No repository file, test, or implementation entry point is named. Done would require an agreed, finalized set of standardized assets and guidelines, with a clear destination for contributors and maintainers to use them.

Written by the indexing model from the issue text.

Assessment

Tech stack
figma
Domain
content, design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.