Summary
Our main goal was to find out how WordPress fits into web application development. We started this chapter by identifying the CMS functionalities of WordPress. We explored the features and functionalities of popular full stack frameworks and compared them with the existing functionalities of WordPress.
Then we looked at the existing components and modules of WordPress and how each of these components fit into a real-world web application. We also planned the portfolio management application requirements and identified the limitations in using WordPress for web applications.
Finally, we converted the default interface into a question-answer interface in a rapid process using the existing functionalities.
By now, you should know how to:
- Decide whether to choose WordPress for your web application
- Visualize how your requirements fit into the components of WordPress
- Identify and minimize the limitations
In the next chapter, we are going to start the development of the portfolio management application with the user module. Before we go there, I suggest you do some research on user management modules of other frameworks and look at your previous projects to identify the functionalities.
