Automattic / Automattic/cortext
Import content into Cortext
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 2
- Avg merge
- 3h 12m
- Merged PRs (30d)
- 8
Description
## Goal
Bring content from Notion into Cortext with as little cleanup as possible after the import.
## Scope
* Notion page imports, including hierarchy, common blocks, and page links.
* Notion database imports, including fields, views where feasible, rows, and relations.
* Import preview before committing changes.
* Import progress, failure reporting, deduplication, conflict handling, retry, and cleanup of failed batches.
## Out of scope
* Non-Notion importers until the Notion importer is working end to end.
* Export and portability, which should be tracked separately.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by mapping the existing import architecture and how Cortext could connect to Notion, then define an end-to-end plan covering pages, databases, preview, progress, failures, deduplication, conflicts, retries, and cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100