Currently, everything is called CMS - tools for supporting websites, advanced portals, wikis, etc. However, CMS requirements vary widely for intranet and public websites.
An intranet usually has a high level of interaction, a lot of user-generated content, different types of content, etc. More users should be able to log into the system (basically, everything, not just content editors) with different levels of authorization and different roles in general. Collaboration as a whole is much more important than with an average "public" site based on CMS.
In addition, you usually need different types of plugins. Google analytics and SEO are much less important, you are more interested in some active user plugin, recent publications, integration with other internal tools (for example, project management) and, possibly, the publication of other data sources (databases, telephone directories, file systems with internal documents ), etc.
In my personal experience, Plone is a good choice. It provides most of the above out of the box or through existing extensions and has excellent integration capabilities with external systems. Cyn.in also provides a somewhat comprehensive plone-based solution.
If Plone is too much for you, you might consider some wiki-like system like TWiki or MediaWiki
source share