In torque’s last article on thinking like an app, the mobilization of WordPress did not deliberately change the way of access development from the perspective of determining the objects to be built. In this release, I will introduce my thoughts on the technical changes that occur in the actual development process. Remember, for now, when talking about WordPress application development, we are not talking about building reusable applications, but about building specific applications for specific purposes, similar to writing plug-ins and writing plug-ins. theme The
Like many of the plug-ins and themes we have today, the reusable part of the rest API may be on the economic horizon of creating word press applications. But we’re not here yet. We’ll have to wait for how it works. What criteria still apply? When you start using an application, you can draw what you have learned in theme and plug-in development, but not all the same rules apply. This is mainly because when you create a specific site, you do not create code to distribute to the thousands of sites that usually occur. When developing a web site, make sure that the client can replace themes, plug-ins, or custom code, and that the web site works properly. This modularity was an important reason why WordPress was first used to create sites. The
I think that when building an application (although it may be wrong), assuming that it is \
When working in web applications, it is always meaningful to follow the word press online document standard and psr-4 standard for file naming and structuring. Some best practices are not important to me. For example, in a recent application project, you did not use wp_enqueue\u script to add JavaScript or CSS files for my application that were not added as plug-ins. Links to scripts or stylesheets in hard coded HTML headers are considered bad habits in client projects or themes. However, hard coding makes it easier for non team WordPress developers to read my code. You can also shorten the initial page load time. In this case, although it is a small thing, for the sake of safety, if you start thinking about everything you usually do, you will soon realize how these small things are cost-effective. The
In addition, the location of the code (such as theme, plug-in, Mu plugin, or other locations) is also very different. You don’t always have to think about themes, plug-ins, or even the entire word press. In many cases, it makes sense to build a must use plugins or mu pugins directory. In plug-in development, it is unreasonable to assume that end users will integrate with other PHP frameworks, such as laravel. But if you want to build half an application on laravel, you can. Or, if for some reason it makes more sense to use symfny’s event router instead of WordPress hook up, continue. The
How to obtain permission? Word pre for deployment
