[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Site update
On Wed, Nov 04, 1998 at 11:03:59PM +0100, Christian Reiniger wrote:
> Ok. Can you start some list about the "getting started" items we should
Probably? I did some work just before my exam today:
Perhaps we need to add a motivation with the importance of a good
infrastructure. And maybe hint in a link to the Catherdral and the
Bazaar.. if we agree that open source is beneficial to Linux game
development than I see no reason not to promote it. =)
This section gives help on setting up a project infrastructure, such as:
A decent website is a must-have: it allows you to inform the
(potential) users of your project about your goals, new releases and
practically any news item related to the project. Also, it allows
direct feedback from the users.
<b>Web site hosting</b>
Your website needs to be hosted somewhere. Not everyone has their own
domain or even web account. We recommend a two-step approach:
<li>Get a <a href="http://www.geocities.com/">Geocities</a> or <a
href="http://members.xoom.com/">Xoom</a> account and build a temporary
yet near-finished site there.
<li>Show that site to <a
"host sites that are related to gaming under the Linux operating
system" and have many benefits over other accounts, such as a direct
link form their pages to your project's page.
<b>Web site design</b>
Go for simply, classixc, readable and not for high-tech state of the
art. First of all, you want to put most of your efforts in developing
a game, and not in creating a superb website representing a vaporware
A few items your website cannot do without (in random order, some
apply to open source projects only):
<li>A background page with your goals and motivations.
<li>A contact address for e-mail feedback.
<li>Screenshots. As soon as you can make snapshots, do so and post
them. Users seem to love screenshots and site visitors with graphical
talents might be aspired to join development when they see screenshots
that are below their personal standard.
<li>A detailed list of features and storyline. Show that you have more
than an idea, that you have a plan!
<li>A wishlist for future releases and a description of the current
status of the project. This will clarify why certain things don't work
(well) yet. Also, it will allow your project team to remind all the
brilliant conceptial ideas without having to scroll back through
<li>A list of required hardware/software/libraries, complete with
links on where to get those requirements.
<li>An HOWTO-Compile document, not only answering the most common
questions to the compilation of your project's sources, but also of
the required software/libraries. Your website needs to be a one-stop
solution, most users like to get the answers at one place.
<li>Download locations of your binaries and source codes (possibly
Bla, any suggestions? (with the previous mails in this thread in mind,
what's in there won't be forgotten)
> Weird time for exams... But of course good luck and even better learning
> progress ;)
Passed two, hopefully the third one as well.
> Error: Windows not found - (C)heer (P)arty (D)ance
I don't see the error? In my case a lack of Windows is intended. ;)
Rob Kaper | mail: firstname.lastname@example.org email@example.com firstname.lastname@example.org
| web: http://capsi.com/ - icq: 707085
| "Hate you so, love you more, I'm so elastic!"