There's a fair amount of hype surrounding SVG. One of the much hyped points about SVG is that it's going to replace HTML any day now. So, I put together the example of a possible SVG webpage design above. It works but is seriously limited in what it can do because of the lack of UI widgets in SVG.
On top of that, bugs in Adobe's SVG viewer added to the problems I had in making it a working example. I wanted the "pages" to be in separate files so a (hypothetical) search engine could index it but Adobe's plugin has problems loading SVG images in SVG images.
The final version uses embedded svg documents instead of using separate files.
HTML is only one of many hypertext systems. It uses a box based layout engine to show images and text. The advantage of layout with SVG is clear with one look at the sweeping curves on this page. So, SVG has that in its favor. But, here are 5 reasons why SVG won't conquer HTML:
Could you create a website using SVG? Yes. Don't hold your breath waiting for SVG to replace HTML until the above problems are fixed.
SVG is a more than capable vector graphics format but improvements to the standard and to supporting technologies like search engines are needed to replace HTML. The necessary improvements would be:
The point of the ability to dynamically load and unload "frames" through a link is to allow search engines to easily make sense of a SVG document and offer relevant links to content in the document. Without search engine support no established site will use SVG over HTML.
Source code may be freely downloaded and examined. Please do not plagiarize.