Feature: #107628 - Improved backend module naming and structure

Description

TYPO3's backend module structure has been modernized with clearer, more intuitive naming conventions that better align with industry standards used by enterprise content management systems.

Module names should immediately convey their purpose to editors and administrators. This series of renamings improves clarity, discoverability, and reduces the cognitive load for both new and experienced users.

Clear and consistent naming is fundamental to good user experience. When comparing TYPO3 with other enterprise CMS platforms, it became evident that some of TYPO3's module names were either too technical, ambiguous, or didn't clearly communicate their purpose to users.

To summarize, the goals of this restructuring are:

Improved clarity: Module names immediately convey their purpose
Industry alignment: Adopt naming conventions familiar to users of other enterprise CMS platforms
Better discoverability: Help new users find functionality without extensive training
Reduced cognitive load: Minimize confusion when navigating the backend

Module Renamings

The following modules have been renamed:

Web => Content

The top-level Web module has been renamed to Content.

Rationale: TYPO3 is a content management system. The primary workspace where editors create and manage content should be clearly labeled as such. The term "Web" was ambiguous and didn't communicate the module's purpose - nobody outside the TYPO3 ecosystem understood what "Web" meant in this context.

Migration: Update module parent references from 'web' to 'content':

return [
    'my_module' => [
        'parent' => 'content',  // Previously: 'web'
    ],
];

File => Media

The top-level File module has been renamed to Media.

Rationale: The term "Media" clearly indicates the module's purpose of managing digital media files (images, videos, documents, audio files, etc.) within the CMS. The term "File" was too generic and technical, while "Media" is widely understood and commonly used in content management systems to refer to digital content assets.

Migration: Update module parent references from 'file' to 'media':

return [
    'my_module' => [
        'parent' => 'media',  // Previously: 'file'
    ],
];

Impact

All renamed module identifiers maintain their previous names as aliases, ensuring full backward compatibility. Existing code, configurations, and third-party extensions continue to work without modification.

Developers are encouraged to update their code to use the new identifiers for consistency and clarity.

The modernized naming improves the overall user experience by making the backend more intuitive and easier to navigate, particularly for users familiar with other enterprise CMS platforms.