On Wed, 18 Feb 2015 00:43:15 +0100, Richard Hipp <d...@sqlite.org> wrote:

I have switched the default Fossil repo over to using the San
Francisco Modern skin.  Everybody seems to think it looks a lot
better, and I agree.

execpt, maybe the fixed-width layout ...


I think the next step of the ongoing Fossil makeover should be to
improve the homepage:
https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki

Suggestions and especially mockups of how this front page should look
are welcomed.

What are the most important features of Fossil that should be
front-and-center on the homepage?  I feel like the front page is
providing Too Much Information and that eyes gloss over when
first-time readers see all that text.  (Maybe I'm wrong - let me
know!)  So what information can be removed from the front-page and
what are the essential elements that need to be retained?

I've always felt the homepage is quite OK. at the very least, it will not put off prospective users,
I'd say. but to guide a cursory visitor around, yes, it might be better to
restructure it a bit. in this case I would stress these points in the `why use fossil` list

points 1, 2, and 4

as the most distinguishing ones. the others need to be mentioned elsewhere, sure, but they are prob. not relevant for first time visitors. I think the "zero-config/(near)-zero-dependencies/single exec" point
might be especially relevant for first-time visitors/users.

one could also contemplate to just list them with a much shortened
explanatory text in parenthesis and convert the items to links where the full explanation can be found (the present list, that is). then a statement `the full list of properties can be found here' or similar. and immediately thereafter a paragraph
containing pregnant links to `quick start' and `concepts'.

one might also try to restructure the `list for fossil users' by discriminating between "casual user" and "advanced user", especially isolating highly technical material from "understanding concepts and how to use fosill" stuff.

just my 2c



What else can be done to make Fossil easier?

FWIW:  I've made some improvements to the techniques available to
"skin" designers, and tried to write up a brief introduction to how to
design new "skins" at
https://www.fossil-scm.org/fossil/doc/trunk/www/customskin.md -
hopefully this will make it a little easier to design new skins for
Fossil, will lower the barrier to entry slightly, and encourage more
people to come up with innovative new designs.  Please read the
document, suggest improvements to the document, and give a try at
designing a new look if you have talents in that area.  That said: as
soon as 1.31 goes out the door, I'm going to start a branch for Fossil
2.0, which will be completely 100% compatible with Fossil 1.x in terms
of repository and check-ins, but will likely have a modified DOM for
the web interface and thus may break any new skins you come up with
today.  Nevertheless, I want designers to try to make skins using 1.31
so that they can suggest ways of improving the DOM to make skinning
and theming easier in 2.0.  I will help you convert 1.31 skins into
2.0 skins upon request.

Thank you all for your attention and your contributions.




--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to