feat: London Gophers Redesign Using Blowfish Theme

[jaminologist]

This is a redesign of the gophers.london website using the Blowfish Theme

Here are the main layout/word changes on each page

Home Page

• Moved a lot of the text to separate pages with their own.
• Added a link to the next 3 meetups

Code of Conduct

• New Page, uses the same wording as it was orginally
• Added text from our conduct slides
• Added wording around how we enforce our conduct

Speaking

• New Page, uses the /apply address
• Uses most of the same text from our new 2022 speaker slides
• Has link to our speak form. (May be better to embed it?)
• Add video link to "It's Not All Talk"

Sponsors

• New page, uses the same text as before at the beginning
• Added 'Venue Sponsors' the idea being to highlight the past 4-6? venues we've been hosted at. Links directly to the host's website using the images.
• Added small Q&A about monetary sponsors and raffle sponsors.

For this PR I would highly recommend downloading the code changes and having a look around. I've updated the Readme as it requires slightly different steps to run than the original site. There have been many code changes and versions in Hugo since our original site was created. So, the original instructions do not appear to work with newer themes. Additionally, with some fiddling I still couldn't get the old way to work as easily as the new way in the Readme, however I would like to know if the 'new way' is easy for other people to use as well on different setups.

Below are pictures of the pages. Note: the background images follow when you scroll, but when using 'full-size screenshot' that can not be accounted for hence the voids of blue present in the longer pages.

Looking forward to hearing your feedback and have a happy holiday!

Home Page

Code of Conduct

Organisers

Speaking

Sponsors

[jaminologist]

Answering questions:

1. No idea, it may exist somewhere in the original hugo 'figure' shortcode or we may need to do more custom things. In the making of the PR I tried to use essentially "0" custom changes (except for the main menu custom html) to reduce the amount of extra knowledge needed to make changes in future. But we don't have to stick to this paradigm

2. I don't think it can deploy in master without changing the deploy script tbh. I forgot about that part. But adding things on top is cool, there isn't a rush to release the PR.

3. I included everyone so far because it was a new idea, but I'm tempted to say last 3? (So, 3 months). That seems more mangeable than the 6 that are there now.