Matt Hinchliffe

I've removed the milestone as the PR is currently blocked due to an issue in the plugin that's been implemented.

The simplest solution I can think of for splitting out shared styles would be to create separate entry points for the header and footer. However, we'd need to be careful...

> Could we make use of the SplitChunksPlugin webpack plugin for this? This is actually an important point I should have added to the original issue... the answer is no,...

> If we are able to split out styles for the header, footer and navigation then we'd be in a pretty good place. 💯 that would be a big win....

We're configured to deliver traffic over HTTP2 by default. The only browser which _should_ receive an enhanced experience over HTTP 1.1 is IE11 on Windows 7 and 8. We currently...

I've done a few experiments and I think something along these lines may strike a reasonable balance between performance, caching, and maintainability: - The Page Kit layout component provides separate...

I'm not sure if this is covered in the code but it really should be... The flags client has been designed to match the existing implementation in `n-ui`. This is...

My initial thoughts on this are that I would like where possible for UI components to not know anything about the request/response objects in order to be generic and reusable...

> Not having it would allow us to have a simpler architecture for navigation data. Yes! Adding types to it was a huge effort because the format was so haphazard....

As mentioned in #207 I think that if we're going to create sustainable components then it may be better to not couple them. > If we're going to encapsulate components...