Interning, Week 1 & 2.

During the previous two weeks of my internship, I focused on analyzing the data import, migration, and mapping processes for 83 best-in-class and out-of-category headless content management systems. My sprint is to document the migration methods for various data types such as contacts, datasets, sections, templates, and pages, emphasizing code-free methods that enable seamless migration without deploying CLI or package management system software (e.g. npm, yarn).

Among the 83 competitors I evaluated, only eight offered a code-free built-in GUI system for importing .csv, .xml, and .json file formats. I also discovered that while there are code-free options for importing contacts via spreadsheets, there were no similar solutions available for templates, pages, or sections.

So far, the code-free cycle for importing and exporting data without utilizing the CLI or deploying yarn/npm looks more or less like the following across all eight platforms:

1. User exports (downloads) their data from the old CMS into the respective file format (.csv, .xml, .json)
2. User navigates to the new CMS platform dashboard and imports (uploads) their file(s)
3. User goes through data mapping process
4. User uploads newly formatted content compatible with the new CMS

Why this is important:

Only eight out of 83 platforms exist that provide user-friendly data import methods devoid of code and command-line interfaces because headless CMS solutions cater exclusively to backend developers.

☆ Their restricted accessibility, which disregards the broader non-technical user base, highlights their shortcomings and underscores the opportunities for our success. By creating a code-free data import and migration solution, we extend an invitation to users of all technical levels to benefit from our services.

How I gathered data:

In my sprint, my mentor provided me with a comprehensive list of enterprise-level headless CMS platforms to explore. I systematically reviewed all 83 of them by opening 5–10 tabs at a time and immediately delving into their documentation. I conducted keyword searches for terms such as “import,” “.csv,” “.xml,” and “migrate.” If at any point I encountered requirements involving yarn, npm, or CLI, I promptly moved on to the next platform.

Once I identified a platform aligning with our code-free criteria, I conducted a more in-depth investigation. This involved capturing screenshots, documenting step-by-step processes from videos, or seeking additional tutorials on YouTube. After confirming that the import process was devoid of code and didn’t necessitate registering for a demo, I proceeded to create a dummy account to thoroughly explore their dashboard.

What I learned:

• Some backend jargon. I can simplify the technical details related to data import and migration, specifically concerning CLI, yarn, and npm deployment, so that anyone, regardless of their technical background, can grasp the concepts
• The difference between a regular CMS and a headless CMS
• What data mapping is and what it looks like
• A more efficient method for collecting a substantial amount of data by capturing screenshots from both documentation and videos
• A better understanding of how database schema can be converted into a spreadsheet format that is unique to each CMS

Next steps:

• Card sorting