Polishing D - suggestions and comments

[Unknown W. Brackets]

My suggestions would be (obviously just my opinion):

1. Before writing any backend, verify with Walter what the server supports.

2. Make sure it supports moderation (frontend should emphasize this.)

3. Moderation would probably be presented with the author, date, 
comment, and page commented for approval - one big list, I'm sure.

4. An rss feed with an optional filter for the page, would definitely be 
useful.  Most likely it would have a flag for approved/unapproved.

5. Some way of highlighting D code within comments would be nice 
(possibly marked up with <code>?)

6. If you're going to use JavaScript, assuming you provide some sort of 
fallback (like a link) to people who have no JavaScript, it might be 
nice to allow the comments per-section in the specification pages.  I'm 
not sure how this would work, though.

For reference, I suggest looking at the PHP pages which have similar 
functionality:
http://us.php.net/array_rand
http://us.php.net/manual/add-note.php?sect=function.array-rand&redirect=http://us.php.net/manual/en/function.array-rand.php

But again, these are just my suggestions.  Hopefully if Walter or anyone 
else have any specific ideas they will say something.

-[Unknown]


Daniel wrote:
> Walter Bright Wrote:
>> I sent the source to the site to Daniel. Let's see what he can do with 
>> it! The look is controlled by just two files - style.css and doc.ddoc 
>> (which has all the macro text).
> 
> I'll certainly take a look when I get home.  At the moment, it's 11:38 am and I'm at work.  : p  I'm currently in need of a breather to work out more theory behind my parser/interpreter; so this just might do it.
> 
> After I've read the files, I shall focus on first things first; getting the comments inlined into the documentation page, collapsable and clearly indicated as just comments, and then writing a comment post form generator in javascript (which hides it from spam web trawler scripts)
> 
> Ideally, comments should be visible both on the page and in a centralized place, and possibly with an RSS feed.  Who disagrees?  Preferences?  Other features?
> 
> Regards,
> Dan