Hi Przemysław, Am 20.07.2016 13:24, schrieb el.pescado: > I'd use something as simple as possible. Personally, I'd go for static > HTML pages, or something almost-static like static pages with some > PHP-includes. I think Jekyll falls into that category.
Yes, that's the case. Jekyll generates static web-pages. We have the choice to either generate the content "offline" and push the generated content to github or to put the Jekyll input files to github. > BTW. Instead of dedicated branch, is it possible to host github pages > from dedicated repository within hydrogen-music project? If i understand the documentation correctly, then we can create either an organisation or project page (https://help.github.com/articles/user-organization-and-project-pages/). Organisation pages live in their own repository, while project pages live in the gh-pages branch of the corresponding repository. Using the organization page would help to keep the main (application) repository smaller, but would mean that everyone who works with the page has to maintain a second repository. If there are no other points which i don't know of at the moment, i would suppose that an organization page would suite us better. Best regards, Sebastian > > Regards, > Przemysław Sitek > > W dniu 2016-07-20 00:42:06 użytkownik Paul Vint <[email protected]> > napisał: > >> I'm not really familiar with Jekyll, Sebastian, but from your >> description it sounds good. Lightweight is key, and frankly, I would >> stay away from anything that allows comments.... as you know >> moderating comments is a fulltime job. Having the ability to manage >> the code via git easily is a huge plus. In my uninformed opinion, it >> sounds good. ;) >> >> Paul >> >> On Mon, Jul 18, 2016 at 6:40 PM, Steve Boyer <[email protected]> >> wrote: >> >> Hey Mauser, >> >> We could look at using an openshift solution. Openshift by RedHat >> uses github and would allow us to do our site that way using a lamp >> or wamp stack as a local development environment. >> >> As far as coding backend, do we really need something as fully >> featured as a cms, or can we leave the forums as is, create a static >> site, and then include a common navigation into the forums to help >> marry the two together? One of the big problems I've encountered >> with the cms anf forum solutions is integration, and more >> specifically, the lack thereof. >> >> I've tried most every cms out there, and when it comes to >> non-technical people uploading content to the site, they work great, >> but we have a fair few tech savvy people on this project. >> >> I mainly uae codeigniter on my php projects now. And it's a nice and >> lightweight php framework. I find it great for making static sites. >> >> Just a couple alternative suggestions. >> >> On Jul 18, 2016 18:09, <[email protected]> wrote: >> 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/ [1] . 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 [2] >> _______________________________________________ >> Hydrogen-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel [3] >> > ------------------------------------------------------------------------------ >> 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 [2] >> _______________________________________________ >> Hydrogen-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel [3] > > > > Links: > ------ > [1] http://hydrogen-music.github.io/hydrogen/ > [2] http://sdm.link/zohodev2dev > [3] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
