Jump to main content

Contribute


Meet the team

anthonydillon

Engineering Director

Contributions: 396

bartaz

Senior Web Engineer

Contributions: 880

lyubomir-popov

Lead Visual Designer

Contributions: 499

elioqoshi

UX Designer


Contributors

barrymcgee

Contributions: 1015

sowasred2012

Contributions: 624

deadlight

Contributions: 506

richmccartney

Contributions: 257

Caleb-Ellis

Contributions: 246

bethcollins92

Contributions: 213

nottrobin

Contributions: 209

grahambancroft

Contributions: 168

renovate-bot

Contributions: 116

yaili

Contributions: 105

pmahnke

Contributions: 67

ilayda21

Contributions: 49

WillMoggridge

Contributions: 29

mtruj013

Contributions: 26

0atman

Contributions: 25

steverydz

Contributions: 23

andesol

Contributions: 21

jkfran

Contributions: 21

ClementChaumel

Contributions: 18

albertkol

Contributions: 18

dependabot[bot]

Contributions: 14

petesfrench

Contributions: 14

Lukewh

Contributions: 13

carkod

Contributions: 10

renovate[bot]

Contributions: 10

hatched

Contributions: 5

b-m-f

Contributions: 4

Contribute

When submitting a new issue, please check that it hasn't already been raised by someone else. We've provided a template for new issues which will help you structure your issue to ensure it can be picked up and actioned easily.

Please provide as much information possible detailing what you're currently experiencing and what you'd expect to experience.

To work on an issue, please fork this repo and create a new branch on your local fork. When you're happy and would like to propose that changeset to be merged back upstream, open a pull request to merge from your local origin/master to upstream/master.

When committing changes, make sure to group related changes so that the project is always in a working state. Use succinct yet descriptive commit messages to allow for easy reading of the commit log.

Guidelines

We follow two guideline documents that align with the practices that the Canonical Web Team follows across all projects.

File a bug

We use GitHub issues to track all our bugs and feature requests.

Chat with us

Find out about new releases, latest features and get help on Twitter.


Running tests locally

The simplest way to run Vanilla framework is to first install Docker, and then use the ./run script to build the site. Before proposing a pull request, ensure that the tests pass on your local fork. To kick off the tests for your project, in the terminal ./run test.

Licences

The content of this project is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license, and the underlying code used to format and display that content is licensed under the LGPLv3 by Canonical Ltd.