Summary
Our main goal was to find 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 features of WordPress and how each of those 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 existing functionalities.
By now, you should be able to decide whether to choose WordPress for your web application, visualize how your requirements fits into components of WordPress, and identify and minimize the limitations.
In the next chapter, we will start developing the portfolio management application with the user management. Before we go there, I suggest that you research user management features of other frameworks and look at your previous projects to identify the functionalities.
