Does the user use the WordPress backend? Not all applications require user interaction and front-end data input. But many of them do. For this type of application, you may need to create a front-end interface for the interaction. It is important to understand which interaction components and what types of data need to be entered. The next section describes whether the front end should be separated from word press. When you think about it, don’t forget to think about how users submit the data they need. Building an interactive UI using the form builder plug-in can save time if the front end is not detached. The
Male caldera forms can generate many parts of the UI and inherit layout tools, verification, deletion and project tracking, thus saving a lot of time to reach MVP. For all selected form builder plug-ins, make sure that you can easily move form configurations between environments. This usually means choosing not to save the form configuration to the database. In addition, most of these plug-ins are not designed to work in this situation, so consider what it would be like to separate the front end of the application from WordPress. The
Do you want to disconnect the front end? One of the reasons I use WordPress is URL mapping. That is, WordPress is used to create a response from the passed URL and execute a query or return an error page based on the URL. WordPress’s URL mapping enhances the templating system. The system is powerful, but may not be suitable for mobile applications. It also includes a lot of unnecessary overhead processing that is closely combined with the existing way WordPress executes queries. This feature may duplicate API requests executed by the application. The
This is why the front end is separated from WordPress. But the main reason I like this is that it is easier to build multiple front ends for various platforms such as web, desktop, IOS, Android, windows mobile, etc. Node Made a trilogy series, showing the proof of concept of JS and a single page web application based on WordPress rest API, which is completely different from the WordPress front end. There are many other examples, such as k.adam White’s expresspress. Roy Sivan’s angular theme and plug-ins are good examples of the opposite approach. That is, build rest API based applications inside WordPress. The
Both methods have advantages and disadvantages. I am happy to use a separate front end. But WordPress is my core competence, so there will be problems. Before I master the front-end framework or become a partner with someone I already own, I will continue to return to the WordPress template and routing system I know. Is the MVC framework used on the front end? Many people assume that to create an application, the model view controller (MVC) pattern must be implemented. This is not true, but the MVC framework is very useful for creating maintainable and extensible applications. Carl Alexander provides a good argument for why MVC is not suitable for the traditional use of word press. The
This does not mean that the MVC framework is not available. All we really need are restful APIs such as WordPress and familiar language frameworks. We are WordPress developers (such as PHP and JavaScript developers), so for the MVC framework
