- From: Hayato Ito <notifications@github.com>
- Date: Thu, 19 May 2016 02:24:55 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
Received on Thursday, 19 May 2016 09:25:24 UTC
My general advice here: - If components are well designed, crawler do not need a flattened tree to get text contents. - Good search-engine friendly components would enable component users to specify text contents in a place of component's children, as *crawlable* text contents*, rather than embedding hard-coded text contents in their shadow trees. e.g. ``` <good-components>hello world</good-components> ``` ``` <bad-components></bad-components> // "hello world" is hard-coded in its shadow tree. ``` Humans might see "hello world" in both cases, but the former is search-engine friendly, I think. Thus, it's up-to component developers. If every components are well-designed, every important text information can be put in top HTML. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/500#issuecomment-220272515
Received on Thursday, 19 May 2016 09:25:24 UTC