Naming things is one of the hardest things in computer science. This is because it involves collaborating with other people and detailed semantics.
When you are building an api in tandem with developing an application, changes to the schema need to be implemented in both places. This can mean that the changes need to be coordinated across teams or in different languages. For projects in production, deploying these together can become quite sensitive.
Any mistakes in implementation or changes in decisions cause a lot of cognitive load to understand the change and how to account for it.
Before you begin implementing, it's important to document and share your api schema or content model. Your role as an architect is to push for consistency and completeness, and seek the input you need from teammates and stakeholders to reduce changes later.
Different teams have different ways of talking about their work. Some say components where others say patterns. These words are discussed with clients and written into code. Having consistency in their use allows you to have a more unified system that is easy to understand and extend.
It is important to define schema up front, because once a system is live, changing it requires complex data migrations between formats.