As someone who uses Dev.to as a headless CMS, I feel a lot of personal pain points with the very simple default editor we get in Dev.to. I figured I would try a personal project with all new tech that I know some things about but haven't built anything serious with:
- Preact
- Next.js
- TailwindCSS
And done in TypeScript because that's how I roll.
Source: https://github.com/sw-yx/dev-to-cms
Demo: https://dev-to-cms.now.sh
Here is my first livestream of that! Had a slow start but got a lot done in 90 minutes.
Dev.To embed:
Catch up on the Dev.to CMS LiveStream!
- Day 1 - Setup Next.js and Tailwind UI, list posts through API routes - 90 mins
- Day 2 - setting up a Markdown Editor with Next.js, Tailwind UI, Highlight.js, React Hook Form, and React Query - 3 hours
- Quick Fix - How To Add Monaco Editor to a Next.js app - 18 mins
- Day 3 - Refactoring to Edit Existing Posts - 3 hours
- Day 4 - Polish Day! Implementing Notifications, Markdown preview, and programmatic Redirects, and Using Web Components in Next.js - 3 hours
- Instant GraphQL with OneGraph - Screenshares in Public with Sean Grove - refactoring handrolled Dev.to API access with OneGraph and GraphQL
- How and Why to Un-Reset Tailwind's CSS Reset
Latest comments (3)
The biggest issue I have is that gammerly does not work in the editor. Forestry.io editor does allow it to work, no clue how.
Wonder if your editor will be recognized my grammerly. It’s a good idea to role your own. Nice work!
yes! once i have my own i can add grammarly, hemingway, or whatever else I want. For example i want to @ people in my markdown, and have it autopopulate into a link to the person's twitter or site or whatever.
Huh. I haven't had problems with Grammarly in the dev.to editor (at least in Firefox). If you really can't get it to work, open an issue so the team knows you're experiencing a bug.