 a bit of yesterday this morning, but I'm really grateful to be here. It's inspiring, especially to see some of the sort of people behind some of the underlying technologies or projects that I have been using. My name is Carl Fittheider. I'm an educator and a touring vehicle, currently at A.C. in Amsterdam. I worked with the publishing that last year that was also my connection to this particular topic. I do some work with the processing foundation, trying to make sort of like code and code more accessible to like wider models. This is sort of like my main sort of like personal release. So today I'm going to talk briefly about this project that came out of my time at the publishing that it's called The Sausage Machine and what I explained online. And so just to give a brief context you've already, I mean that was already also briefly mentioned in the previous presentation, the internet, but so what I'm doing is sort of like nothing new. I'm building upon the so-called The Green Book. From print to e-book I had a publishing toolkit for the arts that was this sort of like two-year research project where also Michael was instrumental in defining all of the technologies and sort of language that's used. The other resources is sort of like this is the main portion that it's coming home. And again like we're like heavily using Randolph, which is I think, I mean I haven't still had a hard time understanding Haskell or something, but I think sort of like it's a fantastic addition. And this is the URL. You've seen a similar diagram before, but real quick sort of like we have those Markdown files that are central to the editing process. They're really great because you can did them and you can use like did workflows with them. And then from the mark, so that's sort of like the existing workflow. And so like from the Markdown we go into different formats via a panel, and it's not only a panel, it's sort of like a panel plus big files, plus a lot of scripts with a lot of different people also like under Haskell have contributed to it. And resolve this sort of like files for different objects. And this is a project system for the rendering, but it's sort of the general anatomy of that product, how we use it or how that I have the publishing that uses it. And to say it's sort of like the publishing that not only does do kind of research into that, they're also like actively like producing books also for the Institute of Natural Cultures as well for other sort of like institutional contexts. So they're like producing books for other entities in this university. And so this is how this would look like. So like you have a folder where all the Markdown sources are. You have a different folder where for example like the fonts end up or maybe one folder where the original dog X file was placed. And sort of the general sort of turn to transformations is mainly guided levels make files and scripts. And so like my approach was to, since this really contains everything besides the panel and sort of like most dependencies, my approach was to move all of this that was normally executed on sort of like the designers slash editors slash whoever's machine and move this and sort of like automate this whole thing. Because sort of like this thing already comes with the with the old instructions and all the rules for doing the transformation. So I thought I would do like some sort of like built box or continuous integration style thing. So the name comes from this quote from the West Wing. It's called, no one likes to see the sausage made, including the guys who make it. Because it's often like just like tight deadlines and that's really also what you said about the first and second law of infrastructure. Like sort of like when you're working in an institutional context, it's there's often yeah, there's often just the requirement to get it done. Disasserts machine, those are like the two URLs that sort of like my fork of that. And this is like a URL to test it onto. Okay. And why this thing? So there were like, this is kind of like the list of my motivation. Why I explored that sort of like getting people started with creating ePops in the common line is a little bit tricky, especially like if they're used to like, that's using word or using marine design. Because they're like a lot of initial sort of like initial sort of initial energy to go over the initial bump. Because like it's on OS X it requires installing X code. Like some of our scripts have dependencies on Django. You then end up sort of like telling people what to do with this and how to mitigate the common line. And this is all things that I think they're like, they're like awesome. And like I personally am uncomfortable with doing it. But if you want to try to sort of like spread the active user base in terms of we also want to like design us to be involved in that and participating in a sort of like a collaborative did workflow. And ideally also editors or even authors to do stuff in Markstone. And this is sort of like problematic. And then sort of like another problem is sort of like it's, it's, it's just not very, it's just not very, it's just not very nice if sort of like you're empowering technology and sort of just throwing weird errors at the user. And then maybe you're the only person in the institution that is somewhat capable of resolving those. And then it's just solved for sort of like, since everything is sort of like self contained in one repository, sort of per one book is sort of like one repository. There's a lot of duplication and a lot of problems are, a lot of problems are sort of like solved in an ethical way. Which is difficult for like, which is difficult for sort of like maintenance. Because you're solving or different people solve things in different ways. There's some difficult for documentation, for example, there's like a, there's a handler switch for say, telling kind of what, like what heading to use for the table contents. And so in some books of us in some documentation would say like, oh, you have to do an H2 in order for it to show up in the, in the, in the table contents and for other things, like other books use the H1. Yeah. So I'll spin up a bit. That's sort of like, this idea was sort of like to have multiple modes of engagement. And this is not, this is somewhat drawn from Alan Kay's work. And I think you have to mention Alan Kay. So this idea was to, to split this up into three levels. So there was sort of like the mode of doing images and symbols. And so I personally see a lot of the, the, the litty gritty terminal shell things. So like, more like in the, in those things. And I don't want to take this away, but I think there's other more approachable ways of, of doing things that are interesting for the novice user. And this is a nice MacLuin quote, quote that Alan Kay also uses. It's sort of like, I don't know who discovered water, but it wasn't fish. So, sort of like maybe sort of like, if you're new to this object, maybe jumping in sort of like from the, from the fish perspective, isn't, it shouldn't be the first step. And this also relates a bit to this thing that actually like a, people that use word, I think they're like highly, sort of they are, the, the new ones are actually like, I think really specialized. And I think those people are really kind of a problem solvers because the program itself isn't so straightforward. So I think I think I'd love to have in this hyper publishing thing, I'd love to have something where you have a way of working where you just try out things, you get a result, and you immediately sort of have a visual feedback. Because this is like at least how I started, sort of like, you know, doing things with computers. And this is sort of like how this thing works. So this is, again, this is continuous integration. So basically, in a nutshell, you make changes to a marathon file. You're committed to it. There's like a, on the deck, sort of like there is a bot that will, in the cloud, that's your comments. And basically run, make all on a server. And then the files that are changed are being committed again on to the Git repository. So this is into sort of like making changes to, to a book. And it's sort of like feeds back into the Git history. I really enjoyed, like meals, practice live thing, because it also had a similar trajectory of sort of like having, having, and this is a second mode, I would say, because like you had objects, and there was a way of kind of like opening up those objects and going into the network code. And coming back to NK and the one that took the child thing. I think at least the original keyboard had this idea that you could press a function and space key. And you have this kind of cork symbol here. And at least originally, the idea was that you would always be able to kind of edit the current, the source code that basically drives the current view. And I'd love to have more of these kind of like things where you can, you have, you have tools and you can like really easily go one step or two, if you want. And in sort of the sausage machine, this is how, this is basically our way of, of going one level below. It's sort of like, we have the make file, the make file is still part of the project. So if you want to experiment more of like, of those kind of transformation rules, you can still go there. And you can still run everything you want to as well. Yeah, maybe, I don't know, it's just like an idea sort of like the Chinese room or so. I'm all for, I think it's great to sort of like tell students, you know, how things work and sort of like sort of untangle those like boxes for them. But then at the same time, I know that also like a lot of, a lot of really awesome projects have some sort of idiosyncratic properties or so. So if I look, for example, like in sort of configuration files or so. And this is sort of like something that I came to learn just all time or so. But like, I think this is like a sort of big hurdle for people that are, you know, maybe new to this type of sort of text based configuration. And so just thinking that sort of like, yeah, sometimes it's really obvious to you, but like sort of the whole thing. And this is like, this is unfortunately, this also creeps into this is like an image taken from Twitter. This also totally creeps into like current kind of front-end web development or so. I don't know if you can read it, but sort of like, this is sort of like React.js mixing, actually really mixing a lot of really, really different sort of like concepts and syntax and kind of like presentation versus controllers or sort of like in the same thing or so. And I'm really sort of like, if this is, if I have to tell this to, if I would have to introduce a student to web development through this kind of means, like this kind of way of working, I'd be kind of lost. I'll just brief, I don't know what I mean, but I'll just briefly show all these things, looks right now. It's kind of like a sort of like, so this is basically a website and you can, well normally it doesn't, it polishes and I can, the demo got not with me, but I can actually explain, so it's like a website on the top left, multiple tabs, on the top left tab, you're able to like import files, you can just drop in existing work files, image files, whatever. This is sort of an optional step. The second step that we see now is it's sort of like a very simple text editor where you can edit your CSS files and make files and markdown files, and you see kind of like a similar file structure on the left that you can navigate. So here is the idea would be, for someone who has never done markdown or has never done like epochs, here you could like in the browser, like sketch out a file, and when you click save, it just renders it in the back end, using exactly the make file, and you can choose between different templates. Once you hit sort of like continue on GitHub, and it just, it forks the template, it applies the, basically applies your local changes on top, and it kind of hooks it up to the system so that whenever you push the repository in the future, the bot that also runs the server will basically rather make all for you and push again to GitHub. Yeah, I think that's it. Thanks so much for your time.