Look into evaluating how we can make building the site take less memory / cpu.

Problem

As k/website has grown, it went from a small hugo build to what it is today (a large, memory and file hungry build).

This is all good though, it means we are adding content and localizations.

Solution

Look into ways to reduce build time. A few options come to mind:

• Can we remove a large chunk of unused content?
• Can we build only a small subset of docs (easily and portable to the various localizations)?
• Are there any optimizations in hugo itself?

There should be a way to reduce the amount of resources required to build k/website. Considering there isn't a clear solution, I won't mark as good-first-issue.

/sig docs
/triage accepted