[ 
https://issues.apache.org/jira/browse/CASSANDRA-17699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17699:
--------------------------------------
    Test and Documentation Plan: Build the website locally then stage it to 
make sure that changes + all elements of the page render correctly.
                         Status: Patch Available  (was: Open)

Patch submitted:
||Branch||PR||
|{{trunk}}|[#143|https://github.com/apache/cassandra-website/pull/143]|

> WEBSITE - Broken link to "existing documents" in 
> development/documentation.html
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17699
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17699
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation/Website
>            Reporter: Matthew D. Sacks
>            Assignee: Matthew D. Sacks
>            Priority: Normal
>              Labels: pull-request-available
>
> The “existing documents” link throws a 404 error when clicked on from 
> [https://cassandra.apache.org/_/development/documentation.html.]
> {quote}
> Using a static site generator often requires the use of a markup language 
> instead of visual editors (which some people would call good news). Antora 
> processes [Ascidoc|http://www.asciidoc.org/], the markup language used to 
> generate our documentation. Markup languages allow you to format text using 
> certain syntax elements. Your document structure will also have to follow 
> specific conventions. Feel free to take a look at [existing 
> documents|http://cassandra.apache.org/docs] to get a better idea how we 
> structure our documents.
> {quote}
> Can someone provide the proper destination link?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to