 So, hello everyone. So, this is my first English session. So, little nervous. Let's get started. So, hello everyone. For now, I'd like to talk about how can SIM developers monetize in the era of block things. First of all, okay. First of all, my name is Ishikawa. I'm a WordPress SIM developer. I came from Japan. In 2012, I published my first business WordPress SIM on my site. In 2015, I published the same lightning on WordPress.org. In 2022, I published BlockSIM XT9 on WordPress.org. I also make a living by developing and selling SIM extension plugins and other plugins. Like me, the business model of a SIM developer is create and sell premium SIMs and plugins. These were the... Let me see. I think these were the mainstream. We could simply create a SIM and sell it as a zip file. It was relatively possible to sell and make money. Points where monetization has become more difficult. Number one, traditional monetization points become less effective. Before FSE, SIM developers developed SIM with unique editing functions and sell premium SIMs. User can easily edit. SIM creators could get rewarded. Such a relationship existed and there was one monetization point here. However, in FSE, a user can customize the entire site with no code, just standard WordPress features. This makes it much less dependent on the SIM. Then as someone who made a living out of the SIM sales, the monetization point disappeared. And it is a matter of life and death. Number two, decreased monetization effect by original block features. Early stage block editors had poor editing capabilities. So we have developed original block with various adjustment functions and layouts and use them as added value. However, by the WordPress banjo applet, advanced layouts are now possible with core block and block patterns, and similar functions have been added to core blocks again. So monetization point disappeared. In addition to once released original blocks become an ongoing maintenance burden, and it becomes necessary to keep a close watch on Gutenberg's development. Number three, CSS output by WordPress become quite complicated. Probably many of the SIM and custom block developers are facing this issue. However, it is inevitable in the evolution of WordPress. In this way, the areas that SIM developers have focused on for monetization is greatly influenced by FSE. As a result, I feel it has become difficult to monetize traditional SIM sales. Future direction of SIM related business. How added value and differentiated? First, we can consider... First, we can consider differentiation by block patterns as the easiest way of selling SIMs and plugins that include various block patterns. However, as I mentioned earlier, there is nothing that users cannot create on their own, so it is weak as monetization. The second is differentiation by global size variations. It is future introduced in WordPress 6.0. This future allows us to create different variations within a single SIM. These block patterns and global size variations are even generally users can make it, but high quality products created by professional designers are naturally having a high added value. These are the new extensibility and monetization points that WordPress has provided. In our case, before FSE, we used to sell plugins that extend the functionality of the SIM. However, expected to tap off due to reliance on the SIM, even if they sell only that pattern, it seems to be difficult because even users have the impression that they can make them on their own. In addition to, we have to move to block SIMs too. Therefore, currently we are selling license with premium patterns and premium pattern added. This configuration is user can use both the classic SIMs and the new block SIMs and keep existing users by the value of the premium patterns acquire new users through the value of our premium patterns. The block patterns is extremely important. We published our own block pattern directory. This is a site similar to official pattern directory. How we created our own pattern directory? Because it's still difficult to only core blocks. I wanted to use my own original box to provide more practical patterns. Practical patterns can be motivate people to purchase licenses. Second, there is a language program. Characters look different in English and double byte characters. For example, even if it looks not bad in English, but in Japanese, the balance is bad. The third is the effect of the same styles. Even if you paste the dot org pattern, users need to make some adjustments. For us, we need to make an effort to get users to continue to license even if the dependency of the SIM decreases. Then how to increase product value? At first, premium patterns, as the name suggests, the patterns are available to only paying users. The design and sample sentences are more elaborate and ready to use. Of course, we provide stylish and common patterns, but actually non-professionally users can't think about page structure in the first step. And they can't think of the sentences to write. Therefore, we are providing a block pattern to create a whole page of a specific page for a specific industry. There is, for the end user, they just rewrite the text to suit their business for the commission creation by using the pattern as a draft of the page, the meeting with the client becomes smooth. When providing the pattern for the entire page including sentences, it must be in the language of the country, and the design optimized for each language is better. For the more content and design trend, the value by region. Localization also has the benefit of non-competing with English-speaking developers. Second, favorite pattern registration functions. This function allows users to register on favorite patterns and easily recall them. Third benefit is link function for favorite registered patterns. Call patterns registered in favorites from the user's site with the API. Then users can use it directly from the edit screen of the site. About whether the theme business is dead. I feel, after all, the theme is important. The theme and the patterns are closely related to the global size, even if you bring in a practical pattern from outside and use it. There are many cases where there is a problem with the uniformity of the design. Even in the era of FSE, users need good themes and highly practical patterns. FSE is highly configurable and customizable, but too much configuration work. Actually, it's quite cumbersome to make from scratch. Additionally, the website must adapt to different screen sizes, how to control the display element according to the screen size. With a single screen width, it might be possible to layout somehow. However, when it comes to layout on multiple users, it's actually not easy. I feel it will be difficult to monetize the theme alone, but considering it as a set with value-added patterns, there will be many business opportunities. At the end, what do you think about the future theme business? Please share your opinion on Twitter or talk to me. Thank you.