[
https://issues.apache.org/jira/browse/CALCITE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122861#comment-16122861
]
Francis Chuang edited comment on CALCITE-1937 at 8/11/17 5:17 AM:
------------------------------------------------------------------
-[~julianhyde]Does it make sense if I just copy the file tree from
calcite-avatica/site into calcite-avatica-go/site and replace the files inside
_docs with my own markdown documents?-
Ok, that makes sense too. I am assuming I'd just need to write the markdown
files and chuck them in my `site` folder then.
was (Author: francischuang):
[~julianhyde]Does it make sense if I just copy the file tree from
calcite-avatica/site into calcite-avatica-go/site and replace the files inside
_docs with my own markdown documents?
> Web site for Avatica Go
> -----------------------
>
> Key: CALCITE-1937
> URL: https://issues.apache.org/jira/browse/CALCITE-1937
> Project: Calcite
> Issue Type: Bug
> Components: avatica-go
> Reporter: Julian Hyde
> Assignee: Francis Chuang
>
> Create a web site for calcite-avatica-go.
> How about this:
> * At run time, the pages should appear under http://calcite.apache.org/avatica
> * The pages should be source-controlled under calcite-avatica-go/site, in
> markdown format (same as calcite and avatica), and generated into svn using
> similar trickery to calcite and avatica.
> * Reduce the amount of content in
> https://github.com/apache/calcite-avatica-go/blob/master/README.md. The
> "documentation" stuff should move to under http://calcite.apache.org/avatica.
> So the page will be mainly a re-direct to the Apache home page. Similar to
> https://github.com/apache/calcite-avatica/blob/master/README.md, in fact.
> * Add a go_history.md file.
> Should avatica-go appear on http://calcite.apache.org/avatica/downloads, or
> should it have its own download page? I think it probably the former.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
