Best Practice Advice: Use page properties Title field for internal usage | Community
Skip to main content
EggBoy
EggBoy
Level 3
May 30, 2018
Solved

Best Practice Advice: Use page properties Title field for internal usage

  • May 30, 2018
  • 2 replies
  • 2442 views

Hi All,

We have a requirement to use the Title field for pages in AEM as internal only, and use Page Title to populate the various places the Title field would be used, like in the <title> tag.

The need is so we can us Title to indicate, internally, more info about the page for reporting purposes. A good example is a page that might appear on our China site, that would normally have a title of this, which is also what winds up in reports etc.

Customer facing:

生物分析实验室定制化解决方案

Internal facing (for reporting, navigation in AEM author, etc. that is consumed globally)

生物分析实验室定制化解决方案 bio lab solutions page

Will this cause issues long term? It does seem that the OoB Title is used for <title> and other context....it is advisable to map Page Title for this?

Thank you all!

Eugene

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by joerghoh

    Hi,

    good question.

    I don't think that you get a technical issue with it. It's more like that people might get confused when you have multiple ways to reference a specific page. When you used classic UI both the name and the title has been displayed in parallel, and if that differed it often caused questions.

    regards,

    Jörg

    2 replies

    joerghoh
    Adobe Employee
    joerghohAdobe EmployeeAccepted solution
    Adobe Employee
    May 30, 2018

    Hi,

    good question.

    I don't think that you get a technical issue with it. It's more like that people might get confused when you have multiple ways to reference a specific page. When you used classic UI both the name and the title has been displayed in parallel, and if that differed it often caused questions.

    regards,

    Jörg

      EggBoy
      EggBoyAuthor
      Level 3
      June 5, 2018

      Thanks for confirming this is not a tech issue or bad practice. This will make reporting much easier, and the interface a bit more intuitive.

      Cheers,

      Eugene

      Terms & ConditionsAccessibility statement

      Loading footer...