 Thank you for attending my session. I'm Seiji Akatsuka from Japan. And this is the first time for me to deliver my presentation in WorldCamp. So I'm very happy to be able to take part in our workplace Singapore. So let me introduce myself briefly. I'm working for Digital Cube as Customer Success Manager and member of WorldCamp Tokyo this year. And it will be held on November 1st and 2nd. So please come and visit Japan. There are more than 1,000 people will attend the event. So you can find and make a lot of friends through attending some sessions and a variety of activities and also some parties in Japanese Rio Karaoke. And this is one of the organizers of WorldCamp Singapore. And this is my agenda. I'd like to talk about why, how, what using Jumpstack approach to WordPress. Firstly, I'd like to share about reason why I'd like to recommend it. Jumpstack is an architecture which can make our website more faster, easier to manage, cheaper to scale, and more secure. So it provides us much better user experiences. So that's why it's better to try this approach in some specific cases. In use Jumpstack to WordPress, there are three elements. Jumpstack, a new architecture for web developers on your left side, and the people who are publishing articles like me is on the right side. And in the middle, there is a way to connecting Jumpstack and people in its WordPress. So let's dig a little deeper to these elements. So first element is Jumpstack. According to Jumpstack project, it offers us a new web-developing architecture based on JavaScript, client-side JavaScript, and reusable APIs which handle data transfer and communication building microservices, and pre-built markups. So basically, using Jumpstack to WordPress, some kinds of plugins like e-commerce, marketing, and some other features which need data transfer and PHP must be updated to some microservices. And this is a basic architecture for Jumpstack. All the code is distributed to CDN to reduce load time of each pages. So Jumpstack website do not need to rely on server-side code. So they can be distributed to CDN much easier and also can deploy every version of site whenever we want. And sometimes, generating static markups takes a few minutes or more. We need to do ultimate deployment like blue-green deployment to eliminate downtime during Jumpstack's deployment. So Jumpstack website fits these cases. For example, company site, landing page, and job site are typical cases. Because these are almost stable. And seasonal catalog sites are usually updated once or twice a year. And for the event, when we are done on our tasks, we do not update it anymore. And second element is people who publish articles. Jumpstack is a wonderful idea for web developer and visitor for our website. However, if I were in this situation, I would like to ask to use Gutenberg or any other page builders. So because I need to put a lot of blog posts almost every day, and I'd like to ask my colleague to check my posts because it is the best way for me to collaborate with each other. For the last element is WordPress. I think WordPress is a bridge between Jumpstack and people who publish articles because we can use great page builders, manage posts, and the great, beautiful things, useful plugins, and also can use WordPress dashboard translated into multinational languages by WordPress community. These are notable values of WordPress. And my second topic is how can we bring Jumpstack to WordPress? I'd like to share about three patterns. This is a simplest pattern to go static because there are a lot of plugins to translate to static and also can deploy to static site hosting like Amazon F3, NetRify, GitHub Pages, and so on. It is a good idea to use these plugins because we can easily try a Jumpstack approach with our previous site. And second approach is to use headless WordPress and static site generators because it is a good idea for web developers who use to static site generator like Gatsby.js because it can use many kinds of data sources, including WordPress. And so they can choose their favorite static site generator. And their clients also use WordPress as managed posting as usual. And third pattern is to use these all-in-one hosting services. It is the easiest way to go static, not only for web's WordPress developers but also static site generator people because we don't need to care about any server-side environment. And WordPress also updates it automatically. So these services consist of managed hosting for WordPress, static site generator, and static hosting service. And some service like Shifter has integrated to other environments like Netrify and also integrated to static site generator like GitHub pages, GitHub and other static site generators. So I think these services expand WordPress ecosystem to outside WordPress developers. And my final topic is about what changes can jumpstart makes for WordPress. The biggest change is that PHP cannot work in this environment. For example, when we are using some contact form on our website, we need to use some alternative way to enable it because PHP cannot handle data transfers. And also other features like search, comments, e-commerce, and other features which need data transfer and PHP must be replaced with some alternative ways. So Jamstack refocused the server-side dynamic rendering via PHP to client-side, static site, client dynamic rendering via JavaScript and APIs. In conclusion, I mentioned about these things. Firstly, Jamstack provides us much better user experiences. That's why it's better to use these approaches in some specific cases. And secondly, there are many ways to bring Jamstack to WordPress. I mentioned about three patterns. And lastly, Jamstack refocused the server-side dynamic rendering via PHP to client-side dynamic rendering via JavaScript and APIs. It makes our website more faster, easier to manage, cheaper to scale, and more secure. So let's bring Jamstack to WordPress community to make all of our collaborators happy. Thank you very much. Thanks for saying. Don't be shy. We still have five minutes. We'll be back. What does Jamstack, how does it work for you? Does it use PHP? You are no longer working with PHP. That's your topic of use, I don't understand. Yes, Jamstack WordPress uses static-side generator. So the website combats the dynamic WordPress website to static HTML and provides through CDN. So basically, Jamstack uses HTML. Yes, static markup, they say. Shit. Yes, yes. They, if we don't have a CDN, so is then really easy to use? Sorry. We only have N to N, and we don't have a CDN in the middle. How do we use that? Ah, that's true. If they don't have a CDN, how do they use that? Ah, we don't need, we don't have CDN. We usually have, we always use some NetRify and any other CDN service. Yes, so caching is very important. Final questions? Thank you. Suggest launch an e-commerce site on Jamstack WordPress? Ah, yes. It's the most important question. I think there are some service, South Service, Shopify, and just simple shopping cart is OK. But if you need full-scale shopping sites like WooCommerce, it doesn't work on Jamstack's environment because it needs a very difficult to control cache control. OK. Everyone, put your hands together to say thank you. Thank you. Thank you. Thank you. Boo.