SSWConsulting / SSW.Dory

SSW.Dory - Sharepoint and GitHub
http://sswdory.com
1 stars 0 forks source link

♻️ Refactor Landing-Page Website Architecture #63

Closed Jord-Gui closed 1 year ago

Jord-Gui commented 1 year ago

Cc: @bradystroud @adamcogan @JackDevAU @leahy268

Pain

The SSW.Dory landing-page website currently uses a Jekyll template hosted in GitHub Pages, which was a quick way to get content up but is too restrictive. We want to update the website to have a custom design.

Potential solutions

  1. WordPress (may not be worth the cost for a project site)
  2. Gatsby + GitHub Pages (Gatsby not SSW recommended solution, but has documentation on how to deploy to GitHub Pages)
  3. NextJS (more work involved to get it deployed and may be overkill for this. Wouldn't be an issue if we hosted on Vercel)

As this is a complete re-architect, we can also trial out Bun 1.0 https://bun.sh/blog/bun-v1.0

### Tasks
- [x] Confirm cost of hosting on WordPress
- [x] Write down Pros and Cons on Gatsby and NextJS
- [x] Get solution approved by Product Owner
Jord-Gui commented 1 year ago

Wordpress has limited sites. Around $6K a year for 10 sites. We already have 27. Initial discussion was that it's not worth taking up the remaining 3 slots for a static single page website.

JackDevAU commented 1 year ago

Maybe try out Astro 👀https://astro.build/

GitHub Pages: https://docs.astro.build/en/guides/deploy/github/

Jord-Gui commented 1 year ago

https://www.ssw.com.au/rules/best-static-site-tech-stack/

Jord-Gui commented 1 year ago

Cc: @adamcogan @samsmithssw @bradystroud As discussed with @adamcogan, we will be going with Option B

Option A: WordPress https://wordpress.com/

Options B: NextJS https://nextjs.org/ (recommended)

Option C: Astro https://astro.build/

~Gatsby https://www.gatsbyjs.com/

SSW Rule: https://www.ssw.com.au/rules/best-static-site-tech-stack/

Image Figure: Google Trends comparing NextJS, Gatsby, Wordpress and Astro. Note: Astro may refer to other things

Jord-Gui commented 1 year ago

Done - as per discussion, will refactor to NextJS. This is tracked in Issue #64