[
https://issues.apache.org/jira/browse/TINKERPOP-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594803#comment-15594803
]
ASF GitHub Bot commented on TINKERPOP-1485:
-------------------------------------------
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/459
I tried to use this to update the site for 3.2.3/3.1.5 and it didn't seem
to work. It didn't error, but nothing seemed to go to svn. Also, I see you
create a `site/target` directory. I was using the root `/target` for stuff in
my scripts. Is there any reason not to make that consistent? i'm fine with your
directory local to `site/` btw - that's fine as long as it's all in one place.
> Move source for TinkerPop site to source code repo
> --------------------------------------------------
>
> Key: TINKERPOP-1485
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1485
> Project: TinkerPop
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.2.2
> Reporter: stephen mallette
> Assignee: Daniel Kuppitz
> Fix For: 3.3.0
>
>
> Some time ago there was discussion on the Mailing List to move the web site
> to the source code repo so that it could be contributed to via pull request.
> It would be nice because then we could better rely on some basic static site
> generation to help deal with repetitive and sometimes error prone process of
> updating the header for the pages.
> Anyway, a few thoughts:
> 1. need a shell script to publish the site to svn - something like
> {{bin/publish-site.sh}}
> 2. place files in the root of the project in a directory called {{site/}}
> 3. if possible, do some basic site generation with maybe some groovy script
> or just the shell script mentioned above to inject a "header file" for each
> page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
