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 đ
This book just released (hosted by Hewlett Packard, includes folks from Netflix, VMWare etc):
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.
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:
And now the results from Editoria look like this đ
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:
- Investing in slow and costly ârequirements researchâ
- 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.
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 đ
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:
The awesome Book Sprints folks continue to do amazing work.
In July 2019, the U.S. Department of Commerce’s Commercial Law Development Program (in partnership with the African Legal Support Facility) brought together a group of world-class experts to update and refresh the “Understanding Power Purchase Agreements” handbook five years after the original publication. The updated handbook, funded by Power Africa, includes additional insight and case studies on the negotiation of power purchase agreements for both small and large-scale projects, along with new guidance on emerging issues in the African power markets such as commercial and industrial power purchase agreements and cross-border agreements.
The updated handbook was drafted using the Book Sprint method, which allowed our diverse group of contributors from African governments, multilateral institutions, development banks, private developers, procurement consultants, and leading international law firms, all whom contributed their time on a pro-bono basis, to complete the handbook in only five days. Version 2.0 of the handbook is available here in PDF format. The handbook is published under the Creative Commons License. Please contact Mohammed Loraoui with any questions regarding the handbook.
From https://cldp.doc.gov/programs/cldp-in-action/details/2547 (Oct 15,2020)
The backend of our Editor (Wax2) is ProseMirror. Some reading resources here…(more to come).
Some pre-release pics (shhhhhhh!!!!)….you can click to enlarge the images.
If you read this far down you deserve a reward đ try this link.
The latest version of wax supports inline and block editing of math. Christos is also doing some cool stuff with the find and replace UI and there is a whole lot more to boot…
One thing that we looked at some time ago is this example : https://pboysen.github.io/
Try this example out…it is a prototype showing how to add questions to a text (multiple answer, single choice, essay, true/false and more…).
It could be very interesting to build this into Wax which would also give us some nice options for various platforms like Editoria etc… essentially opening the door for making interactive quiz content but *natively* within the editor…so no messy secondary platforms to work with and awkward integrations, and we would have complete control over both the styling and conditional export options – for example, for PDF or print output answers could be embedded at the back of the book, for epub or html the content would remain interactive etc.
Interesting to ponder use cases going forward….
The team has been working very hard on Paged.js with a 1.0 release coming very soon. However, it seems I am a little amiss in making more of a big deal about one particular milestone the team should be very proud of. It happened back in August with the first release of a book that had been output from Editoria.
The books is Shifting Stacks published by the wonderful folks at Atla:
https://books.atla.com/atlapress/catalog/book/39
What is interesting about this book is not that it was produced with paged.js and it looks pretty good… actually it looks really good…check out the PDF created by Paged.js here:
https://books.atla.com/atlapress/catalog/view/39/53/300-3
Yes, this is good news – it looks great – but it is not the real news. The real news is that this was output from a paged.js template without any need for book-specific tweaks. In other words, the Atla team just needed to pres a button and the book was formatted automatically by paged.js and converted to print ready PDF. This means the Atla team could work on the book, output the PDF, tweak the content, proof etc, and then press the button and output the PDF etc…. at some point in one of those cycles they push the button for the last time and send the PDF to the printer…
That is quite something…