SSWConsulting / SSWConsulting/SSW.Rules
Netlify CMS - Investigate updating Slate editor
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
@pierssinclairssw @adamcogan @bradystroud
Hi,
As per my conversation with @pierssinclairssw @adamcogan, there are numerous issues with Netlify CMS that seem to be linked to the Slate rich text editor, which needs to be migrated to the latest version.
- Investigate what issues can be resolved by updating Slate
- Investigate what new features are available with new versions of Slate that would be good to implement in Netlify CMS
- Determine whether it is worthwhile updating Slate to the latest version
- Create a video showing the pros and cons of updating, comparing old vs new version
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Netlify CMS integration and its Slate dependency, then compare the current Slate version with the latest version. Investigate which reported issues and useful features are affected, and document the pros and cons in the requested old-versus-new video. Done means there is enough evidence to decide whether the migration is worthwhile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100