A VS Code extension for writing and publishing blog posts with a WYSIWYG editor. Supports WordPress, Blogger, Medium, Ghost, and Substack platforms.
- WYSIWYG Editing: Rich text editor powered by TinyMCE with full formatting capabilities
- Multi-Platform Support: Publish to WordPress, Blogger, Medium, Ghost, and Substack
- Multiple Blogs: Configure and manage multiple blogs across different platforms
- Visual Blog Management: Intuitive webview interface for managing all blog connections
- Default Blog: Set a default blog for quick publishing
- Blog Selection: Choose which blog to publish to directly from the editor
- Metadata Management: Easy-to-use left panel for managing post details:
- Blog selection dropdown
- Post title
- Post status (Draft, Published, Pending Review, Private)
- Publish date/time
- Post excerpt
- Tags
- Categories
- Draft Management: Save and manage drafts locally
- Auto-save: Automatically saves your work every 30 seconds
- Secure Credentials: All passwords, tokens, and API keys stored securely
- Clean Interface: Focused writing environment within VS Code
- Install the extension from the VS Code marketplace (coming soon)
- Configure your blog credentials in VS Code settings
The easiest way to set up your blogs is using the built-in Blog Connections visual interface:
- Open Command Palette (
Ctrl+Shift+PorCmd+Shift+P) - Run: "Live Blog Writer: Manage Blog Connections"
- Click "+ Add Blog" button
- Fill in the form for your platform
- Optionally set credentials immediately or later
The visual interface provides:
- Card-based view of all your blogs
- Status indicators showing which blogs have credentials configured
- One-click default blog selection
- Direct authentication for Blogger OAuth
- Connection testing
- Easy credential management
- Requirements: Site URL, username, application password
- Command: "Live Blog Writer: Set WordPress Password"
- Note: Supports self-hosted and WordPress.com blogs
- Requirements: Blog ID
- Command: "Live Blog Writer: Authenticate with Blogger"
- Note: Requires Google authentication
- Requirements: Integration token
- Command: "Live Blog Writer: Set Medium Integration Token"
- Setup: Get token from https://medium.com/me/settings/security
- Requirements: Site URL, Admin API key
- Command: "Live Blog Writer: Set Ghost API Key"
- Setup: Generate key from Ghost Admin → Settings → Integrations
- Requirements: Hostname, email/password OR connect.sid cookie
- Command: "Live Blog Writer: Set Substack API Key"
- Setup: Use email/password (recommended) or get cookie from browser DevTools while logged into Substack
For detailed platform-specific setup instructions, see:
- Blog Connections UI Guide - Visual interface for managing blogs
- Multi-Blog Platform Guide
- Migration Guide (for existing users)
The old single-blog configuration still works but is deprecated. Please migrate to the new multi-blog system:
- Run: "Live Blog Writer: Manage Blog Configurations"
- Select: "Migrate Legacy Settings"
Old settings format:
{
"liveBlogWriter.platform": "wordpress",
"liveBlogWriter.wordpress.url": "https://example.com",
"liveBlogWriter.wordpress.username": "myusername"
}New settings format:
{
"liveBlogWriter.blogs": [
{
"name": "My Blog",
"platform": "wordpress",
"id": "https://example.com",
"username": "myusername"
}
],
"liveBlogWriter.defaultBlog": "My Blog"
}- Open the Command Palette (
Ctrl+Shift+PorCmd+Shift+Pon Mac) - Type "Live Blog Writer: New Blog Post" and press Enter
- The blog editor will open in a new panel
-
Left Panel - Post Details:
- Select Blog: Choose which blog to publish to from the dropdown
- Title: Enter your post title
- Status: Select the post status (Draft, Published, etc.)
- Publish Date: Optionally set a publish date/time
- Excerpt: Add an excerpt (brief summary)
- Tags: Add tags by typing and pressing Enter
- Categories: Add categories by typing and pressing Enter
-
Main Editor:
- Use the TinyMCE editor to write your content
- Format text using the toolbar (bold, italic, lists, etc.)
- Insert images, links, and other media
- Select your target blog from the "Selected Blog" dropdown (if not already selected)
- Click the "Save Draft" button to save your work locally
- Click the "Publish Post" button to publish to your selected blog
- If no blog is selected, you'll be prompted to choose one
- Or use the Command Palette: "Live Blog Writer: Publish Post"
The extension uses TinyMCE, providing:
- Text formatting (bold, italic, underline, etc.)
- Headings and paragraphs
- Lists (ordered and unordered)
- Links and images
- Code blocks
- Tables
- And more...
The left sidebar provides organized access to all post metadata:
- Title: Required field for your post title
- Status: Choose between Draft, Published, Pending Review, or Private
- Publish Date: Schedule posts for future publication
- Excerpt: Write a brief summary that appears in blog listings
- Tags: Add multiple tags (press Enter after each)
- Categories: Add multiple categories (press Enter after each)
Your work is automatically saved every 30 seconds, preventing data loss.
- VS Code 1.85.0 or higher
- Active internet connection for publishing
- WordPress site with REST API enabled, or Blogger account
- Tags and categories in WordPress currently use simplified handling
- Full tag/category ID mapping to be implemented in future versions
- Blogger combines tags and categories as "labels"
- Image uploads need to be handled separately (links to external images work)
Make sure you have set:
- WordPress URL (without trailing slash)
- WordPress username
- WordPress password using the "Live Blog Writer: Set WordPress Password" command
Run the command:
- Open Command Palette (
Ctrl+Shift+PorCmd+Shift+P) - Type "Live Blog Writer: Set WordPress Password"
- Enter your WordPress application password (not your regular password)
This means the extension's OAuth credentials are not properly set up. This typically only happens if you're building from source. For regular users, the extension includes built-in credentials.
For Developers: If you're building from source, see OAUTH_CREDENTIALS_SETUP.md for complete setup instructions including Azure Key Vault integration.
If you're using custom credentials:
- Verify the Blogger API v3 is enabled in your Google Cloud project
- Check that the redirect URI
http://localhost:54321/callbackis added correctly - Ensure you added yourself as a test user in the OAuth consent screen
See the Google OAuth Setup Guide for detailed instructions.
Make sure you have set:
- Blogger Blog ID in settings
- Run "Live Blog Writer: Authenticate with Blogger" to authenticate
Run the command:
- Open Command Palette (
Ctrl+Shift+PorCmd+Shift+P) - Type "Live Blog Writer: Authenticate with Blogger"
- Sign in with your Google account and grant permissions
- Check that your post status is set correctly
- For WordPress, ensure your user has permission to create posts
- For Blogger, verify your API key has the correct permissions
npm install
npm run compileNote for Production Builds: To include OAuth credentials in the packaged extension, see OAUTH_CREDENTIALS_SETUP.md for instructions on setting up Azure Key Vault integration.
- Open the project in VS Code
- Press F5 to start debugging
- A new VS Code window will open with the extension loaded
npm testdocs/OAUTH_CREDENTIALS_SETUP.md- Complete guide for OAuth credential management with Azure Key Vaultdocs/GOOGLE_OAUTH_SETUP.md- User-facing guide for setting up Google OAuthdocs/BLOGGER_OAUTH_SETUP.md- Technical documentation for Blogger OAuth implementationdocs/QUICKSTART.md- Quick start guide for new users.github/workflows/README.md- GitHub Actions CI/CD setup
Contributions are welcome! Please feel free to submit a Pull Request.
See LICENSE file for details.
- Multiple blog platform support (WordPress, Blogger, Medium, Ghost, Substack)
- Visual blog connection management interface
- Default blog selection
- Draft management (list and edit existing drafts)
- Support for featured images
- Direct image upload to blog platforms
- Support for custom post types
- Post scheduling
- Additional blog platform support (Dev.to, Hashnode, etc.)
- Markdown support alongside WYSIWYG
For issues, questions, or suggestions, please visit the GitHub repository.