GitHub user rawkintrevo opened a pull request:

    https://github.com/apache/incubator-streams/pull/364

    [NO-JIRA][WIP] Jekyll Refactor

    Was looking at working on some of the website cleanups listed in the CWiki
    
https://cwiki.apache.org/confluence/display/STREAMS/Apache+Streams+Website+TODOs
    
    Was appalled at amount of work required for simple website updates
    
http://streams.incubator.apache.org/site/0.5.1-incubating-SNAPSHOT/streams-project/website.html
    
    Decided it may be new out easier to refactor to a better CMS for _just 
these_ updates, not to speak of long term maintainability. 
    
    Jekyll is standard for most TLPs. 
    
    Trying to sort out how the hell the website is actually constructed is not 
trivial. Some of the .md files I currently have in I know are from wrong 
versions.
    
    Also there is a LOT of documentation that simply isn't accessible from main 
site- this is a problem in its own right. 
    
    Opening this as a conversation starter, will open JIRA if we decide to move 
forward. 
    
    


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

    $ git pull https://github.com/rawkintrevo/incubator-streams jekyll

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

    https://github.com/apache/incubator-streams/pull/364.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 #364
    
----
commit 615c28681b20596c9f262decc9f9d672241c0970
Author: rawkintrevo <trevor.d.gr...@gmail.com>
Date:   2017-04-21T04:38:51Z

    Jekyll Refactor

----


---
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