We will be introducing a post type to represent a campaign that will have all campaign settings (theme with campaign's visual identity, navigation options, tracking settings) and can contain 1 or more pages. Those pages are essentially what we now call "campaign".

In order to resolve this naming conflict we will rename the post type to "campaign page" everywhere in both the UI and the code.

To be refined/decided:

• If we change the identifier of the post type then we have to migrate existing content. This can be time consuming and error prone so we may want to delay renaming that identifier. However it looks like we really don't have that much existing content, so maybe it's worth it to do the migration after all and avoid confusion about the old name.

Tasks

• Replace the content type name to campaign page
• For the implementation check if it needs to be migrated manually