Login  Register

Documentation - Inject Footer and Header

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options Options
Embed post
Permalink
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Documentation - Inject Footer and Header

SigmaSquared
5 posts
Is there any documentation, or is it even possible, to insert another .adoc (or another file type) as a Footer or Header?


Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: Documentation - Inject Footer and Header

LightGuardjp
354 posts

On Mon, Oct 5, 2015 at 9:50 AM, SigmaSquared [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Is there any documentation, or is it even possible, to insert another .adoc (or another file type) as a Footer or Header?





If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Documentation-Inject-Footer-and-Header-tp3813.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: Documentation - Inject Footer and Header

mojavelinux
Administrator
2681 posts

And it's scheduled for 1.5.3 to allow docinfo files to be AsciiDoc. Though it's possible to accomplish with 1.5.2 using the DocinfoProcessor extension point.

Cheers,

-Dan

Le 5 oct. 2015 10:54 AM, "LightGuardjp [via Asciidoctor :: Discussion]" <[hidden email]> a écrit :

On Mon, Oct 5, 2015 at 9:50 AM, SigmaSquared [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Is there any documentation, or is it even possible, to insert another .adoc (or another file type) as a Footer or Header?





If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Documentation-Inject-Footer-and-Header-tp3813.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Documentation-Inject-Footer-and-Header-tp3813p3814.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML
Ted
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: Documentation - Inject Footer and Header

Ted
126 posts
You can also "Include" files, if that's what you meant: http://asciidoctor.org/docs/user-manual/#include-directive
- Ted @TedAtCIS
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: Documentation - Inject Footer and Header

SigmaSquared
5 posts
In reply to this post by mojavelinux
It appears that this footer & header 'injection' using docinfo, at this point, only works with HTML and docbook as the output file types.  Is this also true for DocinfoProcessor?

Unlike the link provided by LightGuardjp,  DocinfoProcessor's documentation didn't say what the output file types were. However, ManpageMacro that's used in the example for DocinfoProcessor, references HTML in it's example.  I can only guess that the answer is that the output files for both ways, is only for html and docbook, but I want to be sure.

Excuse me if i'm not asking the right questions, as i'm just now learning about Asciidoctor.

Many thanks.
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: Documentation - Inject Footer and Header

mojavelinux
Administrator
2681 posts

On Mon, Oct 5, 2015 at 9:01 PM, SigmaSquared [via Asciidoctor :: Discussion] <[hidden email]> wrote:
It appears that this footer & header 'injection' using docinfo, at this point, only works with HTML and docbook as the output file types.  Is this also true for <a href="http:// https://github.com/asciidoctor/asciidoctorj#docinfoprocessor">DocinfoProcessor?

The DocinfoProcessor can do whatever it wants in the process method, but ultimately needs to return an HTML or DocBook string to inject (whatever is appropriate for the current backend). To get that HTML or DocBook, it can run Asciidoctor on other source content.

Here's the link to the issue for allowing AsciiDoc content in docinfo files, btw:


There's also an example of a DocinfoProcessor linked in that issue.

Cheers,

-Dan


--
Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen