A little more detail, to avoid overloading the parent comment: Currently making html/css changes on the site is a little bit painful, because they're the kind

A little more detail, to avoid overloading the parent comment: Currently making html/css changes on the site is a little bit painful, because they're the kind of thing that you often want to make small tweaks to until it looks right, and yesod is fond of rebuilding lots of stuff on each change. To continue making forward progress while we've been short haskell devs, the design folks have been iterating on a prototype using a static site generator. Several of the new designs are static pages, so in theory it should be a mostly cut-and-paste job to move them to the real site. However, the css "framework" (ie, sass mixins) of the two have diverged a bit. So, there's a number or ways in which progress could be made. In order from most long-term impact to fastest immediate progress: - Haskell-side improvements to make the site build faster, so the designers could work directly on it for static content. - Getting the site and prototype css back in sync, so that static pages can just be dropped in. - Migrating individual pages from the prototype to use the main site css instead. If you're interested in other aspects, there's governance, legal, and a few other miscellaneous tasks, too.