Quantcast

Asciidoctor variables not getting processed by Awestruct Asciidoc module?

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?

Sent from Mailbox for iPhone


On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
You could try :page-layout: but awestruct-layout should work. 

Sent from Mailbox for iPhone


On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
Okay, something is certainly wrong here. What does your asciidoc document look like?


On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 




--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
attributes should go at the start of the document, typically below the level 0 header (=)


On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--




--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

Yup, that was it, lack of top-level header… thanks.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com
In reply to this post by LightGuard

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
Is your source publically available?


On Mon, Mar 17, 2014 at 12:51 PM, Victor Danilchenko <[hidden email]> wrote:

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--




--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

Jason,

 

Many thanks for your help outside of the list. Here, I will enumerate the fixes for the errors I made for posterity’s sake. Correct me if I get something wrong, please.

 

·         In site.yml, in the asciidoctor section, I had to add  ‘imagesdir: images@’ go get the setting of the ‘:imagesdir:’ in the document to be honored. This is documented in the section 3.1 of the Asciidoctor syntax reference, ‘3.1. Attribute assignment precedence’.

·         To enable interpolation of Awestruct variables, I had to set ‘:awestruct-interpolate: true’ in the document. For some reason I do not yet understand, setting ‘interpolate: true’ in site.yml, either globally or in the asciidoctor section, doesn’t work.

·         The interpolated Ruby site variables from site.yml are in e.g. #{page.site.name}, not #{site.name}, though http://awestruct.org/getting_started/ suggests otherwise.

·         I had to make sure there’s a space between ‘:attribute:’ and its value, otherwise instead of assigning attribute values, the lines were getting rendered as text.

 

This clears up a lot for me. On the forum, you also suggested git sources for three sites as something to look at:

 

·         https://github.com/asciidoctor/asciidoctor.org

·         https://github.com/graphitefriction/graphitefriction.github.com

·         https://github.com/LightGuard/lightguardjp.info

 

One more question, if I may.

 

Can you point me at some info/examples on how to dynamically generate a TOC not just of the current document, but of the entire documentation tree? E.g. if I have 20 .adoc  files, I would like to automatically generate a ToC, to be included in each document, that would have a link for each one of those separate documents. Can you offer any pointers on where to look for this type of solution?

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Monday, March 17, 2014 3:45 PM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Is your source publically available?

 

On Mon, Mar 17, 2014 at 12:51 PM, Victor Danilchenko <[hidden email]> wrote:

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--



 

--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
All you've said looks correct.

For a whole site, I'm not sure how you'd go about generating a full TOC, for a book that's pretty easy, but for a site, I'm not really sure, maybe Dan has some ideas.


On Tue, Mar 18, 2014 at 8:42 AM, Victor Danilchenko <[hidden email]> wrote:

Jason,

 

Many thanks for your help outside of the list. Here, I will enumerate the fixes for the errors I made for posterity’s sake. Correct me if I get something wrong, please.

 

·         In site.yml, in the asciidoctor section, I had to add  ‘imagesdir: images@’ go get the setting of the ‘:imagesdir:’ in the document to be honored. This is documented in the section 3.1 of the Asciidoctor syntax reference, ‘3.1. Attribute assignment precedence’.

·         To enable interpolation of Awestruct variables, I had to set ‘:awestruct-interpolate: true’ in the document. For some reason I do not yet understand, setting ‘interpolate: true’ in site.yml, either globally or in the asciidoctor section, doesn’t work.

·         The interpolated Ruby site variables from site.yml are in e.g. #{page.site.name}, not #{site.name}, though http://awestruct.org/getting_started/ suggests otherwise.

·         I had to make sure there’s a space between ‘:attribute:’ and its value, otherwise instead of assigning attribute values, the lines were getting rendered as text.

 

This clears up a lot for me. On the forum, you also suggested git sources for three sites as something to look at:

 

·         https://github.com/asciidoctor/asciidoctor.org

·         https://github.com/graphitefriction/graphitefriction.github.com

·         https://github.com/LightGuard/lightguardjp.info

 

One more question, if I may.

 

Can you point me at some info/examples on how to dynamically generate a TOC not just of the current document, but of the entire documentation tree? E.g. if I have 20 .adoc  files, I would like to automatically generate a ToC, to be included in each document, that would have a link for each one of those separate documents. Can you offer any pointers on where to look for this type of solution?

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Monday, March 17, 2014 3:45 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Is your source publically available?

 

On Mon, Mar 17, 2014 at 12:51 PM, Victor Danilchenko <[hidden email]> wrote:

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--



 

--




--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

I could obviously generate it by preprocessing the documents and creating a separate toc.adoc file, but I wonder if that is really the best way to accomplish such a goal.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, March 18, 2014 12:52 PM
To: [hidden email]
Cc: Dan Allen
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

