This repository holds all the markdown required to build the Performance Pipeline site
HTML CSS
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
css
design
development
images
production
requirements-analysis
test
.gitignore
CNAME
README.md
feed.xml
feed.xslt.xml
index.html
sitemap.txt

README.md

Performance Pipeline

"Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum."

Contributing Content

The website is hosted by Github Pages and generated by Jekyll from this very same repository. The source of the website is in the jekyll-pages branch and the HTML is generated to the master branch. Depending if you have write access you either want to make direct changes or via pull requests. Just make sure that your changes land in the jekyll-pages branch!

Install Jekyll

First step is to install Jekyll. There is great Installation Guide on their website that should do the trick. Once Jekyll is installed there are couple of ways how to set up your workflow.

Making Changes Locally

Open up the Markdown md files up in your favourite editor and make changes as you wish. To see them in action run jekyll serve in the jekyll-pages branch and Jekyll will spawn a webserve serving the content on localhost on port 4000.

Pushing Changes Live

Once you are finished with everything you are ready to update the actual HTML. Commit everything you've done and generate a site based on your changes. Here the easiest is to checkout the same project to a separate folder. For example ../perf-pipeline-master. So now you will have 2 folders with the project source code. One of them will be on the branch jekyll-pages (the one you are making Markdown changes at) and the new one on branch master.

Now issue a command to generate the site to the folder that has the master branch active. This example will generate the HTML to the folder .../perf-pipeline-master.

jekyll build --destination ../perf-pipeline-master

Now the updated website sits in the master branch version of the repository. You are ready to commit the changes in that branch and push them to Github. Once that happens you will see the website updated at Performance Pipeline website.

Pull Requests

If you don't have write access to repository then you can do pull requests to the jekyll-pages branch.