Most importantly, I need to write some software to help store the interrelationships between the different patterns and generate the HTML document formats automatically. I could write it in HyperCard, but I want to move on to an object-oriented language. I'm most seriously considering using Macintosh Common Lisp; please see the fantasies page.

Here are some other possible patterns:

-- Accessible Interactivity. People like interactivity; make the interactive documents the first documents accessed, and put the interactivity high on the page. Seen here in both "cards" and "statistics".

-- Low-Depth Trees. Keep the depth of the document tree low.

-- Document Freezing. At some point in time, freeze documents and make it clear that they won't be changed anymore. I don't know why you'd want to do this, but there may be a time...

-- Document-Production Software: Rather than write HTML, use some kind of document-production software to generate your HTML. Or something...

-- Responsible Publishing. Don't publish unless you have something to say. This is very un-pattern-language-y; Alexander NEVER uses words like "responsible" in a pattern name, because it doesn't tell you what you need to do.

-- Physical Tags. I much prefer physical tags to logical tags. No argument for this yet.

-- Single CGI environment. Might be best to have a single cgi environment as opposed to multiple cgi's.

-- Locatable Site. A site should have a sense of location... where is it? who maintains it? How do you ground a site? This is not a pattern in the Alexandrian sense.

-- Changed Document Notification. Perhaps notify people when documents they're interested in have been changed.

-- Other things that I started doing towards the end, but haven't come up with a pattern for (either in the pattern language document, or in my software): subheaders in the table of contents. There are more, but I can't think of them right now...