[
https://issues.apache.org/jira/browse/TS-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846981#action_12846981
]
Miles Libbey commented on TS-218:
---------------------------------
FWIW, we decided not to use docbook b4 going live (which would have been
similar to Leif's suggestion):
- We didn't have the docbook format of the admin guide, and converting to that
vs html was more expensive.
- the ability to make a pdf doc seemed overkill.
using ssi, I think we get pretty close to what Leif was talking about. For
instance, in docs/v2/admin, there are 3 includes --
- top.html (has the header and search)
- bottom (the footer)
- leftnav (the table of contents on the left side).
We should be able to do something very similar for the other site pages.
> enable templating/ssi etc for website
> -------------------------------------
>
> Key: TS-218
> URL: https://issues.apache.org/jira/browse/TS-218
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Miles Libbey
>
> Moving from TS-216:
> ----------------------------------
> Sure, lets make it nice. What I meant was, use the templating engines etc. as
> they do (and most of Apache sites do). I now it's archaic, but has benefits
> over editing HTML directly (specially for things like dealing with menus and
> navigational components etc.).
> The incubator site is built using Apache Anakia
> (http://velocity.apache.org/anakia/releases/anakia-1.0/) and tools.
> ----------------------------------
> It would certainly be nice to be able to have ssi or some other way of
> templating to deal with navigation, headers, footers, etc. (but, changing all
> the documentation html to xml so that Anakia can be used seems like a massive
> project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
