Project philosophy

We aim to always encourage participation in our projects from both within the company and the general public. We aim to support and grow the communities that surround our work. We do this by creating web applications that are simple for everyone to understand and use.

Our work should be available to the public, and as easy as possible for anyone to contribute to or learn from. This philosophy should permeate everything we do, from the software we choose to how we write READMEs and our code, to how we respond to pull requests and issues.

We encourage consistency and building on what’s gone before, and so following one of our standard structures is recommended in the absence of other concerns. However, we also encourage exploration and remaining open-minded to better ways to solve problems. This means that there may well be cases where a completely new stack or language may be chosen.

In practice

Our web applications are designed as small, focused, self-contained projects with only loose coupling to our other applications. Code should be shared between projects by writing open-source packages for inclusion in the relevant projects, and applications should share data through public APIs.

We keep our code in public GitHub repositories if possible. Each project should be simple to understand and get running without needing deep technical context or wider context about our other projects. As far as possible, no special credentials should be necessary to get the code running.

We always intend to choose straightforward technology stacks that are no more complex than they need to be for the application in question, just as the application itself should be as simple as possible.

Last updated 10 months ago.