[
https://issues.apache.org/jira/browse/QUARKS-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187427#comment-15187427
]
Samantha Chan commented on QUARKS-2:
------------------------------------
I am new to the Apache set up. Is it true that if we push our content to
Github here:
https://github.com/apache/incubator-quarks-website
It will automatically get picked up by:
https://git-wip-us.apache.org/repos/asf/incubator-quarks-website.git
And then you can publish the jekyll website?
Assuming this is true and we agree to take Alex's work as initial content,
here's what I would suggest we do.
1) Alex to fork https://github.com/apache/incubator-quarks-website
2) Replace the files from _site with the content in Alex's repository. I
believe the files should work as-is once it's delivered.
3) Alex delivers code to his fork and create a pull request.
If the code does not get mirrored back, how do people normally contribute code
to Apache? We need to follow that process.
To get the generated site content, I think you can do this... assuming you have
jekyll running on your machine locally.
>From the root directory of the site, run 'jekyll build'. This will generate
>the _site folder, which contains the website content.
Thanks!
> Initial web site content for quarks
> -----------------------------------
>
> Key: QUARKS-2
> URL: https://issues.apache.org/jira/browse/QUARKS-2
> Project: Quarks
> Issue Type: Improvement
> Components: Web Site
> Reporter: Kathey Marsden
> Attachments: QuarksScreenShot.PNG, QuarksScreenShot2.PNG,
> QuarksScreenShot3.PNG, quarksimages.zip
>
>
> The quarks web site content is based on a cloned template which refers to
> SYSTEMML. It would be good to have at least minimal quarks related content
> before publishing with gitpubsub to the public website. The repository is at:
> https://git-wip-us.apache.org/repos/asf/incubator-quarks-website.git
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
