 Good afternoon everyone, welcome to my DrupalCon, I am Shreya and this is my first DrupalCon ever and I am speaking on the digital transformation from print paper to news and media with Drupal. So this is a small introduction about me, this is Marina Ben-Sens, I am standing in front of it. I am working with Drupals in 2012 and I am working with Singapore Press Holding as a technical lead. This is my Drupal.org profile ID, you can teach me about them. Talking about my recent work, I have recently developed a ThinkChina.sg, the news portal built in Drupal 8. We use cloud, we use containerized architecture, we use blue and green department process. And yeah, we tried our best to match with the real world. Speaking about the SPH, we are now celebrating the 35 years this year and we have around 2.4 million readers across 18 global news papers, more than 900k copies per day, more than 4k staff employees across 3 centres in Singapore and 8 news bureaus overseas. We have more than 500 plus ad partners located in different places across the globe. Speaking about the servers, we have more than 200, 2200 on-premise servers, which is including units, IBM cloud, IBM and mainframes and Windows. We have 150 plus cloud servers, which is hosted on AWS and GCP. We have to manage all the shops, we have around more than 250 tech employees. Looking into some of the products of SPH, the straight times, which is having the highest reach across Singapore, which is having the more Indian ways, the straight times and the Sunday times. We have the Chinese news publication, which is Zhaobao, Wanbao and Shinbin. We have Tamil news publication, which is Tamil Morasu. We also have Malay language publication, Baritarian. Thabla, which is more focused on Indian news. We have a centralised news bank, which provides the data to the external clients. We have the news links system as well. Let's look at the numbers of the straight times, which is having 800 K prints, daily print readers, more than 2 million, 2.8 million unique visits, monthly, more than 30 million pages views monthly and averages and time per user is 2.5 minutes. Looking at another news web publication, the Zhaobao, which is having 386 K news print papers daily, which includes Zhaobao, Wanbao and Shinbin. We have 750 K monthly unique visitors on the Zhaobao side. 14 million pages views per month and average time spent per user is 4 minutes. Zhaobao is also accessible in China, so we have Zhaobao.com, which is the numbers are great more than this compared to this. Now, let's look like where from the digital transformation part of you, where we need the transformation, which are the areas we can focus on and we can improve on it. So, now the editors, there is a new definition of the editorial products. The editorials are very smart enough nowadays. They require new features each and every day to publish the news articles. And they need new features and every... So, they ask for auto tagging of the images. They ask the auto tagging of the articles. They ask the content recommendations, which is auto-served. So, there is a scope of transformation in that field as well. So, each and every editor as well as the user should be having the product expertise. And there is scope of analytical enhancement where we can have a real-time dashboard of which article is trending more, which article is more performed by each and every editor. We can show the dashboard with real-time data based on the real data. We can suggest the articles to the latest trending articles. The technological enhancements as we saw yesterday in the Drupal Initiative, there is much more initiatives in the workflow, workspace, content configuration management, everything. That's why we use Drupal. We feel Drupal is the best solution for news and website, news media publications. From the customer point of view, why there is a need of digital transformation. So, customer is continuously looking for the opportunity to experience media uniquely tailored for their own personal references, context and schedules. So, the consumers are never idle and they are mobile and they need greater control of how and when they need to experience the media. This is a very classic example. In the previous ancient days, the family of four used to watch pictures or movies together. But nowadays, each and every user, their own preferences and choice, a father wants to see different news channels, a mother wants to see different channels, serials, and kids used to see movies or cartoons. So, there is a much more scope based on the personalization and based on the user data. We can do digital transformation. Let's look at the numbers, how digital transformation is much needed. This is the global survey done by PWC where we can see the average CAGR is increasing from 4.3% within the next five years in news and media companies. So, this is the projected numbers by PWC. Talking about globally, the revenue of digital news and media is 53.1% in 2008, while compared to 2019, this continuously steadily growing up from 55 to 57 till 61 is the projected score by PWC. So, 61.6% of global revenue of total revenue comes from the digital revenues. Let's go into more deeper into the details. These are the projected numbers percentage for the next five years. We can see the news and consumer magazines are declining for next five years, whereas internet marketing, OTT videos and VR is continuously growing for next five years. So, we are more focused into digital advertising and internet marketing. Some more insights on the news conceptions of age-wise and device-wise by survey done in 10 different countries for more than 2,000 people. We can clearly see the smartphone users are having high numbers and desktop and the green media is continuously declining. As we already heard in today's DRISNOT, there is a huge increase in globally internet access from 20 million to 300 billion till 2030. So, we can see the scope of news consumption digital is very much important. Let's look into the numbers of how SPH is performing. This is a comparison of print versus digital. The daily average print of straight tanks is declining from 2017 to 2018. As we can see, every publication's digital numbers are increasing while the print numbers are declining. So, in order to get the digital audience to consume the digital customers, at the start of this year, what we have done is, in order to engage the customers, we have launched a Samsung News Tablet which will provide the e-papers. They don't need to download the e-papers and they just need to log into their Samsung Tablet and they can get access to the e-papers which they are subscribed monthly or yearly. So, this is how our marketing team is engaging the audience and gathering the customers very more frequently to increase the digital revenues. So, talking about how digital transformation would be helpful in terms of news and media. So, it would be more helpful in terms of content planning. We can get the audience data, what formal data they do, they read the access and we can suggest the customer audience that we can recommend articles related to their own preferences. We can provide a better UI, look and feel. We can provide an on-site and in-app readers' access. We can provide subscription and pricing promotions. We provide different paywall messages, show different paywall messages for different users. So, users of different countries should see different paywall messages. We use the data to understand the reader's attention, spend and retention to drive lifetime values. There is a scope of revenue diversification to develop the known core products and service using the reader insights and the behavior. Talking about how Drupal is making an impact in SPH. How we use Drupal and based on the news and media publications. How Drupal is making an impact. All the major publications of SPH digitally are powered by Drupal. Right now they are in Drupal 7, but we are running a migration of Drupal 8 and on cloud. Drupal is working as a backbone for all the mobile apps. There is a continuous stimulus integration from print article paper to the Drupal website. The articles which are printed on the physical copies are also published on our website. There is a continuous stimulus integration. It can be real-time or it can be on Chrome jobs. All the major websites are responsive. More the audience of Drupal websites are from the mobile. They are responsive. We have different languages publications and we support multilingual websites. We have some microsites for Zhaobao. We have small projects for Delta and Drupal China. So we build the microsite for them and we are planning to go with the multilingual architecture to have the same code base and how each publication will access the same editorial behavior which we will see and discuss later on. Yeah, this is our responsive website. If you get a chance to look into Zhaobao, not SG, this is the responsive website for it. So this is the print article flow which flows into Drupal. There is a print editorial system where editors create an article into their editorial system which gets published into the physical paper which intends the articles flows into Drupal and Drupal intends which serves to the website, mobile app. We have Google AMP pages. We integrated a Facebook instance article. We have some external clients as well and so basically there are some external vendors which wants access to Drupal articles on monthly or yearly basis. So we provide an external subscription model on monthly or yearly basis so they can consume more articles from Drupal. We provide newsletters as well to retain the customers to get the daily news articles to their emails. It's also powered by Drupal. This is a three-step custom model built in Drupal where editors can select the template and pick the content they want to send out over the email and then check how it looks like before sending it to the actual users. So they can select the content templates. They can select the which content they want to send to the end user and after selecting this, this is how the email template will look. Before sending. So when they click on sending mail, it will go to the test users and after confirming, we can send them to the actual users. We also target, so there are two newsletters, the daily, morning and evening. So we also target the users which haven't access to morning newsletters. We target them differently to see the evening newsletters. This is the most recent feature right now. We have developed on, which is single sign off. Let's say there are two different publications. One is straight times and other is business times. So when the user is logged in into, so user is subscribed to straight times but not to business times. So when user is logged in into straight times and when he goes to business times, he don't need to log in. So based on the user behavior on the straight times, we track the user behavior, which articles we've watched, which category is used to differ and how much time he spends. Using the GA, we will plan to provide the content documentation on all the different publications of all the page publications. So if I go to business times, I have a business time subscriber and I watch the stock news and again I go to straight times. I can see the content recommendations related to stocks at the bill of the articles. This is the most amazing feature, which is content recommendations, which works differently from what I talked previously. So on the homepage, we have two different sections where we have set content recommendations. It's based on the user location, based on the user behavior, based on user average time span. So on every page, it will show different articles, so every time they won't see the same article daily. Talking about the dynamic paywalls, some of the articles are premium articles. So we show them a message at the end of the articles in order to subscribe, in order to see the full articles, you need to subscribe or log in. But the message which is shown at the bottom of the articles are different for all the users. It can be different for different devices, different for different countries, and different for different types of users. Talking about the three in CMSCF. So talking like we have all the Drupal 7 websites, it's on in-house, on-premise servers. So our plan is to migrate to Drupal 8 first, to cloud them, cloud them to Drupal 8. So as it is new in news and media, there is lots of bot attacks or daily going on, so we want to prevent them. There's lots of redundant work going on. So let's say there's a straight dance, and there is a Zauber. So lots of redundant work when we say, so if we do a G implementation on Zauber, same needs to be done on straight dance. But different users and different developers and different types do the same task, which increase our workloads. You want to decrease that. And right now the editorials system is different, and Drupal system is different. We want to make it one. This is the architecture of how our Drupal is being seen as what we have planned for. We can see there is a Drupal core and contributed modules, which will work same for all the publications, which is, there are some Drupal contribution modules, which is also common for all the publications. So we put them into a separate Git repo. There is a separate Git repo for dedicated custom and patches for each publications. We will use the composer to fetch the latest data from each Git repo, and each publication would have the same code base, same Drupal instance, but different. But it's a totally different instance. You are taking it very short. That's all. If you have any questions, you can reach me on. And this is a Drupal.org ID, and you can find my slides on this URL. Maybe time for one urgent question. You don't have to use that. Okay, could you describe a bit more how you used the content engine, the recommendation engine? Place one? Yes. So there are two ways we do it right now. We have integrated with the c-sense and handshake. So there are two different c-sense here. So there are two different companies. We integrate the JavaScript into our system. They track the user behavior, and based on that data, it shows dynamically every time. So it's not an integration? It's not right now, but our plan is to do that. Thank you very much.