I can help out with writing some of the HTML and css for the pages.

On Jul 30, 2016 08:55, <[email protected]> wrote:

> Hi!
>
> Thanks for your input! After considering all the mentioned options, i
> suppose that using the
> jekyll/github pages combination is the easiest solution for us at the
> moment.
>
> If someone is able to help out with the design, please speak up :)
>
> Best regards,
> Sebastian
>
> Am 18.07.2016 22:58, schrieb [email protected]:
> > Hi everyone,
> >
> > as you might have read on different github issues, i'm currently
> > thinking about replacing our current website due to various reasons.
> > For
> > a start, let's leave the forum as it is (that will be the next thing..)
> > and think about a new home and a new backend for our website.
> >
> >  From my point of view, drupal was quite over-featured for just
> > maintaining the website. It was hard to maintain and we had (and have)
> > problems with spam. As a result, more lightwight systems should be
> > considered for the new website.
> >
> > In previous conversations, wordpress has been recommended by some
> > people. This has been also my favourite for quite some time, since i'm
> > using it also on other projects and it is well maintained. It gives us
> > a
> > slimmer CMS without all the overhead of drupal.
> >
> > After starting to look into the "newer" techniques that came up in the
> > last years, i stumbled upon Jekyll and its github integration. Jekyll
> > is
> > a generator for static webpages which is supported by github for the
> > "Github pages", which can be hosted in a github repository side by side
> > with the source code (in its own branch). This would allow us to host
> > our webpage via github (which is a great advantage since we do not have
> > to care for hosting anymore) and manage the code of the site via git.
> > Having the site in git makes it really easy to propose changes (via
> > pull
> > requests) and would ease collaborative editing.
> > The downside (well, maybe..) is that this setup is basically a static
> > approach, so there is no built-in support for comments (though you can
> > integrate services like disqus). From my point of view, this limitation
> > is not a problem. I'm not keen on moderating posts/comments on the
> > website AND the forum :) And it would be very easy to move the static
> > pages to a different hosting service if github would close its hosting
> > service at some time..
> >
> > I've already pushed some example code to the gh-pages branch of the
> > hydrogen repository which can be viewed here:
> > http://hydrogen-music.github.io/hydrogen/ . This is just the default
> > layout with some content from the curren h2 website.
> >
> > Please let me know what you think of this solution and if there might
> > be
> > better solutions for hosting the project website. Has anybody already
> > experience with hosting pages with jekyll on github?
> >
> > Best regards,
> > Sebastian
> >
> >
> >
> >
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> > traffic
> > patterns at an interface-level. Reveals which users, apps, and
> > protocols are
> > consuming the most bandwidth. Provides multi-vendor support for
> > NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > planning
> > reports.http://sdm.link/zohodev2dev
> > _______________________________________________
> > Hydrogen-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Hydrogen-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
>
------------------------------------------------------------------------------
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel

Reply via email to