[Bioperl-l] New Jekyll theme at bioperl.github.io

[Peter Cock]

Hi Brian,

Very timely - BioJava were just struggling with updating the wiki, and
Spencer is taking a look at the MediaWiki and OpenID plugins:

http://lists.open-bio.org/pipermail/open-bio-l/2016-March/001428.html
http://lists.open-bio.org/pipermail/open-bio-l/2016-March/001429.html
etc (and on root-l in private).

GitHub do try to give advance warning of changes, but using their
system will have downsides - here's quite negative example:
https://github.com/blog/1992-eight-lessons-learned-hacking-on-github-pages-for-six-months

One tiny issue: The search box on http://bioperl.github.io/ has a tiny
width (as is right aligned) under Firefox v44  - but a sensible size
(and left aligned) under Chrome and Safari.

Did you guys migrate all the generic things on the old wiki like the
file format pages to wikipedia or somewhere?

What are you doing about the static content outside the wiki? e.g.

http://bioperl.org/DIST/ <-- still important, or all on CRAN?
http://bioperl.org/SRC/ <-- looks like from pre-git days
http://bioperl.org/media/ <-- used in some documentation?

Those are the only things that came to mind before making the
DNS changes to point bioperl.org at bioperl.github.io

Note we'd want to check the @bioperl.org email addresses would
still be OK.

Regards,

Peter

On Fri, Mar 11, 2016 at 1:53 PM, Brian Osborne <bosborne11 at verizon.net> wrote:
> Chris and Peter,
>
> A bit late with this, but you may have noticed: bioperl.github.bio now has
> search capability, it’s ready to take the bioperl.org address.
>
> Peter, we talked about this a bit. Turns out it is not hard at all. Jekyll
> is file-based, no database there. There’s a Liquid template (/search.json)
> that’s used to convert all the HOWTO’s (and misc. other files, 111 pages in
> total) to JSON, in a single file (/_site/search.json). Then some simple JS
> (Jquery) searchs this file. The performance is good, on the other hand the
> JSON file is not large, 963 lines.
>
> There is remaining work upcoming. In May GitHub will disable all the
> Markdown converters except for kramdown, and we’re using redcarpet. I did
> some testing, it appears that our tables are not converted by kramdown, they
> will all have to be fixed. My guess is that this will be straightforward.
>
> Thanks again,
>
> Brian O.