So he starts with a JavaScript only application, then retrofits in a progressive enhancement layer in a Google-specified query string parameter.
He could just as easily done the core experience first with HTML, got a URL structure that is friendlier and RESTful, and then enhanced it with the JavaScript enhancement he needs to turn it into a perception of a one page website.
The bonus of doing it this way is clean URLs for each piece of indexable content.
Comments
So he starts with a JavaScript only application, then retrofits in a progressive enhancement layer in a Google-specified query string parameter.
He could just as easily done the core experience first with HTML, got a URL structure that is friendlier and RESTful, and then enhanced it with the JavaScript enhancement he needs to turn it into a perception of a one page website.
The bonus of doing it this way is clean URLs for each piece of indexable content.
Because, really, what's the advantage of http://example.com/?_escaped_fragment_=about-us over http://example.com/about-us ?