Consider vendoring the entire docsy template

[alamb]

While debugging #159 it was not obvious to me where the overall site templates were coming from. This may just be my own lack of experience with Hugo/Docsy but as we go and make more extensive modifications to the templates, I think it would help to make it clearer where the source comes from and how to change it

Also, I think reducing the amount of third-party content not under (our) source control, that is used to build the site would make it less likely we hit issues such as #159 (due to third-party library being updated)

Here is a PR with this this idea

• Vendor docsy template and add readme explaining how to overrides work #160

[vinooganesh]

Copying my comment here: Hey @alamb -

Docsy's docs actually recommend going with the hugo go module approach. I'm a little more concerned with vendoring docsy then I am about vendoring lunr and jquery mostly because docsy is a pretty active project. I can imagine upgrading eventually resulting in a huge number of diffs making the CR of actual content more difficult (also I've seen projects that vendor other large repos just decided to never update the dependency because over time it becomes a maintenance pain).

I think the biggest question is how flexible and customizable we want the website to be. I originally chose docsy as just a simple theme that we could pretty easily use/follow that "looked" like other projects (Iceberg was first and I mirrored their setup). If we want a lot more flexibility outside of what docsy provides then I think it's definitely something worth discussing.