Am Fri, 06 May 2016 07:48:48 +0000 schrieb maik klein <maikkl...@googlemail.com>:
> On Friday, 6 May 2016 at 03:01:07 UTC, Dicebot wrote: > > On 05/06/2016 04:26 AM, Jack Stouffer wrote: > >> Also, I can just include a simple JS library for the same > >> auto-highlighting functionality. > > > > Please prefer static generators and pygment-like highlighters > > to JS whenever possible. Demanding JS enabled for simple > > programming blog to be rendered decently it simply outrageous. > > I would also recommend a static site generator, I currently use > Hugo https://gohugo.io/ though it is written it Go haha. Jekyll > got really slow after 30 blog entries, especially if you want to > do the syntax highlighting offline. Martin Novak uses pelican(0) for his (1) blog + isso (2) for comments. Markdown blog posts + plugins for everything(3,4) + git + markdown comments + self hosted comments sounds nice. The main problem with static blog generators is that having multiple blog authors is a little bit more complicated. We should at least give direct push access to all authors. You don't want to wait weeks for somebody to pull a spelling fix pull request ;-) And it's a little harder to setup, but maybe we could use a setup which automatically rebuilds the blog once somebody pushes to the git repository. Then users don't need to have pelican installed locally. Maybe use all non-final branches for previewing/testing where every contributor gets a branch. We could use this workflow: git pull # Add blog post git push origin master:jpf91 # View preview on preview.blog.dlang.org/jpf91 git push # View blog at blog.dlang.org (0) http://blog.getpelican.com/ (1) https://code.dawg.eu/ (2) https://posativ.org/isso/ (3) https://github.com/getpelican/pelican-plugins/ (4) https://github.com/getpelican/pelican-plugins/tree/master/liquid_tags