Developing applications that are readable for TREX in a good way
I would like to develop some applications like book management, article management, employee profiles and so on.
The question for me is how to develop this applications in order that TREX can display it in a good way. With this I mean the following:
When I display a list of books / articles I have a view with a list of books and the abstracts like it is in sdn->articles->by date -> last 30.
Normally I would configure TREX to crawl the page and then he would also index the overview page. But I would like that he is just displaying the entry/database's recordset for the according record and not the link to the overview page.
I integrated for testing purposes the jive-forum and there he is doing it in the right way be saving the records in the KMC area and for every thread there is a separate entry....
How are you solving things like this? Is there a good "best practise" for things like that?