Geek asks and answers

Naming convention for Page Proxy?

Tridion naming conventions are interesting because authors see names for:

  • Scheme
  • Patterns
  • Categories and Keywords

I understand that we can use the Component fields to store the content associated with the page <meta name="keywords">, descriptionand <meta name="robots">. This allows you to translate these fields (compared to page metadata), as well as be managed by a separate group of developers.

I could name this type of Component SEO Infoor similar.

But we can also store information other than SEO, such as the title of the visible page ( <h1>This Heading</h1>), navigation information and other parameters / content related to the page (for example, rejection of the page).

Do you have a proprietary naming convention or approach to this page proxy component?

  • Will it be Page Metaconfusing?
  • Is it Pagetoo simple?
  • Is it SEOwrong if it includes information other than SEO?
+3
source share
1 answer

I think naming conventions are always hard to find due to personal / subjective nature.

So, for your question, I think that there is no one correct way to call it, but perhaps something that you and the client can agree on as the best descriptive name for this situation.

, Page Info, - / . , Page Meta, , , ( ).

, Page Proxy ... Page Data...

: Page SEO , SEO. , SEO, metadata ( , ..), , SEO ( , ).

+3

More articles:


All Articles