Mahesh Gudapakkam

@peterjc - no strong views on line wrapping. I didn't realize it was intentional - they just wrapped odd as I was resizing my screen while working so I removed...

i am thinking they (a contributor) should be able to test it locally (as in run jekyll serve on their local machine) and test all pages/links rather than pushing it...

I found this really nice [blog post](http://www.tricksofthetrades.net/2016/04/26/github-flow/) (which I used as a guide to get started, contribute and keep my fork upto date). Would it be useful to either point...

Thanks @MarkusPiotrowski for explaining it and I now understand it well. Will make sure that future commits/pull requests are done in this manner.

I can work on setting this up in _config.yml file - I believe that is where you define directory locations for various assets .. let me know if you folks...

for the record .. these are the IMAGES we currently have ``` $ find . -iname "*.png" -o -iname "*.jpg" ./apple-touch-icon-144.png ./biopython_grey.png ./wiki/Biopython.jpg ./wiki/Biopython_small.jpg ./wiki/Contig_class.png ./wiki/Hmm_discrete.png ./wiki/Hmm_discrete_py.png ./wiki/Journal.pcbi.1000406.g002.png ./wiki/Phylo-apaf-node0.png ./wiki/Phylo-apaf.png...

for the record .. these are the CSS files we currently have ``` $ find . -iname "*.css" ./css/hyde.css ./css/poole.css ./css/syntax.css ```

@peterjc - got it - i now see the difference between the ones under root to those under 'wiki'. So the goal is to relocate those under root to `assets/images`,...