Carve out time for coding! To get momentum on publishers' increasing enthusiasm for code, every Friday afternoon, May to August, we convene on Twitter to compare notes on our side projects. It's fantastic to see all the things people are doing with their growing technical literacy.
If someone’s having to read your docs, it’s not “simple”, but technical documentation often resorts to words such as 'just', and 'simply', which can make for a frustrating read. We wrote a one-page website, justsimply.dev, to encourage documentation writers to look again at their language.
In association with The Bookseller's FutureBook conference, we were thrilled to deliver a Day of Code, which demystified programming for the book trade. 40 delegates from bookselling and publishing wrote their own website from scratch in a day, using Ruby, Jekyll, HTML and CSS.
We run occasional coding sessions and courses for organisations such as Book Machine, eLife Sciences, the London Book Fair, SYP, and universities. Often we make these free to attend. We announce such courses on Twitter. Contact us if you'd like us to quote for a private coding course for your organisation.
We donate to some of the open source code we rely on, such as Rubocop, via OpenCollective, and contribute to code where we can, such as the Lisbn rubygem, and the official Rails documentation.
Whether it's supporting paid internships, attending an anti-Trump demonstration, or pushing for corporates to support technical literacy in publishing, we are proud of our actions to make the world a bit better.
We have a busy diary of events we run or contribute to throughout the year. Recent events include a coding seminar at the London Book Fair, BookMachine Unplugged, Byte the Book, Coding at the Castle for the Oxford SYP, the Pitch competition, and more.
This is a public collection of the building blocks that we use as we continue to improve Consonance. Just as Consonance gives its users “one source of truth” for their data, our component library provides us with “one source of truth” for some of the most key components in our code.