diniscruz / book_practical_git Goto Github PK

Question: Why does the repo use /manuscript/*.txt files instead of .md? Switching to Markdown extension would make it easier to read in GitHub since it would render the markdown and show any possible formatting issues.

https://github.com/DinisCruz/Book_Practical_Git/blob/master/manuscript/addingfilestoteammentorswebrootviaauserdatafoldersyncedwithgithub-2.txt#L123-L124

At the moment the content (see below) is organised by 'published month' and it would be better if it was split by topic (like what was done for the Angular_JS book)

https://github.com/DinisCruz/Book_Practical_Git/tree/master/content)

https://github.com/DinisCruz/Book_Practical_AngularJS/tree/master/content

Since there are quite a lot of Git users out there that are trying to figure out how to do CI using GIT, and a large part of the blog posts that are already on this book talk about how we are doing CI at SI and TeamMentor

this is what it looks like at the moment

this is what it should look like (when using this tool https://github.com/o2platform/leanpub-book-site)

I noticed some funny semi-markdown while reading the book on the train today:

**_  
_**  

https://github.com/DinisCruz/Book_Practical_Git/blob/master/manuscript/addingfilestoteammentorswebrootviaauserdatafoldersyncedwithgithub-2.txt#L41-L42

https://github.com/DinisCruz/Book_Practical_Git/blob/master/manuscript/addingfilestoteammentorswebrootviaauserdatafoldersyncedwithgithub-2.txt#L123-L124

Probably other places too. I'll need to grep to find all instances.

Some of the chapters have content that users git/GitHub, but its focus is on another topic

These Chapters would be better in another book (or deleted)

see https://github.com/DinisCruz/Book_Practical_Git/blob/master/manuscript/Creating_a_version_TeamMentor_which_uses_the_new_GitUserData.config_file.md

and compare with original

http://blog.diniscruz.com/2013/03/creating-version-teammentor-which-uses.html

This is not good at all, and I need to figure out the root cause of this prob (and hopefully there will not be other posts with it)..

That said, I did find a weird image on a post I fixed a couple days ago (need to go back into it a look at why)

Here is the problem:

at http://blog.diniscruz.com/2016/02/reverse-engineering-recently-patched.html