The create content template use-case's highly coupled structure makes it hard to read and change.

Issues with the current structure:

• template types are not clearly named
• create template use case is mixed with edit template use case
• use case data transformations are not clear --> model processes as types
• domain logic is mixed with UI logic
• presentational and container components are not clearly separated, making presentational components hard to reuse, resulting in duplication

Address these issues. Make it better.