delftswa / delftswa.github.io Goto Github PK

Hi @delftswa2014/students2015 ! (really hope this cross organization tagging works)

Here (finally) is how we are going to do the book preparation:

• I will create a skeleton
• You can fork this repository, and add your chapter (see the example on how to). This repo includes a Vagrant VM to run Jekyll, following the instructions you can test locally whether everything works
  • You will need to check your links/images yourself, you may use the test_links.rb script in the repo for this
  • Only link to open content (so nothing from your own team repository)
• File a pull request
• I will review
• And possibly merge, or otherwise give feedback

So you are free to do a copy/paste, or you can play around to retain your history (pick yourself).

Good luck and looking forward to the contributions!

Btw: site is http://delftswa.github.io. Be sure to report the site to your project as well (generally they really like it!)

@rogierslag @avandeursen we (team-kodi) also created an appendix and added that to the repository (link) but as you can see upon opening it you don't get a nice webpage.

Should I also add a YAML to this page as well? And should the format be different because I assume the appendix should not show up in the table of content?

Write a short introductory chapter.

Started on this, almost done.

In general, most of the software treated here is quite stable. However some package (e.g. Docker or Tribler) have some big changes coming up. Once this book is indexed by Google as well, this might cause people to believe that the (at some point) outdated information is still current. I'd therefore like to add a date to each chapter when it was published in order to give people some clue how old the information is.

When we think about the future years, this is more pressing. In 2016, some projects on the site might only be a month old, whereas the 2015 edition will be over a year old (unless updated).

@avandeursen what do you think of this?

Also tagging the current chapter generators: @thegeman @JoopAue @trensen @RickWieman @s-ercan @Donenzone @hermanbanken

It would be nice to see how well the book is read.

Configure Google Analytics so that it shows us page views for each chapter?

We already discussed it's going to be Creative Commons CC BY 4.0, but I think this should also be put somewhere in the book (i.e. on the site).

If you boot this repo in Vagrant, the menu is sorted alphabetically (as it should be).
However, on http://delftswa.github.io/, the menu is sorted in a different way (no idea which way, to be honest).

in Figure: Bug Tracker decision tree, the output options of "Joomla! core?" should be "yes" and "no", the "no" output arrow is wrongly tagged as "yes".

In our appendix, we've a multiline code block containing common used commands.
Unfortunately, this block is translated into a very long one-liner by Jekyll:

->

Any thoughts on how to fix this?