[bt-devel] Website: Content Migration

[Eeli Kaikkonen]

On Sat, 12 Dec 2009, Raoul Snyman wrote:
> On my OpenLP project we have basically done exactly that. We've separated
> developer content from user content, pushing the developer information to the
> wiki, and then just having links on the site to the different project pages
> (SF.net and LP.net) and a "how to contribute" page which tells users how they
> can become contributors.
>
> If you'd like to take a look: http://openlp.org/
>
> Eeli, that's pretty much what I was thinking as well. Separate the developer
> stuff and keep it on the wiki.

I don't feel that openlp.org has actually separated developer content
from end user content. I would take Project page, SF.net page and LP.net
pages off from the header menu. These should be visible only under the
Develop main section where they could be links inside the main area
text. There they could also be explained - now they are meaningless to
ordinary end users and to some wannabe developers.

The Features link is duplicated in the header menu and in the left side
menu - it should be in one place only, like the Download, Blog and
Forums links. 14 left side links is too much; as we know from basic
usability knowledge, maybe 5-10 items in one place is quite good. Here
the redundancy clutters the interface. That's one reason I want header
area links for BibleTime: we could have fewer left side link area
items.

The left side navigation links shouldn't replace the current site with a
new one like the Contact Us link does (at least without a clear
indicator which tells it will do it).

  Yours,
	Eeli Kaikkonen (Mr.), Oulu, Finland
	e-mail: eekaikko at mailx.studentx.oulux.fix (with no x)