👀 Investigate - Move to TinaCMS

[JackDevAU]

CC @bradystroud @adamcogan @wicksipedia

Hi Team,

We are looking to move from DecapCMS to TinaCMS but, we need to investigate if we can move with Gatsby or if it will be less work to start fresh with Next.js.

Tasks

• [x] Investigate how we can manage images
• [x] Investigate and list all components that are needed to migrate
• [ ] Investigate and estimate effort required to move to TinaCMS with current implementation (Gatsby)
• [ ] Investigate and estimate effort required to move to TinaCMS with Next.js
• [ ] Writeup a recommendation and get the Product Owners Approval (Make a Done Video?)
• [ ] Create PBIs

[Aibono1225]

Update 03/06/2024:

Investigate how we can manage images

Based on Tina's doc, I've set up a separate content repo to test image handling functionality. The results show that images stored in a public folder within a separate repo can be successfully managed by TinaCMS.

Therefore, to move to Tina, we might need to run a script to:

• Move all images from the rules folder to a public folder (e.g., assets)
• For each rules subfolder, create a corresponding subfolder within the public folder. This will make it easier for users to locate and modify images

Also, we might consider adding a feature to TinaCMS that automatically updates the images folder name when a rule folder name is changed.

[Aibono1225]

Additionally, the current implementation of Rules use gatsby-remark-custom-blocks and gatsby-remark-fenced-divs to generate styled blocks such as email templates and good/bad examples.

Once we move to TinaCMS, we will need to handle these block manually, which means transforming all .md files to .mdx to use custom components.

[JackDevAU]

Update:

Investigate and list all components that are needed to migrate

We have 9 components that are used and 1 that I don't think needs to be migrated.

To migrate:

• Aside
  • Warning
  • Info
  • Todo
  • China
  • Codeauditor
  • Highlight
• Email
• GoodBad
  • Good
  • Bad
  • Ok
• Greybox
• Image
• Table
• Twitter
• Youtube

We will also need to migrate the Frontmatter as the current fields can be improved now that we know what we need.

Shouldn't be migrated:

• Hidden
  • This was used to show/hide certain content based on if the user was in our GitHub org or not