* Ricardo SIGNES (samael-vim@...
> Working from this, I hope we can develop a proposed site tree for
> vimonline and begin work on fleshing it out.
> * answ.html - not quite a FAQ, not quite a brief guide
> Something like this could be useful on the new site: a
> feature-oriented FAQ. I don't think we have one, really.
> This is something that should be integrated with the :help
> files and manual. It could be a FAQ with very simple answers
> and extensive linking into the manual.
> I don't think we have this, yet.
Yes; ultra-to-the-point docs are important to new users, and even long
time users who never progressed far into the more advanced stuff.
A terse quickstart explaining the basics of modal editing and the basic
commands (a, A, i, I, [n]d[x], search and replace, :w and :q) will
probably go a long way to helping new users get used to vim; after that
a FAQ like that will be very useful.
> * binaries.html - links to mirrors for binary distributions
> A page like this probably belongs under 'mirroring info' on
> the downloads page.
I'd say the mirrors would be best integrated into the download page,
either with multiple links, a server side script redirecting (maybe
based on a previously set preference), or something similar.
> As has been mentioned, the downloads page is a little
It's conveying a lot of information; what the files are, the current
name, the naming convention, and a description. A lot of that could be
removed (naming conventions are explained on the ftp anyway) and
regorganised. A table would probably be a suitable way to organise it.
This is where nested tables might actually be used in a GOOD way.. :)
> * chat.html - links to vim IRC channels
> This is a good idea, and can probably go under 'support' as
> one or two lines of 'where to find good vim irc channels'
Agreed. I don't think a web IRC client's needed; it's just cruft.
> * deve.html - vim development goals and 'mission'
> This is actually a really good page, though somewhat hard to
> follow. Things like this should be listed in the SourceForge
> project page, possibly as project documentation. It would be
> nice to get an idea of what vim is supposed to be and not be,
> in detail; also, it'd be nice to see where it is going.
Yes, perhaps worthwhile linked to from a description of some of vim's
> * dist.html - a list of vim distribution mirrors
> Sven's page is -really- long and detailed, but most of the
> detail could easily be displayed only when requested, to make
> the list easier to see at a glance.
My eyes go funny on that page. Again, I'm sure it can be integrated
into the download page, with the (mostly) pointless details linked on
subpages if the user really cares about contact information etc.
> * docs.html * doc/ * howto/ - an overview of vim documentation
> Most of this is already covered by vimonline's documentation
> pages (vimdoc.sf.net), but that page needs to be brought in
> line with the look of vimonline. Also, more 'official' HOWTO
> like documentation should be listed -- things that are longer
> than tips.
A documentation links page will probably be useful, but I want to
emphesise the importance of some friendly documentation on the main
site; stuff you wouldn't be afraid of pointing a total Vim newbie to.
Long lists of John Doe's vim howto pages on GeoCities or whatever
doesn't fit into that category :)
> * features.??.html - a brief description of vim in 6kB
> The brief description in 6k is a nice running project, and
> should be maintained as part of vimdoc, probably.
An About Vim page, linked to from the front page with a 3-4 line
description of Vim perhaps.
A features list similar but more complete than the whyvim page on
vim.sf would probably go well in there; I'd prefer we concentrate on
demonstrating why vim is a good editor than "Why you should use vim, cos
we're rabid zealots!!!!11111" which is what most people read into any
"advocacy" pages :)
> * hist.html - release dates of vim
> This 'brief history of vim' is nice, and should be expanded, I
> think, into more of a narrative history. Bram can write this
> in his copious spare time. :)
Yes, preferably without Sven's evil date format :)
> I'm not sure where we'd put this. Possibly in an extended
> 'about vim' page that expands on the little "What is Vim?"
> blurb on the front page.
<looks up a few lines>
Stop looking over my shoulder! ;)
> * index.html - huge file; news; FAQ;
> This page is wildly out of date, in many ways. "Read
> about some new features of vim-5.4!" The news is already
> incorporated into vimonline. Again, though, we need a FAQ on
> vimonline, probably linked from the main page, possibly linked
> from 'about vim' and/or 'support'.
It's the classic Too Big For It's Own Good page. The answer to the
meaning of life could be on there and you'd never find it.
> * lang.html - a list of syntax files and their maintainers/etc
> This page, too, is way out of date. This is rendered obsolete
> by the scripts archive.
The scripts archive includes all the syntax files?
A list of data like that ripped out of the latest distributions would
probably fit well somewhere, maybe under support ("Q: Where do I report a
bug in highlighting <something>? A: Contact the
> * macs.html - news for vim for macintosh
> News alone should mostly cover this. Adding a 'type' field to
> news items and letting users filter on that should entirely
> cover this.
There's a lot of information on that page that won't fit in a news page.
It can always be linked to from the main site anyway; who cares if we
don't provide copious details about how the Mac stuff is progressing or
how it's configured by default? If that info is included, it needs to
be for all platforms.
> * mail.html - vim mailing lists
> This is covered by the 'support' page, although 'support' does
> not list some of the more obscure lists. Maybe we should have
> a 'more lists' link to find the non-English language lists,
A seperate lists page with a way of subscribing easily won't go amiss.
is a nice example; linked to from
the "Getting Help" page.
> * orga.html - information about the domain vim.org; maintainer, email
> addies, etc
> Redundant, especially if vim.org will point to vimonline.
A site should always give some info on who owns and maintains it,
whether vim.org points to vim.sf or becomes a site in it's own right.
Personally I'd prefer it become a site in it's own right, if only
because vim online is more concentrating on the script/tips database and
vim.org more on the basics of how to get vim, how to use it, where to
get support and more information. Keeping the third party script/tips
stuff on a seperate page will help keep the main site uncluttered and
> * pics.html * pics/ - banners, buttons, and screenshots
> Screenshots are already covered by the Why Use Vim? page.
> Banners and buttons should go under our 'About Vim' page, or
> under an 'Advocacy' or 'Community' section. (Community could
> also contain the IRC info.)
Sounds reasonable. That will aid crosslinking from support without
pushing stand-alone but potentially small snippets of information
outside the main document hierachy.
> * prayer.html - Pater Noster for Vim
> I don't know; we could include this somewhere. It strikes me,
> like the 101 addiction signs, as not being particularly useful
> or funny. Maybe under 'Community' or 'Advocacy'.
Community -> Funnies, or so.
> * quotes.html - quotes about vi and vim
> This is an amusing page, and belongs under 'Advocacy,'
> 'Community,' or 'About Vim.' Maybe we should create a quotes
> list, like tips and scripts, so that excellent / amusing
> quotes can rise to the top.
Again, sounds like a third party site thing; I do see potential for
having a random quote picked like a tagline for each page, as a link to
a list of them.
> * search.html - search engine interface
> We have this already; if we need a more extensive one, we can
> link to google with site:vim.sf.net
Text gadget in bottom left or top right. :)
> * setup.html - Sven's minimal vimrc
> This can be a single tip, or several. It doesn't need its own
> page on vimonline.
Basics on customising vim would fit well under the beginner documents
> * tree.html - a site map
> This page is incredibly out of date. We don't really need
> it, but once we decide how to lay out vimonline's expanded
> content, we'll have one anyway.
Pfft, site maps are a crutch to poor navigation structures ;)
> * users.html - links to pages of other vim users
> This is covered by user info. Users can list their own links
> to their pages there.
Community -> User Sites
> * press/ - vim in the press and in reviews
> This kind of content should be better organized, and on the
> vim 'Advocacy' page, or as news items. Or both!
Now now, let's not turn into Amiga users and wet ourselves whenever our
favourite editor gets mentioned somewhere ;)
> -- end --
* Index - A few lines describing vim and linking to more detailed
pages, a list of news.
* News - full news interface.
* What Vim Is - More detailed explanation of modal editing etc
o Features - Similar to vim.sf.net/whyvim.php, with less emphesis on
"this is why you must use it"
o What Vim Is Not - Description of design philosophy, why vim is
unlike emacs, etc.
o License - link to iccf stuff, maybe;
* Getting Vim - Main download list, link to main ftp, nav to older
versions (probably some logic to support mirrors,
browsing versions etc)
o Mirrors - list of mirror sites, maintainers etc.
* Getting started with vim
* Configuring vim
* Web interface to the docs
* Link to third party howto's etc.
o Mailing lists
* List archives
* Community - Unless this gets very long, this will prolly be one page;
o Third party pages; user pages et all
o IRC Channels
o Um, etc.
Thomas 'Freaky' Hurst - freaky@...
A healthy understanding of the way the universe works.