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

Bill Farner commented on AURORA-1314:
-------------------------------------

Thanks for pitching in!

Please have a look at our contributors guide: 
https://github.com/apache/aurora/blob/master/CONTRIBUTING.md

Our main git repo is the source of truth for markdown documentation.

Also, i'm actually not certain we can fix this issue as approached here, as the 
anchors are currently set up to work with github; and their renderer likes to 
prepend 'user-content-' to anchors.

An alternative that i would like to explore is using github's markdown renderer 
directly, via their API to provide greater uniformity: 
https://developer.github.com/v3/markdown/

However, i think there is a worthwhile discussion our dev team should have 
about whether it makes sense to mirror our documentation onto apache.org.

Given that this is potentially a pretty long thread to pull, you might consider 
opening the discussion in our next IRC meeting, but avoid getting bogged down 
with the impending overhaul

> wrong ids name: user-content
> ----------------------------
>
>                 Key: AURORA-1314
>                 URL: https://issues.apache.org/jira/browse/AURORA-1314
>             Project: Aurora
>          Issue Type: Bug
>            Reporter: Willy Aguirre
>            Assignee: Willy Aguirre
>              Labels: web-site
>
> wrong ids name: user-content-
> http://aurora.apache.org/documentation/latest/vagrant/
> http://aurora.apache.org/documentation/latest/user-guide/#user-content-interacting-with-jobs
> http://aurora.apache.org/documentation/latest/configuration-tutorial/#user-content-aurora-configuration-tutorial
> http://aurora.apache.org/documentation/latest/deploying-aurora-scheduler/#solution-2
>  is #solution
> http://aurora.apache.org/documentation/latest/storage/#atomicity-consistency-and-isolation
> id="atomicity,-consistency-and-isolation"



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

Reply via email to