Nectar Allocation Visualisation and Project Pages

Not all requested changes in, but it looks good enough.

The download times for the service components are well within acceptable limits, even allowing for potential future expansion. Making changes to "improve" performance will likely not be worth the effort and represent an example of the "premature optimisation" anti-pattern.

We may be able to get some improvement in download performance without code changes,  just by configuring compression for the payload, but its not needed at this point in time. 

I would like to suggest that the "growth" graph does need to have its performance issues addressed first.