simonsan
commented
4 years ago Probably it make sense to stick to static site generation.
Something like Hugo that also works with markdown, is easy to set up and has some good themes ready to use.
Examples:
- hugo-icon <= probably my favourite
- airspace-hugo
- meghna-hugo
Update: I asked the guys from PB what they use for a static site generator and they were recommending pelican. Will have a look into both. Pelican seems nice because it supports Markdown and Restructured Text file which will make future C&P from our /docs even simpler if we want to write an News post or something. And it's written in Python, so we don't need to get in touch with another ecosystem for pulling in a dependency as for hugo(?). Sadly they don't have any good templates for us there afaics.
TheJJ
When talking to people about openage they often ask for a webpage for more info. I have the feeling from questions coming after sending them to our official website, that the website itself and even the repo (which I often send in addition for even more information) for new people doesn't really give all the information in an easy to find and non-overwhelming way.
So, what do you think of a rework of our the openage - website?
The following examples I took mainly from https://www.projectborealis.com/ and https://www.python.org/ .
About the project borealis website I like that it is streamlined and all the infos are not overboarding. It's one page layout, that I normally dislike, but here it is really made in a nice and clean way.
The python website I personally find too over-boarding with information for a project like openage, where most people want to first be informed about the basic principle of the project itself and afterwards dig deeper into development etc. But I choose it because I find the main menu really clear and also the menu items are really well sorted. You get to the infos you need fast.
Here are some examples what we could add, what we could change and how a good (in my opinion) page could look like from the before mentioned examples:
add a media page with some screenshots of assetpacks (e.g. aoe1de, aoe2de), tools etc.
give (more) frequent updates on a small blog-like page, kind of like the news comment on the reddit, probably more streamlined into a text and not weekly but when something new and exciting happens
documentation/development page to include blogposts about modding api (subpage dev-blog?), link to future sphinx documentation, etc. basically developer resources, here an example from openTTD development page
core glossary/feature overview, what is working, whats in development, what were planning next. basically an overview what we collected in /docs
a nice FAQ or even more verbose as shown in Python's FAQ we could forward people to, when we get asked many of the same questions at once (streams, chat, talks, etc.)
Download page collecting latest direct links to downloads (Github releases, Kevin CI builds, bintray), basically the download links should be in a non-outdating form (
latest-xyz.exe)helpers overview if and where help would be needed
Changelog
in the future something like server-/community browser
What do you think, would it even make sense to ask someone professional to do it for us? I think everyone has already enough to do, also web-design is a good topic to ask someone that is more into the topic then most of us are? Maybe even someone has already an idea who we could ask?
Please state your ideas, suggestions and/or opinions. Cheers!
UPDATE: Another good example i feel is the website of the game-engine amethyst.