cms应用程序的mvc方法
你好，我的任务是用 php 创建一个相当复杂的 Web 应用程序，它是一个自定义 CMS，能够复制 WordPress、Joomla 或 Drupal 等知名内容管理系统提供的功能和特性。我将尝试将这些众所周知且强大的系统提供的尽可能多的功能集成到我的应用程序中。当然，我要遵守的另一个条件是从头开始构建一切。
我倾向于在构建主应用程序时采用 mvc 模式设计。不过我以前没有在这种规模的项目中使用过这种设计。
我的问题是针对那些在大型复杂应用程序中使用过mvc的人的。我想知道这实际上是否是正确的方法，以及在这种规模的项目中我可能会遇到哪些陷阱。我还想知道你们中是否有人使用不同的方法创建了相当复杂的 cms，以及您将如何构建这样的应用程序
Hello I have been tasked with creating a fairly complex web application in php, it is to be a custom CMS that would be able to replicate the functionality and features provided by well known content management systems like WordPress, Joomla or Drupal. I am to try and integrate as much of the functionality that these well known and powerful systems provide into my application. And off course one other condition i am to comply is to build everything from scratch.
I am inclined to go for the mvc pattern design in building the main app. Tho i haven't used this design on projects of this scale before.
My question therefor is destined to those of you who have used mvc in large-scale complex applications. And i would like to know if this is in fact the right approach and what are the pitfalls that i might come across in a project of this scale. I would also like tho know if any of you that have created a fairly complex cms using a different approach and how would you structure such an application
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
就我个人而言，我会保证模型-视图-控制器类型的 CMS 比其他任何东西都重要（特别是如果您是开发 CMS 和基于它的项目的人），但是实际的业务分离可能不会影响您的整体应用程序设计。
例如...
总而言之，MVC 架构只是一个基线，用于说明在创建新功能（编写代码）时如何区分不同的关注点和业务价值 - 创建新表单、列表、工作流程、导航结构、聚合等。但是，应用程序 (CMS) 的实际架构取决于如何以及谁使用它，次要因素是您的开发团队的规模和经验。
Personally, I'd vouch for a Model-View-Controller-type CMS above anything else (especially if you're the one developing both the CMS and projects based on it), but the complexity of the actual business separation might have no impact on your overall application design.
For instance...
To summarize, a MVC architecture is merely a baseline as to how you separate different concerns when creating new features (writing code) with Business Value - creating new forms, lists, workflows, navigational structures, aggregates, etc. However, the actual architecture of your Application (CMS) depends on how and who will be using it, secondary to the factor of your development team's size and experience.