Website?
Website?
The current website looks ugly. Why not make a new one?
Someone with some pretty basic skills could whip up a site in no time. However, if some server side things need to happen, some more work is required... or you could use wordpress and have that serve the site.
That being said, if you don't use WordPress, you could use SVG on your website.
Someone with some pretty basic skills could whip up a site in no time. However, if some server side things need to happen, some more work is required... or you could use wordpress and have that serve the site.
That being said, if you don't use WordPress, you could use SVG on your website.
-
- Juggernaut
- Posts: 854
- Joined: Wed Aug 26, 2015 6:15 pm
Re: Website?
Ugh, Wordpress? Really?
Re: Website?
I'm happy with current website.
When I first found this game, that page directed me to this forum and the latest releases.
Having a not-fancy website is not a problem IMO (in fact, I prefer it that way).
Also, FreeOrion is in more need of developers rather than players.
When I first found this game, that page directed me to this forum and the latest releases.
Having a not-fancy website is not a problem IMO (in fact, I prefer it that way).
Also, FreeOrion is in more need of developers rather than players.
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Website?
More players are quite welcome. Players have useful comments and suggestions, can turn into devs, can directly or indirectly help publicise to inform or attract more players or devs, and really are a big part of why some people contribute to a project like this: in the hope someone else will play / use it.
Re: Website?
Oh, you're so right, Geoff!
Re: Website?
Well, the current website is just a wiki. Most people will see the front page and think "oh, this doesn't look like much. I'll look somewhere else" or "oh, a wiki. I'm probably in the wrong place." Either is terrible. The webpage fails to communicate that this is the website of a game and any recent activity.
Everything has to be specifically looked for on the website. It actually takes a while to find the download link for the eyes, as there is a lot of text to search. Before the download link is found, most users are already gone.
here are some examples of open source games which have a good website:
Yesyes, 0 A.D.'s website requires some love, I agree. But it's still much better then what freeorion has.
Things which could be done to improve the freeorion homepage:
No, text is not as efficient in communication as images. However, text correctly mixed with images helps a lot.
Everything has to be specifically looked for on the website. It actually takes a while to find the download link for the eyes, as there is a lot of text to search. Before the download link is found, most users are already gone.
here are some examples of open source games which have a good website:
- OpenTTD. You can instantly see:
- That the website is about a game;
- A menu;
- The download link;
- A link to documentation on the game;
- A screenshot;
- Most recent news;
- and a request to help with translation, including which languages need some help.
- 0 A.D.. You can instantly see:
- That it's a game;
- A download link;
- A menu;
- A donate button;
- Some images and a video;
- News about the game.
- The Battle for Wesnoth. You can instantly see:
- That it's a game's website;
- A menu;
- A download link;
- A description of the game;
- Some pleasing art;
- (scroll down)A video;
- (scroll down)Some images.
Yesyes, 0 A.D.'s website requires some love, I agree. But it's still much better then what freeorion has.
Things which could be done to improve the freeorion homepage:
- A menu (preferably at the top (below the image portraying the game) or on the left side of the screen;
- The website needs to communicate that it's the website of a game;
- An obvious download link (think an image);
- An obvious link to the community (again, think an image);
- An encouraging image to contribute (whether it be translation, art or coding), with a link to a page which explains that;
- Some (recent) images of the game on the front page.
No, text is not as efficient in communication as images. However, text correctly mixed with images helps a lot.
Re: Website?
You've got a point there, xahodo.
Maybe you are applying for the web maintainer position or for making a new design? Either of that would be great, I guess.
Maybe you are applying for the web maintainer position or for making a new design? Either of that would be great, I guess.
Re: Website?
I'm willing to do it, but I still need to learn a lot. It gives me some incentive to use my (very limited) web development skills (html, some css, some javascript). However, I'm also afraid I might be inadequate for the job. Especially when communication with the server needs to happen (I'm clueless in that regard).
I would love to help out but, to be honest, I'm scared to mess up.
I would love to help out but, to be honest, I'm scared to mess up.
Re: Website?
Well, ok. Tonight I'm willing to try (haven't got an excuse to not try). But I would like some feedback on my ideas.
At the top I would like to put the FreeOrion logo. Below that a horizontal menu. At the right I'd like to put a download button. Below the download button a donate button.
Below the menu is the space of the website that changes.
The menu would contain the items: "about" (default page), "news", "media", "manual", "community", "contributing" and "contact".
Everything you're able to click on would change color if the user hovers over it. The currently selected menu page would be obviously differentiated.
Now on to images: the download link would contain a down arrow, the donate button would contain a heart icon.
On the about page would be a small text along with a couple of images.
The demo of the site will not be fully functional, but rather serve as an example. I will be busy for a while before I have anything tangible (basically need to learn as I go and I won't be using web design software).
But I need some blessing to start and at least some idea that, if it's deemed better then what currently serves as a front page, I can go off and finish it and that it'll actually be used.
It won't contain any back-end stuff, though (so no database support whatsoever). I'm willing to learn that somewhere in the distant future.
At the top I would like to put the FreeOrion logo. Below that a horizontal menu. At the right I'd like to put a download button. Below the download button a donate button.
Below the menu is the space of the website that changes.
The menu would contain the items: "about" (default page), "news", "media", "manual", "community", "contributing" and "contact".
Everything you're able to click on would change color if the user hovers over it. The currently selected menu page would be obviously differentiated.
Now on to images: the download link would contain a down arrow, the donate button would contain a heart icon.
On the about page would be a small text along with a couple of images.
The demo of the site will not be fully functional, but rather serve as an example. I will be busy for a while before I have anything tangible (basically need to learn as I go and I won't be using web design software).
But I need some blessing to start and at least some idea that, if it's deemed better then what currently serves as a front page, I can go off and finish it and that it'll actually be used.
It won't contain any back-end stuff, though (so no database support whatsoever). I'm willing to learn that somewhere in the distant future.
Re: Website?
Short answer: because we don't have anybody who has the skill, nerves and time to make a better one and is willing to maintain that website long term. The good thing about the current wiki homepage is that it's easy to maintain. It does not help if someone makes a fancy new website, but leaves the project a year later and no one's left behind who can maintain the new website.
That said, you're certainly welcome to put up a prototype for a new website. Don't worry too much about getting it wrong, the current website demonstrates quite clearly that you're dealing with a bunch of people who don't know much about making a good webiste. So, as long as it looks better than what we have now, and, in terms of function, has everything we have now, it most likely will be welcomed as an improvement.
The main issues will be if that new website will work on our current hoster (that means, are all the frameworks, libraries, whatever you use to build the website available etc.), and can someone else take over maintenance should you, for whatever reason, not be willing/able to do that anymore someday (which is quite likely, as only a very few people stay with the project for more than a couple of years - which is perfectly ok, you have to be quite hardcore to stay with an open source project for 10 or 20 years... ).
Re: Website?
I'll give it a try
Placing the download button for the current stable release more prominently is certainly a good idea. However, I'd still also want the links to the test builds, and, if we are currently close to a new release and offering release candidates, a link to those as well on the front page.At the right I'd like to put a download button.
The most recent news entries should also be displayed on the front (=default) page. There can be an additional, separate "news" page where you can see more news (and of course a page where you can see all the old news, like now), but I think it's important that you don't have to go to a different page (even if it's only one click) to see the latest news.The menu would contain the items: "about" (default page), "news", "media", "manual", "community", "contributing" and "contact". [...] On the about page would be a small text along with a couple of images.
Well, I can give you mine. I cannot, however, promise you that we're going to use it, for that it has to meet some requirements (basically what I mentioned in my earlier post above).But I need some blessing to start
Actually, the simpler (implementation-wise) the better. I don't see the need for a database (the only thing that comes to mind would be the news, and for the few news we put on our homepage that can easily be managed by editing static pages accordingly, so a database would be overkill anyway). The less frameworks, libraries, javascript and other fancy stuff you use, the easier it will be to maintain the site (and for someone to take over if necessary). So, IMO, keep it simple and straightforward.It won't contain any back-end stuff, though (so no database support whatsoever).