Sometimes it would be useful to list product documentation produced with other tools on a Publican-generated splash page for a product.
* Entries should support the same fields as a Publican-generated book (product/version/title/subtitle/abstract) but should also support the sort_order parameter.
* Docs linked in such a way should also form part of the DUMP.xml, as part of the suite of documentation that Publican knows about for a particular product.
(In reply to Ruediger Landmann from comment #0)
> * Docs linked in such a way should also form part of the DUMP.xml, as part
> of the suite of documentation that Publican knows about for a particular
What is the rationale behind this requirement? External systems consuming publican content should communicate with the external system directly. This makes it easy to remove publican from the mix should that be required.
Please provide a few examples for testing.
Jeff, we're thinking of the drupal articles. E.g. https://access.redhat.com/articles/1127153
I need multiple links with all the information you want on the page.
Preferably in this format:
<member role="$sort_order" title="$title" href="$uri" version="$version">$sub_title</member>
And I'll need to know which product each link is for, but that isn't part of the XML as each product will have a separate list.
If you don't have real ones in prod then give me fake ones that link to personal pages or something.
f84ff5c..2eefbb4 devel -> devel
a48506e..623425b devel -> devel
<member role="10" title="The Ways And Means Of Pants" href="https://pants.redhat.com" version="6">Pants in all thier glory!</member>
one member per link!
to be clear:
role = sort_order
title = title
href = url
version = product version
member content = sub title
There is no validation done on anything nor are the URLs vetted or limited to any domains.
<simplelist> tags to be placed in en-US/External_Links.xml file.
Both links and real docs are showing up in their proper place on the splash page. Verified.
A fix for this shipped in Publican 4.2.0.