GitHub user ptgoetz opened a pull request:

    https://github.com/apache/storm/pull/330

    STORM-567: Move Storm Documentation/Website from SVN to git

    This is a work in progress on migrating the storm website/documentation to 
git in order to make it easier for the community to contribute updates. If 
there is enough interest in contributing, we can create a feature branch to 
better enable collaboration.
    
    This is more or less a straight copy of the current website content, with 
the following enhancements:
    
    * Use bootstrap for layout to make docs mobile/tablet friendly
    * Restore syntax highlighting for code snippets
    * add a documentation index page listing all doc links.
    
    I haven't worked on branding (e.g. integrating the official logo, color 
themes, etc.).
    
    I'd love collaborate if anyone is interested, especially anyone with better 
front-end skills than I. ;)

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

    $ git pull https://github.com/ptgoetz/storm documentation

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

    https://github.com/apache/storm/pull/330.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 #330
    
----
commit ebb48e393485d38fe906e81c0d0162e32d3b5d6a
Author: P. Taylor Goetz <ptgo...@gmail.com>
Date:   2014-11-26T19:16:30Z

    add docs directory and WIP on website/documentation migration to git

commit 1ef421ff59563ab5e3341c5e5bd1c9b1a685ec1e
Author: P. Taylor Goetz <ptgo...@gmail.com>
Date:   2014-11-26T19:18:11Z

    add jekyll _site directory to .gitignore

commit ce25aa5710d2692cac64a7820d5cf10279e10a09
Author: P. Taylor Goetz <ptgo...@gmail.com>
Date:   2014-11-26T19:20:38Z

    add link to documentation index

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to