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

Tyler Hobbs commented on CASSANDRA-12533:
-----------------------------------------

bq. When we have updates to the doc to do, we could push a special '-doc' 
branch and use that for any further change. Say, today, 3.7 being the last 
release, we'd create a cassandra-3.7-doc from the cassandra-3.7 tag and push 
doc changes

That sounds good to me.  I agree that this shouldn't be necessary very often 
once the docs are more complete.

bq. Sure. I suppose you saw the README file in the website sources wich has 
some initial notes? I'll try to add a few more details on what does what, but 
if you have specific point you'd like me to address/clarify, that'll help too.

I did see the README that was there.  The new info you've just committed is a 
_great_ improvement.  That's exactly what I was hoping for.  Thanks for putting 
that together.  +1 on closing this.

> Images not handled correctly on website
> ---------------------------------------
>
>                 Key: CASSANDRA-12533
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12533
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Documentation and Website
>            Reporter: Tyler Hobbs
>            Assignee: Sylvain Lebresne
>
> In the new [IDE|http://cassandra.apache.org/doc/latest/development/ide.html] 
> section of the website, the images are not working.  In {{site/public}} in 
> SVN, the new images aren't anywhere to be found, so either the build process 
> isn't transferring them correctly, or they're being used incorrectly in the 
> original Sphinx source.
> On a related note, the styling for the "Hint" section on that page is 
> missing. That might be intentional, I'm not sure.
> More generally, I'm curious as to why we're using both Jekyll and Sphinx and 
> not just Sphinx alone?  It's sort of hard to tell how to fix this issue with 
> both tools in use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to