About three years ago, I said to torque, \
In his presentation, Ryan talked about the need to prioritize developer experience. Often, the core decisions of WordPress are made in a user first manner. It depends on the advantages of the user. And it’s great. WordPress needs a website that runs frequently and provides services for bloggers and SMBs with similar experience in their own managed WordPress. Com or studio press. It will be dominated by COM and other platforms. This is an example of a method that WordPress uses in an unconventional way. The
There is a problem here. I am one of the strongest supporters of using WordPress as the back end of an application. In the process of learning angular and vuejs, I told everyone to learn oneortwo JavaScript frameworks and use them with WordPress. However, at the end of this article, you will begin to connect the built vuejs front end to the back end, which is caldera space’s web application to extend the functionality of caldera forms. The back end is built by laravel. I feel guilty about this, but I don’t think that as long as PHP development is carried out, it can defeat the developer experience of laravel. The printing press is not near. That is the problem. The
The modern FTW WordPress rest API is an amazing tool. Can be greatly expanded. The infrastructure for creating custom rest API paths performs very well, providing developer experience that cannot be seen elsewhere in WordPress. The rest API provides a flexible and extensible abstraction for current HTTP requests. WordPress is not anywhere. Rest API endpoints declare an architecture that can be read by people and clients. The custom field used by the WordPress post type does not have a schema defined. Wp\u http\u request object is not available in other contexts. The new wp_hook class does not provide a parameter registration type for the hook. The
The most important modernization of WordPress API – wp_rewrite, working system (wp_cron), plug-in API (hook) and other functions are not user oriented. None of them is a priority for WordPress 4.8. However, if the user cannot see the improvement, the idea that it is not important is the wrong equivalence. I think that users need results, and the results come from developers who have tools to complete tasks. When building the traditional word press website of FTW decoupling, a cool thing is that plug-ins can do a lot of things. However, plug-ins tend to be very tightly integrated with the traditional word press request lifecycle. The
Plug ins are a major part of enhancing word press. However, if the current plug-in stack becomes a part of the era of WordPress platform, as a developer, all other parts of the plug-in must be separated before the developer can choose to use a part of the plug-in
Woocomerce excels in code rewriting crud objects. For example, e-commerce is difficult. Products, customers and payments require infrastructure. If you want to use WordPress to drive SaaS with a front-end separation front-end, you are likely to use it separately from the standard product display and shopping cart. The
I recently wrote about adding a rest API to my plug-in caldera forms. The forms plug-in provides a front-end form and data storage layer. Although it is difficult to separate the two, making the storage tier separate from the standard format, it helps to improve the additional functionality to process items in a new way. Help other developers meet client requirements. No one will use \
However, the job of creating a better developer experience for WordPress developers will be better and cooler features that can be listed on our website. The open source FTW WordPress plug-in is just part of the amazing list of open source tools that come with WordPress. Far fewer tools use the WordPress rest API in an unconventional way. It is a function of time and will change. There are several excellent examples of open source tools that allow you to use WordPress’s innovative new methods. For example, nodejs client of nodify WP platform and WordPress rest API is used to build moxie lean stack, realt and WordPress into isomorphic web applications, and use angularjs with existing plug-ins. We need more of these and open source them. The
Part of the problem is that they ignore existing containers in WordPress. Does not match the plug in or theme boxes. So they can’t get the same support as others. It should be noted that before PHP 7 FTW ends this post, you can use PHP in the past 10 years to modernize word press. PHP has come a long way since PHP 5.2. If you want to seriously consider becoming a platform that prevents us from building our own web applications, you must stop supporting PHP 5 as soon as possible. The l*mp managed stack that brought us here will not take us where we want to go. Setting up PHP 7 as a WordPress hosting required is not a recommended first step. Of course, you can also use node as a part of the stack, but don’t be too greedy
Please look at me. I’ve been seriously discussing WordPress tattoos recently. Because I am a member of this community, I love what it gives me. But if you want the word press to become the foundation of the modern network, you must take the technical debt seriously. WordPress has infrastructure problems. I want us to give priority to paying off these technical debts because we put end-user experience first. As I said before, I will end this article and return to the laravel application. But first, let’s take a look at the scope that WordPress needs to create whole or part of an application, not sandwiches and work periods. I will share what I have learned.
