[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786228#comment-13786228
 ] 

Travis Graham commented on CLOUDSTACK-4799:
-------------------------------------------

I linkend to local pages in the same guide and used ulink urls for pages that 
were in other guides. If I'm able to use the linkend to still access pages from 
completely different guides I can start doing that.

I was thinking of a way to make doc updating for new version releases easier 
and used the same interpolation for $PRODUCT that spits out CloudStack with all 
the things that get updated on a new doc release. That would prevent things 
like needing to updated the version numbers whenever a new version bump happens 
for things like the repo info and whatever else gets updated on new releases.

That of course will be dependent on whether old docs get rebuilt or not, but if 
they are, I'm guessing that would happen in their own branch that isn't master. 
Master would refer to the most current live version and any other feature 
branch would have their own settings that are particular to the version of CS 
that's current for the docs.

I'm not sure how that's setup in Publican, but I would think making that aspect 
of the docs more DRY would be a nice time saver for rolling out new versions of 
the docs. If that's something that's do able I'd be happy to get that rolled 
into one of the patches I'm rolling out.

I also need to get Publican setup locally so I can "test" the changes before 
sending out patches. I see Daan asked about getting that setup, so I'll work 
with the link that was provided and see if there's any issues I come across 
(there was mention of having to tweak the perl scripts).

> Update Deployment Architecture Overview section
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-4799
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc
>    Affects Versions: 4.2.0
>            Reporter: Travis Graham
>              Labels: documentaion
>             Fix For: 4.2.1
>
>         Attachments: deployment-architecture-overview.patch
>
>
> Adds in links to other docs it only loosely references by name and adds the 
> Primary Storage info about being zone wide for 4.2.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to