open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • What a crest looks like
  • Choose the tools you like to create the crest, together
  • Option: Use Figma to design your crests together
  • Getting started
  • Copy the template
  • Share the board with your colleagues
  • Collaborate
  • Tips
  • Export
  • Share
  • Alternative options

Was this helpful?

  1. Tutorials

Create Crests

Crests will appear on our website, to show off your team!

PreviousMaps & CartographyNextPitching

Last updated 3 years ago

Was this helpful?

A glimpse of the 2019 crests

What a crest looks like

  • Your crests need to be 400px by 400px

To check if your SVG exported correctly, open it in your browser! Sometimes gradients and opacity can cause some issues.

Choose the tools you like to create the crest, together

We have no strict rules on what tools you should use. The only restriction is that the output is as described above, and that it's a team effort!

Option: Use Figma to design your crests together

Figma is a good tool for visual collaboration. It is not the only one, but it works.

Getting started

This is what the board looks like:

Copy the template

Share the board with your colleagues

With free subscriptions, you can only add 2 editors and unlimited viewers. So choose wisely who can edit.

Add the colleagues who are allowed to view

Add the colleague who will edit with you

Collaborate

Go to your breakout room (shared in advance), ask someone to share the figma screen and start brainstorming!

Tips

  • Pick colors

Export

Select the artboard and export as SVG (bottom right)

Share

Share your crest in the folder "crests", with the name of your project. Ask your coach for the team folder.

Afterwards, we'll share you crest, with project description, on our website!

Alternative options

  • You can also choose to use a team member's preferred software and share screens with the team.

  • Feel free to use and suggest any other workflows 👌

A , exported as SVG (so no PNG or JPG) – which can be created with tools like Figma, Sketch, Illustrator or Adobe Fireworks.

Depending on the software you're using, there's ways to fix that. Not sure how that works? go to the Design consult channel in

Choose who will create the design. and verify their email address. Feel free to use a Figma account you already have, but keep in mind there are restrictions on the amount of collaborative boards you can use.

You can download the discord desktop app at . You can use the browser version, but it works a little less fluid.

We have prepared a template at open it and duplicate it to your folder like shown in the image below, or copy it to one of your own boards.

(by Inti)

Free vector graphics

Use collaborative tools to work together

Versioning is possible with tools like , and you can export designs into code immediately!

vector
Discord!
This person can create an account
https://www.figma.com/
https://www.figma.com/file/Vxqp9O3hg9sA9ItzMpwmPF/osoc-crest-template?node-id=0%3A1
https://mycolor.space/
https://coolors.co/
https://thenounproject.com/
https://figma.com/
Zeplin
https://osoc.be/editions/2019
A pro tip from our swag designer coach Niels