By chance I had a conversation yesterday in person with pbokoc, pkovar and rkratky. We wound up discussing xrefs (because we are that kind of cool!). As you may know, xrefs allow you to link to a piece of content without having to know where it actually lives. In DocBook you link to the id of the section/etc. AsciiBinder does not support xrefs today. AsciiDoc has syntax for them, but the processing that AsciiBinder does to build the site precludes us from using it. I believe I can get us something like this working though. Is there an interest? = Xrefs in AsciiBinder A plugin will be written (I have a rough Proof Of Concept done) that overloads the AsciiDoc xref syntax. We would now be able to do the following: xref:title_with_underscores_case_insensitive[optional text to use for the link text - otherwise the title is used] This would link to the page that has that title. But what about collisions? If two pages have the same title, you will need to be more specific. Using the Dir entries from the _topic_map.yml you would specify: xref:dir/title_with_underscores_case_insensitive[optional text to use for the link text - otherwise the title is used] This may or may not work fully if you have a / (slash) in your title. If we want xrefs back, I am willing to sacrifice this :) are you? = Cross-repo linking As a bonus, we can probably get something like this to work: xref:content-set@dir/title_with_underscores[optional link text] The content-set level linking would only be available to books/content that is jointly published. The content-set is the same as the name of the repository. This means that you could link to the install-guide from the release-notes but you can't link to the council docs. The install-guide and release-notes are published in the same area of the site. Council docs is separate. What do you think? regards, bex _______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx
