With Vrite’s unique features like Kanban-based content management, the actual publishing flow is quite unique. All you have to do to publish a piece can be just drag and drop.
Dedicated Content Group
The recommended approach is to create a dedicated, ideally locked, content group for publishing, with an easily-identifiable name e.g. Published. You can then move any content piece that’s ready to be published, to this content group.
Publishing with Vrite Extensions
Vrite Extensions simplify the setup process you have to go through to publish your content pieces to popular platforms like Dev.to, Hashnode, or Medium. All you have to do is install the Extension and a custom Webhook handling auto-publishing will be added for you. Additionally, you’ll also be able to publish manually from the Extension’s Content Piece View. You can learn more about Vrite Extensions here.
Syncing with GitHub Repo
Instead of publishing through the API or to existing blogging platforms, you can choose to sync your content with a GitHub repo, and thus — your existing publishing workflows. This means you can use Vrite as a powerful WYSIWYG editor for your Markdown or MDX content (through the MDX extension). You can learn more about Vrite’s Git sync
Given that Vrite is in Public Beta, it’s constantly evolving and new content delivery methods, alongside more resources on how to implement them, are on the way. Below you can check out related articles from the Vrite blog:
- Better blogging on Dev.to with Vrite - headless CMS for technical content - a guide on implementing a custom Webhook for auto-publishing your content to the DEV platform, using Vrite API and Content Transformers.
- Start programming blog in minutes with Astro and Vrite - a guide on using Vrite’s dedicated Astro integration to build a static blog really fast;
- Notion-like Experience for Your GitHub Content — a guide to using syncing a GitHub repo with Vrite;