I consulted with the project setup and would like to discard my ideas from someone for additional opinions.
The main part of this site is very complex and has very individual features, so from what I saw more, is webapp. However, a blog is needed, and a forum is also needed. This is a general overview of this project.
Since the main part of the website is more related to webapp, I think that this project should be divided into separate parts, which are considered by different structures and CMS, so that each component does not limit other components. This is a rather difficult decision to sell, because no one wants to support different structures and CMS, if it really is not suitable for them.
My logic is that the main part of the website is a really complex webapp, trying to fit it into a CMS like Drupal or Joomla, or something that will increase development time and cost. This part makes sense to create more flexible technologies like Zend Framework or Symfony, basically something that is not a CMS.
For the rest of the components, I see no reason to use the framework, since many of them are standard components, such as a blog and forum. Thus, for the rest of the website, my options are: 1) to build everything that is necessary for one CMS that I am familiar with (for example, Drupal), but since I have already taken the path of dividing the site, I thought option 2), why not to split the site even more and choose the best software for each component. For example, Drupal does not make an excellent forum. It is simply not where its strength is.
It also turns out that the people who will participate in the writing of the blogs are basically not the people who participate in the forums, so I think I should not worry about something like training the same staff on 2 separate software providing.
-. , : , ( ) ( ), , , , , - , .
, , , , . , . , - ? , ? , ?