Horde3D

It seems that all the news topics posted in 2013 have the gray, embossed, with arrows on the side, header. If I recall correctly this was used only for the latest article, and the older ones were separated by the dotted line.

This is supported by the fact that all the older articles, except for the latter, are separated by dotted lines. The first one with the gray header was the beta 5 announcement that was the latest news article for a long time.

_________________
Paul

True.

BTW I'm thinking about the idea of moving the entire website to GitHub Pages (http://pages.github.com/) and take the opportunity to restyle it for the first stable release.

I am not familiar with the github pages. Would they allow us to keep using the horde3d.org domain? If they would do that and provide us with a gallery alongside the wiki that github already has it would be what we need.

When it comes to restyling the pages, I always liked the minimalist theme and thought that went along nicely with Horde3D's philosophy. I used to do webdev to pay for the bills so I might be able to assist on that side. I'll always have a problem with time, but after March things will clear out a bit.

_________________
Paul

GitHub Pages is basically a host service which provides a control-versioned way of handling project websites.

For simple project websites like Horde3D's one (basically just static content with some javascript snippets) it's perfect because it provides free webspace and a collaborative way of improving the website itself through the same GitHub paradigm.

It also allows to link the website with a proprietary domain (like horde3d.org).

Maybe we could establish some kind of closed beta? I wouldn't like to have a work in progress website publicly available. But in principal I agree that it would help to keep pages more uptodate. Although the current wiki pages offer also the functionality to keep content updated by the community and it isn't used frequently either.

Maybe we could have discussions before merging new features, and have e dev plan similar to how Wikipedia works.

I agree with closed betas on major changes, because the front page is like our business card and we wouldn't want that busted. But for small things like news updates that should not happend.

Also the news could be done by several designated community managers using a simple guide line for a "what is news" threshold.

Along those lines I was also thinking about separating the news in a separate xml file and loading them in the main page via javascript. That way the hustle for updating the news would be minimal and less error prone.

I think that the wiki and the website do not really share the same dev method. The wiki requires creative article writing while sections like the news and gallery require just inserting pictures and events of importance.

_________________
Paul

I meant a closed beta for releasing the pages on github. Of course we don't need a closed beta once the pages are up and running and we just want to change some gallery pictures.

In theory I have FTP access to the horde3d webspace, but as I'm not the owner of the webspace I can't give access to someone else. So hosting it on github would be preferred, as I think there are easier options to maintain collaborators (just a guess, haven't looked at it yet)

First of all I'd try to migrate the website from static HTML to Jekyll (which is used under the hood by GitHub Pages):

http://jekyllrb.com/

It separates CSS and layout from real content (which could be written with trivial Markdown syntax, like anything else on GitHub) and will also make very easy to use the website as a technical blog (news) with static pages (introduction, vision, download, links).

I glanced over Jekyll a bit. Seems to be a nice ruby-based tool for static websites. Although ruby coding seems to be optional it might be just the excuse to get my feet wet with it.

_________________
Paul

Consider that for Horde3D website IMHO no Ruby code addition should be necessary...But feel free to experiment with it, of course

Also found Hyde. Seems to be the same but for Python.

_________________
Paul