Added a CommittChange Donate Button

Added a donate button to Cabbage Tree Labs and it’s child projects (Pagedjs, Wax, XSweet). Generally, I don’t like the donation model but I do know there are folks that want to find a way to support what we do.

So, if you want to support these projects financially and have heaps of spare cash laying around think about a donation. If you don’t have HEAPS of cash then I recommend saving your money 🙂

https://www.cabbagetreelabs.org/

Hewlett Packard Book Sprint Update

This book just released (hosted by Hewlett Packard, includes folks from Netflix, VMWare etc):

book_cover

This book presents the SPIFFE standard for service identity, and SPIRE, the reference implementation for SPIFFE. These projects provide a uniform identity control plane across modern, heterogeneous infrastructure. Both projects are open source and are part of the Cloud Native Computing Foundation.

As organizations grow their application architectures to make the most of new infrastructure technologies, their security models must also evolve. Software has grown from one monolith on one box, to dozens or hundreds of tightly linked microservices that may be spread across thousands of virtual machines in public clouds or private data centers. In this new infrastructure world, SPIFFE and SPIRE help keep systems secure.

This book strives to distill the experience from the foremost security experts and SPIFFE community members to provide a deep understanding of the identity problem and how to solve it. With these projects, developers and operators can build software using new infrastructure technologies while allowing security teams to step back from expensive and time-consuming manual security processes.

Available under a creative commons license.

https://spiffe.io/book/

epubcheck

Editoria produces only valid EPUB from its export. To validate we run the output against the Daisy consortiums epubcheck. However the publicly available epubcheck linked from Daisy/IDPF is running epubcheck 4.2.1 and it reports errors which are incorrect.

So..we had the problem that Editoria, running the latest epubchecker, was producing valid epubs but the public epubchecker site was reporting errors!

So… we asked the awesome folks at Cloud68 if they would set up an epubcheck 4.2.2 and they did… free to anyone to use:

http://epubcheck.cloud68.co/

And now the results from Editoria look like this 🙂

Image collée à 2020-11-11 20-49

Workflow Sprints

Prepping some docs about Workflow Sprints…here are some excerpts…feedback to adam@coko.foundation appreciated!

What is a Workflow Sprint?

A Workflow Sprint is a new methodology for helping organisations understand and optimise their publishing workflows before making technology choices.

Workflow Sprints do this in a series of facilitated sessions that can occur remotely or in real space. The process was developed by Coko Founder Adam Hyde after he witnessed many publishers (or organisations with publishing operations) making these common mistakes:

  1. Investing in slow and costly ‘requirements research’
  2. Identifying solutions purely in terms of tool features

When facing the challenge of improving inefficient, dysfunctional, or ‘stitched together’ legacy publishing systems we have seen everything! The most common way to start digging an organisation out of this hole is to hire external consultants, or appoint someone internally, to individually interview a wide spectrum of users, construct hopelessly complicated logical diagrams, and make a long bucket list of features that seem to be missing.

After this long, expensive process the work begins to find a tool builder that can rewrite their offer (in terms of an existing tool, or bespoke development) in the language of your requirements document.

Another common approach is to skip the long requirements stage and adopt a new tool quickly that seems to fulfil at least some of the ‘missing features’ and live with the consequences.

We do not advocate either strategy.

Real, ‘future proofed’ solutions that create measurable efficiencies in publishing processes come from first understanding your publishing workflow, and then designing an optimised workflow. Only then can we understand what tools may be required to get you from where you are now to where you want to be.

In other words, process optimisation is not a tool-first process. It must be a workflow-first process. Technology should be a servant to workflow, not the other way around. You must understand the workflow you want in order to understand the tools you need.

A Workflow Sprint is a rapid, cost effective way to help your organisation design better publishing workflows and make sound technology choices.

What Remote Facilitation Looks Like

Some pics from Book Sprints remote facilitation events…I have also started doing Workflow Sprints remotely (more on this in the next post)…the following starts with a cool little vid 🙂

49841053458_c5e128ca8e_k 49841099118_8d2bae40a6_k 49854266736_68cbc3796c_k 49854548581_728e637a86_k 50289527908_5f89b8d73b_k 50290413807_894ba1f9ad_h

Facilitation has certainly evolved in the last year or so due to the pandemic. I think the Book Sprints crew do an amazing job of keeping it real and they have mastered the art of efficiency and productivity in this new context.

I also just want to point to an event about facilitation. I sorta also don’t want to point to it. It has a lot of red flags for me in the way it presents itself…it might be more for tired corporate facilitators….anyho… judge for yourself:

https://neverdonebefore.org/