✨ 💡 Core Activity

Migrate an existing website to TinaCMS to improve content editing capabilities and developer workflow. This includes converting all content from Markdown to MDX and ensuring platform compatibility.

🔬 Experiment
We are experimenting with two key areas:

1. Content Migration:

• Assess the feasibility of converting existing Markdown (.md) content to MDX (.mdx) while preserving formatting, embedded components, and frontmatter metadata.
• Investigate automated tools or scripts that can assist in bulk conversion and test compatibility within TinaCMS.

2. Hosting Environment:

• Develop a Proof of Concept (POC) to evaluate the TinaCMS-powered site on Azure Web App x Docker Container vs Vercel.
• Compare performance, integration support, build pipelines, and feature parity (e.g., preview mode, environment variables, API routes).
  Success will be determined by whether the site retains its current functionality post-migration and integrates smoothly into the CMS and chosen platform.

🛠 Supporting Activity

• Setup of a test repository and branch to isolate and track content migration efforts.
• Documentation of migration tooling, errors, and edge cases encountered during MD → MDX transformation.
• Deployment of two POCs: one on Azure, and one on Vercel, for side-by-side comparison.
• Team review of editing experience in TinaCMS using MDX content.
• Capture learnings for future migrations of similar websites.

No source files or tests are named. Start by reviewing the existing Markdown content, frontmatter, and the test repository or branch described in the issue, then compare the Azure Web App with Docker Container and Vercel POCs. Done means content preserves its formatting and metadata, current functionality remains intact, TinaCMS editing works, and the hosting comparison is documented.