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

ASF GitHub Bot commented on GEODE-2507:
---------------------------------------

GitHub user metatype opened a pull request:

    https://github.com/apache/geode-site/pull/1

    GEODE-2507 Add gradle tasks for compile and view

    Add gradle tasks to make it really simple to compile and view
    the website. The gradle task relies on a docker container,
    apachegeode/geode-site-build that has the build chain preinstalled.
    
    There's also a preliminary cut at improvements for publishing the
    site content.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/metatype/geode-site master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode-site/pull/1.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1
    
----

----


> Acquire and populate new geode-site repo for the web site
> ---------------------------------------------------------
>
>                 Key: GEODE-2507
>                 URL: https://issues.apache.org/jira/browse/GEODE-2507
>             Project: Geode
>          Issue Type: New Feature
>          Components: web-content
>            Reporter: Karen Smoler Miller
>            Assignee: Karen Smoler Miller
>
> Move the web site content to its own repo.
> 1. Acquire the repo.  Name it geode-site.
> 2. Populate the repo with the current web site's contents on the master branch
> 3. Request that the asf-site branch be switched from the geode repo to this 
> new geode-site repo, and test that everything works
> 4. Update the contents of LICENSE files for geode and geode-site
> 5. Setup auto-publish by creating an INFRA JIRA ticket
> 6. Revise README for publishing instructions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to