All you've said looks correct.

 

For a whole site, I'm not sure how you'd go about generating a full TOC, for a book that's pretty easy, but for a site, I'm not really sure, maybe Dan has some ideas.

 

On Tue, Mar 18, 2014 at 8:42 AM, Victor Danilchenko <[hidden email]> wrote:

Jason,

 

Many thanks for your help outside of the list. Here, I will enumerate the fixes for the errors I made for posterity’s sake. Correct me if I get something wrong, please.

 

·         In site.yml, in the asciidoctor section, I had to add  ‘imagesdir: images@’ go get the setting of the ‘:imagesdir:’ in the document to be honored. This is documented in the section 3.1 of the Asciidoctor syntax reference, ‘3.1. Attribute assignment precedence’.

·         To enable interpolation of Awestruct variables, I had to set ‘:awestruct-interpolate: true’ in the document. For some reason I do not yet understand, setting ‘interpolate: true’ in site.yml, either globally or in the asciidoctor section, doesn’t work.

·         The interpolated Ruby site variables from site.yml are in e.g. #{page.site.name}, not #{site.name}, though http://awestruct.org/getting_started/ suggests otherwise.

·         I had to make sure there’s a space between ‘:attribute:’ and its value, otherwise instead of assigning attribute values, the lines were getting rendered as text.

 

This clears up a lot for me. On the forum, you also suggested git sources for three sites as something to look at:

 

·         https://github.com/asciidoctor/asciidoctor.org

·         https://github.com/graphitefriction/graphitefriction.github.com

·         https://github.com/LightGuard/lightguardjp.info

 

One more question, if I may.

 

Can you point me at some info/examples on how to dynamically generate a TOC not just of the current document, but of the entire documentation tree? E.g. if I have 20 .adoc  files, I would like to automatically generate a ToC, to be included in each document, that would have a link for each one of those separate documents. Can you offer any pointers on where to look for this type of solution?

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Monday, March 17, 2014 3:45 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Is your source publically available?

 

On Mon, Mar 17, 2014 at 12:51 PM, Victor Danilchenko <[hidden email]> wrote:

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--



 

--



 

--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
You could create a file that includes all the others and generate the toc that way, but then things won't link up the way they should.


On Tue, Mar 18, 2014 at 11:58 AM, Victor Danilchenko <[hidden email]> wrote:

I could obviously generate it by preprocessing the documents and creating a separate toc.adoc file, but I wonder if that is really the best way to accomplish such a goal.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, March 18, 2014 12:52 PM
To: [hidden email]
Cc: Dan Allen


Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

All you've said looks correct.

 

For a whole site, I'm not sure how you'd go about generating a full TOC, for a book that's pretty easy, but for a site, I'm not really sure, maybe Dan has some ideas.

 

On Tue, Mar 18, 2014 at 8:42 AM, Victor Danilchenko <[hidden email]> wrote:

Jason,

 

Many thanks for your help outside of the list. Here, I will enumerate the fixes for the errors I made for posterity’s sake. Correct me if I get something wrong, please.

 

·         In site.yml, in the asciidoctor section, I had to add  ‘imagesdir: images@’ go get the setting of the ‘:imagesdir:’ in the document to be honored. This is documented in the section 3.1 of the Asciidoctor syntax reference, ‘3.1. Attribute assignment precedence’.

·         To enable interpolation of Awestruct variables, I had to set ‘:awestruct-interpolate: true’ in the document. For some reason I do not yet understand, setting ‘interpolate: true’ in site.yml, either globally or in the asciidoctor section, doesn’t work.

·         The interpolated Ruby site variables from site.yml are in e.g. #{page.site.name}, not #{site.name}, though http://awestruct.org/getting_started/ suggests otherwise.

·         I had to make sure there’s a space between ‘:attribute:’ and its value, otherwise instead of assigning attribute values, the lines were getting rendered as text.

 

This clears up a lot for me. On the forum, you also suggested git sources for three sites as something to look at:

 

·         https://github.com/asciidoctor/asciidoctor.org

·         https://github.com/graphitefriction/graphitefriction.github.com

·         https://github.com/LightGuard/lightguardjp.info

 

One more question, if I may.

 

Can you point me at some info/examples on how to dynamically generate a TOC not just of the current document, but of the entire documentation tree? E.g. if I have 20 .adoc  files, I would like to automatically generate a ToC, to be included in each document, that would have a link for each one of those separate documents. Can you offer any pointers on where to look for this type of solution?

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Monday, March 17, 2014 3:45 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Is your source publically available?

 

On Mon, Mar 17, 2014 at 12:51 PM, Victor Danilchenko <[hidden email]> wrote:

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--



 

--



 

--




--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

vdanilchenko@vistaprint.com

