Stealthy git - solving CMS woes with git, on the quiet
Content management systems are rarely fun to use. Not for developers, not for authors. They hamper effective development and they invent confusing processes for content authors.
What if we could build a CMS on top of git? What if instead of trying to invent new ways to solve things like version control, publishing approval, previews, and accountability, we used git which already has mechanisms to cope with these things and more?
Although developers might welcome this, content authors might not. Especially if we asked them to learn git so that they could do their work. Let’s not tell them. Let’s do it all behind the scenes and give them the benefits without exposing them to the underlying technology.
This talk will look at how Netlify CMS (an increasingly popular open source project) is marrying powerful git workflows with static site generators, continuous integration tools, and a flexible admin interface to make building and maintaining a CMS powered site a joy for all.
Writing a book in 2018
The usual way of writing a technical book is to open the Word or LibreOffice application, to write some content, to make a backup, to send it by email to the publisher and to deal with the feedbacks. And repeat.
However in 2018 we can do differently by using open formats like Asciidoc, by using version control to propagate changes, by using collaborative platforms like GitHub or GitLab to collate feedbacks in any form as well as transforming text and code into readable and interactive artefacts.
It gives us a unique opportunity to approach the whole process of writing in term of “content experience”, of “toolchain” and of “distribution”.
In the end, a “book” becomes a “writing format” as we can reuse the same pattern to manage any kind of “content” — articles, publications, essays, documentation — that we can transform in physical books, e-books, interactive web pages etc.