IEEE Transactions on Software Engineering

Hint on the RSS feeds (Using the Encyclopedia RSS as an example) We know the feed is all about the Encyclopedia, so there is no need to repeat the information on every entry. "Update of the Page..." and "New Page Added" is also superfluous. We all know (or don't really care) that the URI is interaction-Design.org/encyclopedia/. There is also no need for a date declaration in the headline, as there is a date-stamp on all RSS entries (assuming your feed validates). We *do* care about the page that has been modified. My suggestion for a fix is this (for headlines): New Page: Mock-Ups Updated Page: Personas Leave off the .html suffix. Again, no one cares that you are writing HTML pages. What happens when you go to PHP (or whatever)? A better solution would be to totally get rid of such things in your URIs all together. Your URIs should be in the form of: http://interaction-design.org/topic/pagename/ This will "future-proof" your URIs. I can give you more info, but this was tangential to the RSS hints I'm giving. In your body, you have totally separated what was done (action) from the object. You need repetition here. The body should be something like this: Rewrote the whole encyclopedia entry for Mock-Ups An even better idea is to actually put the new data *in full* into the feed entry. Show us the new version of Mock-Ups. The site has some good potential. I'll help in any way I can.

Hints on your form. Don't make me erase all the stuff you have in your text entry screen. It's more than a bit annoying. Use Javascript to delete it on focus, or don't have it there in the first place (especially as it is below the form field). Your parser shows visible escape-characters on single quotes. You'll want to fix that. You'll also want to fix the odd "correcting" that occurs in the name field. I am CM Harrington, not Cm Harrington. You don't tell us that you are munging names. Your email obfuscation isn't sufficient. I would suggest a more "bloglike" approach and ask for both an email and a URI. Publicly show the URI, and only keep the email for yourself (for potential follow-up or kill-file purposes). Also, Domain/IP addresses should be kept private. No one cares about them, unless you are going to attempt to target a denial-of-service attack.

Your text will appear here !