This is my own review of my final project CluelessPC.com web site. The [revised] dynamic features of the web site are highlighted below.
The web site's CMS is designed to store content in multiple langueages, and to serve content in the preferred language of the user. It does this at the paragraph-level. So if a user has an account and is logged in, they will see content in their preferred language if it is available, defaulting to English if it is not.
The CMS data model is a simplification in that it assumes that translated content will always map from one language to another paragraph-to-paragraph, which seems like a long shot. It also uses languageid at the tbldoccom level, so effectively for the moment titles are all in english. An easy work-around would/will be to make a new componenttype for title and build support for it in the getContent processor.
One nifty aspect of the architecture is that users can have as many languages of preference as they like, and the language choice (from the processor's point of view) is not stored in the url variable, so in theory someone who was fluent in several languages could potentially see content, which was incomplete in any one language, in a flurry of different familiar languages at once!
The website allows users to login and handles whether they are able to successfully log in or are denied.