Yeah, definitely not what I am looking for – what I need is something that would have both the list of documents, and TOCs for each document. Awestruct.org site has something similar, the ‘Documentation’ tab on top and a ToC for each document on the left, except that tab dropdowns seem to be statically generated, and I need a list of documents I can update on the fly.

 

At the moment I am going with simply writing a stand-alone script which will parse a list of documents, extract their top headers, and combine them into a toc.adoc file, but this seems like a really kludge, crude way of doing it. Still, this is all I have thought of so far…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, March 18, 2014 4:05 PM
To: [hidden email]
Cc: Dan Allen
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could create a file that includes all the others and generate the toc that way, but then things won't link up the way they should.

 

On Tue, Mar 18, 2014 at 11:58 AM, Victor Danilchenko <[hidden email]> wrote:

I could obviously generate it by preprocessing the documents and creating a separate toc.adoc file, but I wonder if that is really the best way to accomplish such a goal.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, March 18, 2014 12:52 PM
To: [hidden email]
Cc: Dan Allen


Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

All you've said looks correct.

 

For a whole site, I'm not sure how you'd go about generating a full TOC, for a book that's pretty easy, but for a site, I'm not really sure, maybe Dan has some ideas.

 

On Tue, Mar 18, 2014 at 8:42 AM, Victor Danilchenko <[hidden email]> wrote:

Jason,

 

Many thanks for your help outside of the list. Here, I will enumerate the fixes for the errors I made for posterity’s sake. Correct me if I get something wrong, please.

 

·         In site.yml, in the asciidoctor section, I had to add  ‘imagesdir: images@’ go get the setting of the ‘:imagesdir:’ in the document to be honored. This is documented in the section 3.1 of the Asciidoctor syntax reference, ‘3.1. Attribute assignment precedence’.

·         To enable interpolation of Awestruct variables, I had to set ‘:awestruct-interpolate: true’ in the document. For some reason I do not yet understand, setting ‘interpolate: true’ in site.yml, either globally or in the asciidoctor section, doesn’t work.

·         The interpolated Ruby site variables from site.yml are in e.g. #{page.site.name}, not #{site.name}, though http://awestruct.org/getting_started/ suggests otherwise.

·         I had to make sure there’s a space between ‘:attribute:’ and its value, otherwise instead of assigning attribute values, the lines were getting rendered as text.

 

This clears up a lot for me. On the forum, you also suggested git sources for three sites as something to look at:

 

·         https://github.com/asciidoctor/asciidoctor.org

·         https://github.com/graphitefriction/graphitefriction.github.com

·         https://github.com/LightGuard/lightguardjp.info

 

One more question, if I may.

 

Can you point me at some info/examples on how to dynamically generate a TOC not just of the current document, but of the entire documentation tree? E.g. if I have 20 .adoc  files, I would like to automatically generate a ToC, to be included in each document, that would have a link for each one of those separate documents. Can you offer any pointers on where to look for this type of solution?

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Monday, March 17, 2014 3:45 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Is your source publically available?

 

On Mon, Mar 17, 2014 at 12:51 PM, Victor Danilchenko <[hidden email]> wrote:

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--



 

--



 

--



 

--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Asciidoctor variables not getting processed by Awestruct Asciidoc module?

LightGuard
Administrator
I'll have to think about that one for a bit.


On Thu, Mar 20, 2014 at 7:54 AM, Victor Danilchenko <[hidden email]> wrote:

Yeah, definitely not what I am looking for – what I need is something that would have both the list of documents, and TOCs for each document. Awestruct.org site has something similar, the ‘Documentation’ tab on top and a ToC for each document on the left, except that tab dropdowns seem to be statically generated, and I need a list of documents I can update on the fly.

 

At the moment I am going with simply writing a stand-alone script which will parse a list of documents, extract their top headers, and combine them into a toc.adoc file, but this seems like a really kludge, crude way of doing it. Still, this is all I have thought of so far…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, March 18, 2014 4:05 PM


To: [hidden email]
Cc: Dan Allen
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could create a file that includes all the others and generate the toc that way, but then things won't link up the way they should.

 

On Tue, Mar 18, 2014 at 11:58 AM, Victor Danilchenko <[hidden email]> wrote:

I could obviously generate it by preprocessing the documents and creating a separate toc.adoc file, but I wonder if that is really the best way to accomplish such a goal.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, March 18, 2014 12:52 PM
To: [hidden email]
Cc: Dan Allen


Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

All you've said looks correct.

 

For a whole site, I'm not sure how you'd go about generating a full TOC, for a book that's pretty easy, but for a site, I'm not really sure, maybe Dan has some ideas.

 

On Tue, Mar 18, 2014 at 8:42 AM, Victor Danilchenko <[hidden email]> wrote:

Jason,

 

Many thanks for your help outside of the list. Here, I will enumerate the fixes for the errors I made for posterity’s sake. Correct me if I get something wrong, please.

 

