It sounds to me like computing the relative path seems like the best long term solution. We'd need the doc root (which we should already have), the location of the file relative to the doc root and then the resources root directories (images, javascript, styles), of course we'd also need the output directories, but we should already have those as well.

On Thu, Sep 12, 2013 at 6:57 AM, asotobu [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Dan I think we need a way to handle this situation, for example in my talks about Asciidoctor, and when I teach personally to my mates how documentations should be written, I encourage them to create as many as adoc files as required and more important distribute them across their project as with code; so for example in src/main/resources/file1.adoc would contain the index file with includes to different files like src/main/resources/com/lordofthejars/foo/file2.adoc and so on, with this approach you know where to find exactly the documentation of a part of your project/module (at same place as normal resources of your project). Basically I try to give the same treatment of documentation as anything on a project.

Now because I am embedding CSS there is no problem, but of course as ChrLipp suggested it could be a problem in near future if people finds more useful to not embed CSS.

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Single-CSS-for-multiple-nested-adoc-files-tp552p577.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

--

Jason Porter
http://en.gravatar.com/lightguardjp

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Single-CSS-for-multiple-nested-adoc-files-tp552p578.html

To unsubscribe from Single CSS for multiple, nested adoc files, click here.
NAML