[Smaug] Smaug Web pages
Rick Moen
rick@linuxmafia.com
Thu Jan 31 08:18:01 2002
[Sorry about breaking threading, but I had already deleted David G's
posts, and had to pull them out of the Web archive.]
David, thank you for doing the site overhaul. I'm sure it needed it.
> ...moved the detailed info about the meeting to its own page, since it
> looked really rather out of place on the front page...
Since you're doing the lion's share of the work, I defer to you on this
point, but please consider: In my experience, the information people
look for most on a user group site is "where, date, time" event info.
Putting summary details of this as prominently as possible (with the
most-crucial data in "strong" or "em" tags) on the main site page has
two benefits (BIG HONKING benefits, methinks):
o It's what viewers seek most often.
o Such text calls your attention to it, when it needs updating.
Most user groups' sites advertise outdated "upcoming" meeting data most
of each month, which from the viewpoint of public outreach is worse than
no data at all, as it make the group look like it might have folded.
This doesn't mean that the index page need be crammed with event
details: Just the where/date/time stuff need be there, to give visitors
an at-a-glance grasp of where and when something will be happening.
ALSO: I think it's a _really_ good idea to include those same brief
where/date/time details on the next _several_ upcoming events, NOT just
the one next one. Why?
o Because deferred maintenance is inevitable. If you list only one
event, I guarantee you'll end up advertising only outdated "upcoming"
meetings some large percentage of each month. This is A Very Bad
Thing.
o Because some people like to do calendar planning for more than just
the next two weeks or so -- without having to keep revisiting sites.
The whole point of having a predictable date formula like "first Monday"
is to be _able_ to have data like:
Monday, Mar. 4, 2002, 8 PM
Monday, Apr. 1, 2002, 8 PM
Groups that _have_ such information in advance should find it in their
interest to highlight it, early. I _strongly_ urge that you revisit
this matter. (This is based on watching a lot of user groups for a lot
of years.)
The link from the main page is to "meeting.html". But there is no
such page: The file you created for that purpose was "meeting.sub".
So, you've banished event details to a broken link. Oops.
But, if you repatriate that meeting info to the front page, that'll
get fixed. I urge you to consider that.
I'll 'fess up to having had a vague notion that I should have been
fixing up template.html, and having flaked out. Reading your
most-recent messages, I notice that you're making more-extensive use
of "#include" directives. Thus the *.sub files.
I'm running on a sleep deficit, and this is going to be the workday from
hell (again), so please be patient if I'm a bit dense on this: I didn't
quite follow your explanation yesterday, about your site revs. Well, I
sort of did, and sort of didn't.
If and when you have time, it'd be really, really helpful if you could
take half an hour and write a short piece outlining the logic behind
(and primary techniques used in) the site, naming conventions, etc. It
should end up eventually, I think, in the project pages' Doc Manager, in
part because that's where aspiring site maintainers are going to look
for our collective knowledge to be documented.
I know coders hate writing documentation: That's why I'm volunteering
to do as much of the annoying parts as can be taken off your hands. But
half an hour of your time now will probably go a long ways towards
avoiding having well-intentioned but poorly informed shlubs like me
messing up your work.
(I also know that coders are incurable optimists. That's why it's handy
to have a sysadmin like me around to sprinkle pessimism and caution on
the assumption that everyone's going to think and understand before
leaping in and fscking everything up. ;-> )
Anything we can do to make the HTML _self_-documenting is probably going
to be good, too. What's clear to the original creator isn't necessarily
at all obvious to others trying to help.
Some piddly-ass trivia:
When I tidied up your original HTML, one of the things I did was put
whitespace and line-breaks in the table tags so they were readable. The
tables were the one single, murkiest, most difficult to read part of
your design.
Your revision wiped out my cleanup of your table formatting. (Of
course, I _should_ have done it in the template, as well.)
I also had yanked "base URL" tags out wherever I encountered them. Why?
o Because they seemed to have zero utility, in the first place.
o Because they made the site contents non-portable.
One should be able to take a wget or CVS checkout, put it on one's local
site, and not get extreme breakage. The "base URL" tags _were_
breakage. Deep-sixing them was a no-brainer.
While I was at it, I fixed all absolute URLs, making them relative,
and eliminated the common error of linking to "index.html" instead of
to "./" (and to "index.html#foo" instead of "./#foo"). Why? Think
about caching for a moment, and you'll see why.
Your site revs have reintroduced hyperlinks like "/index.html" again.
In my view, that's breakage from both the absolute-path standpoint
and the caching one -- and should be fixed.
OK, I have to get back to my workday from hell, again.
--
"Is it not the beauty of an asynchronous form of discussion that one can go and
make cups of tea, floss the cat, fluff the geraniums, open the kitchen window
and scream out it with operatic force, volume, and decorum, and then return to
the vexed glowing letters calmer of mind and soul?" -- The Cube, forum3000.org