·         In site.yml, in the asciidoctor section, I had to add  ‘imagesdir: images@’ go get the setting of the ‘:imagesdir:’ in the document to be honored. This is documented in the section 3.1 of the Asciidoctor syntax reference, ‘3.1. Attribute assignment precedence’.

·         To enable interpolation of Awestruct variables, I had to set ‘:awestruct-interpolate: true’ in the document. For some reason I do not yet understand, setting ‘interpolate: true’ in site.yml, either globally or in the asciidoctor section, doesn’t work.

·         The interpolated Ruby site variables from site.yml are in e.g. #{page.site.name}, not #{site.name}, though http://awestruct.org/getting_started/ suggests otherwise.

·         I had to make sure there’s a space between ‘:attribute:’ and its value, otherwise instead of assigning attribute values, the lines were getting rendered as text.

 

This clears up a lot for me. On the forum, you also suggested git sources for three sites as something to look at:

 

·         https://github.com/asciidoctor/asciidoctor.org

·         https://github.com/graphitefriction/graphitefriction.github.com

·         https://github.com/LightGuard/lightguardjp.info

 

One more question, if I may.

 

Can you point me at some info/examples on how to dynamically generate a TOC not just of the current document, but of the entire documentation tree? E.g. if I have 20 .adoc  files, I would like to automatically generate a ToC, to be included in each document, that would have a link for each one of those separate documents. Can you offer any pointers on where to look for this type of solution?

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Monday, March 17, 2014 3:45 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Is your source publically available?

 

On Mon, Mar 17, 2014 at 12:51 PM, Victor Danilchenko <[hidden email]> wrote:

Well, I have played around some more, and it’s looking like the problem is with setting standard attributes. So for instance I have:

 

= Top header

:imagesdir: /asciidoctor/imagess

:awestruct-layout: base

:testvar: test

 

== Sample header

 

Imagesdir: {imagesdir} - {testvar}

 

So ‘testvar’ gets set, but ‘imagesdir’ keeps the default value, and my setting is ignored.

 

Any idea what may be going on here?

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:25 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

attributes should go at the start of the document, typically below the level 0 header (=)

 

On Fri, Mar 14, 2014 at 11:19 AM, Victor Danilchenko <[hidden email]> wrote:

Here’s my .adoc file:

 

---

layout: base

---

== Sample header

//:stylesdir: .

//:stylesheet: asciidoctor/styles.css

//:toc: right

//:toc-title: Sections

:imagesdir: myImages

//:awestruct-layout: base

 

== Another header

 

There's an image here

 

[[img-overview]]

.Overview of deployments

image::Overview.png[Overview, 500, 327]

 

if I remove the front matter and leave in only the :awestruct-layout:, the compiler renders my doc with some default layout. The only way I get my own layout is via front matter. Also the :imagesdir: directive has absolutely no effect on the URL of the image included at the bottom.

 

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 1:08 PM


To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

Okay, something is certainly wrong here. What does your asciidoc document look like?

 

On Fri, Mar 14, 2014 at 10:47 AM, Victor Danilchenko <[hidden email]> wrote:

That didn’t work either. Other asciidoctor attributes also don’t work apparently – at least I tried to set the :imagesdir: attribute, and it also got summarily ignored.

 

The attributes don’t get rendered, but apparently also don’t get parsed&stored…

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Friday, March 14, 2014 11:54 AM
To: [hidden email]
Subject: RE: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

You could try :page-layout: but awestruct-layout should work. 


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:41 AM, Victor Danilchenko <[hidden email]> wrote:

Yes, I installed the latest RC version of Awestruct, as per your advice, and my ‘base’ layout works fine from front matter – just not from asciidoctor attribute setting.

 

 

From: Jason Porter [[hidden email]]
Sent: Friday, March 14, 2014 11:31 AM
To: [hidden email]
Subject: Re: [awestruct] Asciidoctor variables not getting processed by Awestruct Asciidoc module?

 

I'm assuming you have a layout named base, so that's not the problem. You're using a recent version of awestruct?


Sent from Mailbox for iPhone

 

On Fri, Mar 14, 2014 at 9:24 AM, Victor Danilchenko <[hidden email]> wrote:

Hi,

 

So, having finally gotten the basic Awestruct environment to work, I am trying to use it to compile some sample Asciidoc content, and it’s compiling, except that apparently the Asciidoctor variables aren’t being processed. So for instance I should be able to do something like this to specify the layout, as per https://github.com/graphitefriction/oscon-2013-docs-workshop/blob/master/activate-asciidoc-content.adoc :

 

:awestruct-layout: base

 

But that does absolutely nothing – I currently can only specify layout via front matter. Any suggestions on what’s going wrong – and how I can/could figure it out on my own?

 

Thanks in advance!

 

 

 



 

--



 

--



 

--



 

--



 

--




--
Loading...