2 don't use tcm uris for these identifiers
source | link

Sounds functionally similar to a requirement for unique identifiers for analytics. I previously wrote a post that summarizes some of the points in the other answers: http://www.createandbreak.net/2013/01/sdl-tridion-and-web-analytics-aka-how.html (with drawings :-) )

To get unique identifiers for component presentations within a given page, you will need:

  • Component
  • Component Template
  • Position on the page

For CSS, assuming component and template names are unique, this could be a combination of component and template names. Otherwise use Tridion Content Manager URIs (e.g. tcm:5-123) or the "unique" part after the first dash.Otherwise use Tridion Content Manager URIs (e.g. tcm:5-123) or the "unique" part after the first dash.

For elements that are only added to the page once (and maybe use the ID attribute), you can also consider identifying the "region," container component (if used), or even schema. It depends on the content model.

Note that dynamic component presentations make it more challenging--whatever adds or calls DCPs must add the position requirement.

Edit: I'm taking back the suggestion for URIs since these identifiers are easier to use if consistent across Publications and especially between Dev, Test, Acceptance, and Production (DTAP) environments.

Sounds functionally similar to a requirement for unique identifiers for analytics. I previously wrote a post that summarizes some of the points in the other answers: http://www.createandbreak.net/2013/01/sdl-tridion-and-web-analytics-aka-how.html (with drawings :-) )

To get unique identifiers for component presentations within a given page, you will need:

  • Component
  • Component Template
  • Position on the page

For CSS, assuming component and template names are unique, this could be a combination of component and template names. Otherwise use Tridion Content Manager URIs (e.g. tcm:5-123) or the "unique" part after the first dash.

For elements that are only added to the page once (and maybe use the ID attribute), you can also consider identifying the "region," container component (if used), or even schema. It depends on the content model.

Note that dynamic component presentations make it more challenging--whatever adds or calls DCPs must add the position requirement.

Sounds functionally similar to a requirement for unique identifiers for analytics. I previously wrote a post that summarizes some of the points in the other answers: http://www.createandbreak.net/2013/01/sdl-tridion-and-web-analytics-aka-how.html (with drawings :-) )

To get unique identifiers for component presentations within a given page, you will need:

  • Component
  • Component Template
  • Position on the page

For CSS, assuming component and template names are unique, this could be a combination of component and template names. Otherwise use Tridion Content Manager URIs (e.g. tcm:5-123) or the "unique" part after the first dash.

For elements that are only added to the page once (and maybe use the ID attribute), you can also consider identifying the "region," container component (if used), or even schema. It depends on the content model.

Note that dynamic component presentations make it more challenging--whatever adds or calls DCPs must add the position requirement.

Edit: I'm taking back the suggestion for URIs since these identifiers are easier to use if consistent across Publications and especially between Dev, Test, Acceptance, and Production (DTAP) environments.

1
source | link

Sounds functionally similar to a requirement for unique identifiers for analytics. I previously wrote a post that summarizes some of the points in the other answers: http://www.createandbreak.net/2013/01/sdl-tridion-and-web-analytics-aka-how.html (with drawings :-) )

To get unique identifiers for component presentations within a given page, you will need:

  • Component
  • Component Template
  • Position on the page

For CSS, assuming component and template names are unique, this could be a combination of component and template names. Otherwise use Tridion Content Manager URIs (e.g. tcm:5-123) or the "unique" part after the first dash.

For elements that are only added to the page once (and maybe use the ID attribute), you can also consider identifying the "region," container component (if used), or even schema. It depends on the content model.

Note that dynamic component presentations make it more challenging--whatever adds or calls DCPs must add the position requirement.