TYPO3 Core

Suppose i want to develop an extension and i would like to be sure the content generated in front-end by this extension will be correctly indexed by indexed_search.

In the documentation i found this page 27 :
"On the image below we are looking at another scenario. In this case the cHashParams is obviously used by the plugin “tt_board”. The plugin has been constructed so intelligently that it links to the messages in the message board without disabling the normal page-cache but rather sending the tt_board_uid parameter along with a so called “cHash”. If this is combined correctly the caching engine allows the page to be cached. Not only does this mean a quicker display of pages in the message board - it also means we can index the page!
"
Or
"The indexer is constructed to work with TYPO3's page structure. Opposite to a crawler which simply indexes all the pages it can find, the TYPO3 indexer MUST take the following into account:
Only cached pages can be indexed.
Pages with dynamic content - such as search pages etc - should supply their own search engine for lookup in specific tables. Another option is to selectively allow certain of those “dynamic” pages to be cached anyways (see the cHashParams concept used by some plugins)
Pages in more than one language must be indexed separately as “different pages”.
Pages with messageboards may have multiple indexed versions based on what is displayed on the page: The overview or a single messageboard item? This is determined by the cHashParams value.
Pages with access restricted to must be observed!
Because pages can contain different content whether a user is logged in or not and even based on which groups he is a member of, a single page (identified by the combination of id/type/language/cHashParams) may even be available in more than one indexed version based on the user-groups. But while the same page may have different content based on the user-groups (and so must be indexed once for each) such pages may just as well present the SAME content regardless of usergroups! This is the very most tricky thing.

"
But what about content into pages ???

Could we have a section in documentation to clarify the points to follow to have the content generated by the extension fully indexed.

Actually, couple of extensions does not allow full indexing of content and it's no good news !

Thanks for help

(issue imported from #M12213)