It’s inside this proposal: Handling Fully Migrated Documentation Pages and Updating Backlinks. There are 2 options listed there:
-
option 1- use redirect object to parent page of the topc, which is faster for us but less nice for the user since they would need to search for the exact piece of info they needed among the whole doc tree. But, we could say that in the new doc organization it’s easy to search and find what you are looking for and assume it’s not that much work for the readers.
-
option 2- adding a new xobject for each new doc page with reference of the original page it comes from. But I just realized that this would still not solve the use case where the user has a bookmark to a heading of an old page. The new button with the link that would display all the new pages coming from the old page will still make the user search among all those pages. Actually, if we do the same display as in the Extension pages, e.g.: https://www.xwiki.org/xwiki/bin/view/DocApp/Code/ExtensionLD?id=org.xwiki.platform:xwiki-platform-like-ui&name=“Like”, it might be even harder than option 1, where we’d simply redirectly to the parent page and let users use the searchbox. (It’s one extra click to land on a doc page where there are 2 ways of searching).
WYT?
I can continue the discussion in that thread and make the poll there. Thanks!