[nopal]

I'm very eager to see how they handle the actual exchange code.

Jekyll and static HTML make a lot of sense for a marketing/informational site (which this appears to be right now), but at some point, they're going to need a dynamic backend (right?). These exchanges will need to aggregate plan info from lots of different insurance carriers and display plans to people based on various bits of user-specific info. Perhaps they can generate static info pages for all of the plans and redirect people to these pages via JavaScript and then pass the actual enrollment off to the insurance companies.

If they have to support enrollment and dynamic content, it will be interesting to see how they do so while adhering to their principles of simplicity.

If they don't, it will be an interesting example of how to embrace simple solutions where possible while preventing scope creep.

Either way, I'm glad to see this type of innovative development happening.

[herge]

One "website" can have multiple backends: static files prepared with Jekyl for the CMS part of it, and a full backend for any dynamic bits. You can feed both in the same page with judicious use of AJAX.

[nopal]

Of course. And if they do implement such a JavaScript-dependant approach, it will be entirely different from any other government site. As I said, I look forward to seeing how they progress.

[digiphile]

So am I -- and a lot of other folks who cover tech & public policy!