 manager at a company called PPI Media. This is my contact details. Yeah, so I'm a Drupal first-timer, so it's my first DrupalCon, and I'm very happy to be here and enjoy all the good mood and all the nice people here. And so not only I am personally new to Drupal, but my company, PPI, is new to Drupal as well. So we started about at the beginning of this year, thinking about connecting to open source. So before I will go on with the presentation, I would like to talk a little bit of where PPI comes from and what PPI is. So PPI is a 35-year-old company, and we come from the publishing sector. And we have a lot of customers out there, and we are mainly based in the newspaper and magazine publishing area. So we have a digital production line to optimize all the processes in newspaper, planning, and production, which means we start from connecting to the good old presses, to the pre-pressed processes. We connect to ad systems and things like this. Because this is our foundation, and we used to be an open and closed source company for all these years. So now we try and work to get some open source DNA into our structures. And one part of our solution package is a smart editorial system that we use right now. And as even our customers see that there's a need for digital transformation because they see that they want to create inspirational content for both digital and print. They talk about storytelling. They talk about the early story starting on a mobile, just with a push, and then developing the story of a day. And in the end, in the evening, they want to decide, OK, should part of it become part of our print or not? So they want to have a multiple use of content. They need, because they have a close pressure on them, lean production processes for both print and online. And in the end, when we talk to them, so what would you wish to have? They say, OK, so we need one system to fill all channels. So one system for all for digital and print. So this is our task. So we have an existing publishing tool. And now we thought, OK, what could be this one system that our customers want to use to create and store all the content, have their content pool in it? And we think that the WebCMS should be the right address for this one, because this deserves all the digital needs that our customers have. And so our ideal is to provide a lean and simple user-friendly workflow to connect our existing publishing workflow directly to a WebCMS. So this is the task that we started with. And when you search the landscape of WebCMS systems, you all know that there are tons out there. But one system you will run into when you think about publishing and publishers, for sure, is the Thunder Initiative. I don't know if everybody knows about Thunder. I think so. So it's a Drupal distribution from Borda in Munich. And yeah, so we ran into them, and we really liked Fed into open arms. So I would like to use this chance to give a real big thank you to the Thunder team, because we got a lot of support and learned a lot from them that only in a technical way, but from their approach to have a culture of sharing and cooperation. We are working on to become part of the Thunder community, especially in the last circle down there to become an industry partner and see where we can just contribute to this project and by contributing to this project, contribute to Drupal and to this beautiful community. OK, so we decided, OK, let's go open source. Let's use Thunder as a starting point. And now, so this is the situation. You know all this. I don't have to talk about that. There is the WebCMS, which is the central content hub for all the different kinds of context text images, videos, and whatever. And you're all pretty good in serving the digital channels. So you're doing amazing stuff. And I had a lot of very interesting talks about what you do. And so as we are a media company, we are not a digital agency. We are not a web agency. So we are really a software company. And so all these new channels, they are not on our list. So and this is why we decided to do what we can, what we use. So we're very good in printing. We're pretty good in integrating. So we have a lot of APIs in our portfolio with our other workflows. And when we have a look at the WebCMS and how a WebCMS is linked to print and in design especially. So we talked to some agencies and some of them, they just use copy and paste from WebCMS to in design. And I have a lot of pain with this. Files are often stored in the file system or on somebody's computer. And there is no really centralized file storage. I've heard a beautiful talk about PDF generators where I can create amazing PDFs from Drupal with a lot of scripting and CSS and stuff like this. And also in this talk alone, whatever tool you use, there are some limitations in what these tools can get. And the quality of PDF, in the most cases, comes near to what the customer wants in the end. And what we always, as well, see is that some planning tools are missing. So yeah, you can go for the big vendors. I don't want to name them here, which provide a real big fact editorial system. But for some cases, these might be overpowered. So when we investigated this interfaces, we figured out that there are more publishers out there than just newspapers and magazines. So there are corporate publishers. There are NGOs, government organizations, and everybody who's producing some printed or PDF content is, in this sense of the meaning, a publisher. And by providing our solution, we think that these media houses can use a professional and good-implemented publishing workflow as well. So what did we do? We created a JSON API that connects to Drupal's JSON API to directly read the content from the WebCMS and transfer it into InDesign documents. So our entire workflow is InDesign-based. And using this approach, connecting to our planning tool, which I will show in a minute, we see that any kinds of publications can be produced with this workflow. And we have a focus on a user-friendly and non-technical workflow. So there's no scripting. There's some configuration. But most of the configuration is done directly in the InDesign documents. Because the way the layout creates an InDesign document defines how the content will be formatted in InDesign. I provided three demo spots. And the first is about web to print almost without InDesign. And I will explain in a second why this is almost without InDesign. So what we see here is a Thunder page. And this is an article about hiking in Norway. So it's in German. I'm sorry about that. But you see that there are some formats in there, like headline two. There are pictures. Pictures have captions and stuff like this. What we see now on the screen is our web-based planning tool, where we create the publications. You can store them there. You can copy and stuff like this. So the foundation is to use InDesign documents that are pre-formatted in a special way. And these are uploaded to the server and can be loaded from the web UI to the pages to define how these pages should be formatted. When I assign a template document, you see that there is a predefined layout on there. There are some pictures. And there are text frames where the body text should go to. So now how do I place my content from the web CMS on these documents? So the easiest way is to go to a thunder to the content overview and drag and drop the article and drop it on the page. So the system sees that there is an article already prepared. And it's placed in the background. So the magic in the background is done by an InDesign server. And you see that's not only a copy and paste approach. So we see that there is the caption of the image or the formatting information from the web CMS is directly transferred into InDesign formats. So this is only very basic formatting. So when you have designers that are pretty good in InDesign, you can use grab styles and tons of formatting options in InDesign to lay out the text automatically when it comes into the InDesign document. So now when we have a look at the article in the web CMS, we integrated a preview of the layout of the article in InDesign that you can see inside web CMS how the placed article looks like on your InDesign documents. OK, now you see in the headline there could be maybe some more words or could be more interesting. So what to do about it? You go to your story in the web CMS and just change it. You apply the changes and the article is updated automatically, which means it could be a way how we can simplify correction workflows with customers by giving them access to the article in the web CMS. You see that as well, the update in the page dummy is updated as well. OK, so that's the first workflow, which is quite automated. And this is because our customers, they really love automation. And this is why we have this template-based approach, because when we analyze a newspaper, where we come from our magazine, together with our customers, we always figure out that about 60% of the pages are more or less the same concerning the layout. Even though we started discovery, they always say, no, this is everything very special. In the end, they say, OK, the overall layout of the pages is more or less the same. And this is why this automation, in this case, really offers them a lot of work. And so they can focus on the special pages where the layouters have the time to really do pretty good jobs on very special pages. So once again, just to point it out, that we not only copy and paste the content, so the images are placed into image frames and the caption is transferred together with the image. And any kind of formatting options in the WebCMS are transferred into the InDesign documents and converted into InDesign format information. OK, so this was a very automated process. So when we talk to the layouters who like to do their InDesign documents step by step and want to be creative in the layout, they say, OK, this is a part of automatic to what we need. So we would like to have the content in our InDesign documents and then have it there and layout and do something else. And this is shown in the next example. Here we will use an InDesign client plugin to connect my InDesign client directly to the WebCMS in the same way. So again, we start in Sunday. There's an article about the Tower of London. When I click again, it will start. And this article, I want to load this one into an InDesign document. So in this case, we again start in the web UI, but we can start in the InDesign client directly as well just by loading a document. And in this case, I have to tick the option that I will open my document in my InDesign client. So here you see the structure. And this is provided by our InDesign plugin. We create something that we call a content group. And this content group is nothing else but defined number of InDesign text and image frames. So you see when I click on one, everything that belongs to this specific group, to this specific article is highlighted. And this plugin provides a content search option. When I search for the London article, it performs a search in Drupal. It shows me the article with its components. And I see that there is an image as well. And now we can just drag and drop the article onto my InDesign page, places the image, caption is placed, and formatting rules are applied. Save the document. We will create a preview, which is shown in the page dummy, as well as in the web CMS. So now I jump as it was very quick, but I'm now back in InDesign in my InDesign client. Now, sorry, this has been the preview. And now we will jump to. So now we are in the InDesign client, and now we change the article in InDesign. Not the Tower of London. In this case, it's the Tower in London. The system indicates that there are changes to the document which have not been transferred to the web CMS original. And this update of the web CMS can be cut off, which means that we just have a print variant, and we don't want to update the online original version. We can automate it, or we can make it a manual process, as we did here. So I hit this little pen. So now the blue dots show me that both documents are in sync, which means InDesign and web is on the same level. And when I refresh my article, in Sunday you see that now the Sunday story is updated. So if you have a look on the top, there is a new card which is called Create Print Variant, because we are pretty much sure that you will never use your online stories one by one to have it in print. So we used an existing plugin called Create Variant and enhance it in a way that when we use an online story and we create a print variant of it, we will remove all the online specific content, like image galleries, videos that are embedded, and stuff like this. So we will prepare the copy of the story for being published in InDesign document. OK. So now the last workflow example I would like to show you is just called Layout First. Because we know it from our customers, they like to work with freelancers, for instance. But they want to give them a limited amount of space in the magazine, in the newspaper, or something like this. So in this workflow, we will start in InDesign. And from an InDesign article, we will create a corresponding article in Sunday. Again, I have to take it a second time. Same starting point. So the headline of the article will be the name of the article in Drupal. So I'll just give some names that I will recognize. So this is page 7 top, page 7 left. And the last one is page 7 right. So now our tool offers the option to create these articles in the web CMS. I have to do this three times because there are three articles to save the document in InDesign. Now we go back into Sunday or Drupal in the Content Overview. And we see that the three articles are created here. And I open to edit it. You see that we have an image paragraph, that we have body text. The title is taken from the original article in InDesign. And on the right-hand side, again, I see the preview. So working with freelancers, or somebody else, or if you just want to set the rules for your editors, this could be a useful workflow. And believe it or not, we often get the question. So I have an InDesign document. And I want to import this into Drupal or into the web CMS. And the workflow that I've shown you can be used for exactly this use case. Because when we create the article from InDesign, in the web CMS, we will transfer all the content of the article into the web CMS as well. So and this can be used for this, from my point of view, a little strange kind of workflow, but I learned that SPH is doing it right now. And they're pretty happy in transferring their content from Hermes into Drupal. And yeah, and if you'd like to do this, so the option will be there. OK, so these have been the three demo workflows. And yeah, so this approach works with a native Drupal. And we have the highest integration with the Sunder at the moment. But we try to keep the other interfaces on track as well. And we have the same integration with WordPress as well. So what we do, we see other benefits. So we see that there are no limitations in PDF options because we use the full range of PDF options that InDesign offers. And yeah, there are no limitations. And what we think from a customer's perspective or from the client's perspective, whenever they do add changes to their layout, when they change their CI settings, when they change styles, when they change fonts, or whatever, they can just do it by themselves in the InDesign documents. And if they are clever, they organize their InDesign documents as InDesign books. And then they have to change all the settings in the InDesign book. And it will be applied to all the InLine documents. And then we have to update the templates on our system. And all the CI changes everything is then used from that point on. And the client can do this by themselves in a tool that they know. So there is no scripting. There is no CSS style sheets involved, things like this. So it's a real straightforward, which enables the client to control the layout of their documents by themselves. So we've seen that we offer different workflow options with this tool. But there's an easy and direct exchange between online and print. That we have full text search options in the InDesign client and in the web UI as well. So I haven't shown this in the workflow, but in the web UI there is a search option integrated as well that I can do it from the web. And we see that there's a big option to simplify correction and co-working workflows because we have this centralized storage of the documents on our server. And everybody can access the documents on any place in the world. So wherever he is, he can just go to the page and open the InDesign document from the server instance. So what we are working on right now, and I hope that I could have shown you something in another video, but as you know it, things are not always ready in time. So sorry for that. What we are working on right now is the support of custom paragraphs and blocks and header elements. So we see that, especially in magazines, there are some kinds of like a subhead line or there's an author box or a short message box or some special text elements. And what you just can do is in Sumner you can create new paragraph types. And the only thing that limits is that they have to have the field type text and you kind of the text field types in them. And the next time, so when you create them in Sumner and we restart our server, these new paragraph types will be recognized automatically by the system and can just be used without a lot of administration working in the background. Another topic that we learned when we talked to agencies that are doing financial reports for their customers is that the import of tables, Excel tables from the web CMS into InDesign documents is a real hard topic together with the import of work documents in general because in this case, the customer receives all the original text from their customers as a word in Excel and they spend tons of time by copy and paste word into InDesign documents and the next update, they just lose all the layout work that they put into the InDesign documents at this day. So we've shown in this approach and they said, okay, this looks pretty good. So just import the word documents into the web CMS and then go on to InDesign. Can you do this for tables? We said, we have to think about this. This is what we are in at the moment and tables are a little challenging at this point. And because we have good context for the Arabic word, we are working on the full support of Arabic publications, so right to left. And my favorite slide at the end is Arabic Sunder version that we used and whenever I get some questions about configuration, I have to have an English version on the other screen that I can just get along with this slide to left Sunder. Okay, so this is the end of my session. So thank you everybody for being around and yeah, I'm happy about your feedback. Any questions? Yeah. Can we test this module or? Yeah, so right now as we are just, as I said, we started at the beginning of this year, so it's not available in any kind of marketplace, but if you're interested, I can give you my business card and we can talk about giving you a demo access for a limited time just to check out and see, so yeah. Could you export all the pages to one InDesign file? If you create the pages. Yeah. Could you handle that to one InDesign file which can go to a printer? Yeah, so actually what we do is, yeah, so it depends on how you set up your template document, which is just one document. And this is in the system of InDesign file, if you want to send PDFs or if you want to send your printer in your own tool, that's the PDF simulation work for already included because we used to create high quality PDFs as, yeah, from our foundations that we know how PDFs have to be represented. So this will just come along with the web UI or we have several PDF profiles that we can use and we can make really good use of PDFs that we can send to the printer. And if you have, say, the products of a certain product family, is it possible to add those, say I want to generate one PDF file with products of one family? Say, one product can be, or you have cars from a certain brand and one PDF file with all the cars from that brand. So right now, it's not, so it's on the web UI and every publication is a single entity. So right now we can just create PDFs for the publication. But there are a few options there. In this case, if you have like five publications for the company, you can use a Twitter, you have them all on screen and then you can produce PDFs for the publication. Are the images embedded in the papers? So they're embedded, they're not, say, separate or uploaded in the paper. Yeah, so image replacement, yeah. Okay, so it's an image inside the InDesign file. It's not linked outside of the file, but it's inside, so it makes the InDesign file very heavy. Yeah, so this is a question about how we set up a work field. So we can use this, we can work with low-res and we'll just do a layout process so we can create what people ask and we can just do things that are just very high-res solutions. Can you elaborate about the different interfaces between Drupal or Thunder and InDesign server, so the web UI, which technology can use for this? Yeah, so it's, for the web, you use React, so I'm not a technician. Yeah. I'm a product manager, so... Is it a React interface for Drupal or Thunder, or is it a different technology built? Yeah, it's outside. Okay. Yeah, so this is our closed source. Soft source, okay. Compoundment, yeah. And the InDesign plugin you use, is it also closed source and is it the component of the UI? Yeah, okay. So, you know, it's not necessary, so the InDesign plugin can be used without the UI speeds. Okay, so you don't need the VendUI, you can work with the plugin and just Thunder and the plugin can communicate. And so, more or less, so there's a sort of component in the background, but I'm really not worried, but would love to know. The plugin, maybe, which language is it? Written and how complicated or how much time you've spent on it, and how much time you've used, to get used to it, is it led over to do so, or can you just download the API and start programming the plugin for InDesign? So, on the InDesign plugin, we've been working for, I don't know, 15 years. Okay. That's great. Yeah, so we're here at Adobe Server Partner. Okay. And the company level, and so we have full support of Adobe Server. As I mentioned, so part of the component is an InDesign server, so we run and host and multi-instance InDesign server and potential customers will just get an instance or two depending on how much traffic they have on this InDesign server, which will remarkably reduce the costs for having an InDesign server environment. So, when this is closed source, what will be the price range to be expressed for that? Yeah, that's a pretty good question. So, we talked about the usage of the InDesign client, plugin, Adobe. This could start from about, let's say, 15 years in a month, which is the smallest one, and then we have different ranges that have different functionality options. And so, this setup that we've seen here in the demo would be, I think, about 1,000 years in a month, with a given number of users. So, usually, I think, 10 users into this package and the revisionary users, we just add. So, we see that the solution actually should be to lower the price of that one. One benefit that we see is that when you go for a real editorial system, you have to pay all the seats that you have in the editorial system. You have like 500 editors working. You have to pay a lot of money for the seats in the editorial system. And in this approach, using open source web CMS as the editorial system, we would save all this costs. So, yeah. Real-time collaboration. We have one user, but not here. So, we saw that you created a node from within InDesign. So, you created those three articles. Mm-hmm. That's most of the sticks. If you were to add an image in InDesign and have it create a node through Google, would that also improve the image? Yeah. So, if you're interested in a demo accessible sensor like this, give me my card and we'll be happy to talk to you afterwards. And then, as soon as you come back, we'll talk to you as possible. Okay. So, yeah. Thank you for your attention. Have a nice evening. Thank you.