Until recently I couldn't have pointed you to a website I'd created with Domino (apart from the obvious of course). All my work has been on intranets. Then came Kwik Kopy AU and now I am working on a new version of ShowLED.com. With this transition comes a new way of thinking. There are things you can get away with only on an intranet - not the web.
With ShowLED, the migration is not so much about the need to move to Domino as it about moving away from Flash and framesets. With this site and most others its ranking on Google and other search engines is the paramount factor. To help improve this ranking it's important to design the site to be search engine friendly (SEF). Flash and framesets are not SEF.
But Domino sites, by default, aren't particularly easy for Google and the like to trawl. We can change this though and the tip I described yesterday is a step in the right direction.
Take a link like the one below, which Domino produces at the view-level when you use @Command("Domino"; "ViewNextPage") in a hotspot, which is not SEF at all:
<a href="" onclick="return _doClick('80256F3200314563.c06de816f1bb457f80256f40004834f5/$Body/0.131A', this, null)"> Next » </a>
This one isn't really very SEF at all. This link works by using a redirect (HTTP Status code 302 returned). As far as I know, Google will not index a link that actually returns a different page. This is the basis behind the way Movable Type now prevents comment spammers on blogs from improving their PageRank, whereby URLs are masked by a separate call to a script that performs the redirect.
Now, I wouldn't stake my reputation on the validity of the above statements, but I do think that it's best to keep things simple and link to real pages, whilst keeping the links nice and simple. To do this you have to do things yourself. As I keep on saying - don't let Domino create your code; do as much of the HTML coding as you can on your own.
Furthermore, look again at the view navigation link that I included above. The _doClick() function is not SEF as it involves submitting the form, which Google spiders won't do.
All these nice and easy @Functions are fine on an intranet but next to useless when you want a search engine or disabled user to get about your website.
There is also talk of Google not liking Query_Strings and not indexing pages with &lots=of¶meters=included. How true this is is questionable and to a degree these parameters are something we just can't avoid in Domino sites.