CSDN Draft Publisher
zhenbin_huang30 downloadsSync Markdown notes to CSDN blog drafts via a local Playwright bridge, with multi-account support, draft management, and write-back editing.
- Overview
- Scorecard
- Updates2
An Obsidian plugin that syncs the current Markdown note to a CSDN blog draft, and lets you manage existing drafts without leaving the vault.
What it does
Full usage documentation lives in the Wiki — including a 中文快速上手指南.
- Command palette: Sync current note to CSDN draft
- Ribbon icon menu: sync the current note, open the note in the CSDN editor, or open the draft manager
- Reads
title,description/summary,tags, andcover/imagefrom YAML frontmatter - Draft manager panel: browse drafts of the active account, search by title, paginate, open a draft in the CSDN editor for write-back editing, and delete drafts with confirmation
- Multi-account support: each account gets an isolated Playwright browser profile
- Automation only looks for the "save draft" button; it never touches the publish button
- Local image references are detected and reported; images are not uploaded automatically
How it works
The plugin ships a small Python bridge script (csdn_bridge.py, also embedded in main.js and released to the plugin folder on first run). When enabled, the plugin starts this script with the Python interpreter configured in the settings, and talks to it over local HTTP at http://127.0.0.1:8765. The bridge drives a Playwright Chromium browser to fill the CSDN Markdown editor and save drafts.
Privacy and data disclosure
- No telemetry. The plugin collects nothing and reports nothing.
- No credentials stored. The plugin never asks for or saves your CSDN username or password. Login happens once in a real browser window, and the session lives in a local Chromium profile under
%LOCALAPPDATA%\CSDN-Draft-Publisher\. - Network use. The bridge listens on
127.0.0.1only and never sends your notes anywhere except to CSDN itself when saving a draft. Draft sync requires internet access to csdn.net. - Account required. A CSDN account (and a one-time manual login per account profile) is required for the plugin to be useful.
- Files outside the vault. The plugin spawns a local Python process, writes
csdn_bridge.pyinto its own plugin folder, and Playwright keeps browser login profiles under%LOCALAPPDATA%\CSDN-Draft-Publisher\. None of your vault notes are copied outside the vault.
Setup
Install and enable the plugin.
Install Python 3.11+ and the bridge dependencies:
pip install playwright==1.62.0 python -m playwright install chromiumA conda environment works as well (
environment.ymlis provided).Open the plugin settings and make sure Python command points to a Python that has Playwright installed (
pythonby default, or a full path such as a conda env interpreter).Turn on Enable bridge service. The plugin starts the local bridge automatically.
Run Sync current note to CSDN draft. On first run a browser window opens — log in to CSDN manually once; the session is reused afterwards.
Settings
| Setting | Description |
|---|---|
| Bridge URL | Local bridge address, default http://127.0.0.1:8765 |
| Enable bridge service | Starts the Python bridge with the configured interpreter; disabling only stops a bridge the plugin itself started |
| Python command | Python interpreter used to launch the bridge |
| CSDN accounts | Add, rename, log in, and clear login state per account; each account has its own browser profile |
If port 8765 is already served by a manually started bridge, the plugin reuses it and will not stop it when the toggle goes off.
Recommended frontmatter
---
title: My article title
description: One-sentence summary
tags:
- Python
- Obsidian
cover: https://example.com/cover.png
---
Development
The repository root doubles as the plugin folder:
main.js— plugin source (plain JavaScript, no build step). It embeds a base64 copy of the bridge script and writes it next to itself on first run.csdn_bridge.py— the Python bridge (source of truth for the embedded copy; regenerate the base64 constant when you change it).manifest.json,versions.json— plugin metadata for the Obsidian community directory.
Install a dev copy by symlinking or copying this folder to <vault>/.obsidian/plugins/csdn-draft-publisher/ and reloading Obsidian.
Contributing
See CONTRIBUTING.md for the local check commands, branch and commit conventions, and how releases are cut (RELEASE-CHECKLIST.md). Bug reports and feature requests use the issue templates; security issues go through SECURITY.md.