Features
- Admin initialization, login, password modification
- Cloudflare KV persistent configuration and site information
- Multi-site management and switching
- Site notes
- Site connection testing
- Markdown article list, creation, editing, deletion
- Local draft saving
- Draft list display
- Draft status distinction (not published)
- Published article status distinction (published)
- Image list management
- Image upload
- Multi-image batch upload
- Image deletion
- Batch image deletion
- Image link copying
- Copy all image links
- Markdown editor real-time editing and preview
- Mobile editing / preview switching
- Drag-and-drop image upload
- Paste image upload
- Insert images into articles from gallery
- Local reactive list data caching
- Responsive layout
Features (Compared to HexoPlusPlus)
Staexoctor is not a simple clone of HexoPlusPlus, but rather a lightweight, multi-site, server-hosted blog management backend centered around Cloudflare Workers + GitHub Repo.
1. Better Suited for Cloudflare Workers Architecture
HexoPlusPlus leans more towards traditional Node.js / server-side environment approaches, while Staexoctor is designed from the ground up around:
- Cloudflare Workers
- Cloudflare KV
- GitHub API
Therefore, it is more suitable for deployment in edge environments.
2. No Need to Build Traditional Server Backend
All server-side operations in Staexoctor are handled by Workers, including:
- Site addition
- Configuration saving
- Article reading and writing
- Image upload
- File deletion
- Connection testing
No additional database or traditional backend services are required.
3. Better Suited for Unified Multi-site Management
Staexoctor natively supports:
- Multi-site configuration
- Multi-site switching
- Independent blog repository and image repository for each site
- Site notes
- Site connection testing
This makes it more suitable for uniformly managing multiple static blog sites, rather than just a single-site blog backend.
4. More Granular GitHub Repository Configuration
Each site can independently configure:
- Blog repository Owner / Name / Branch / Token
- Image repository Owner / Name / Branch / Token
- Markdown directory
- Image directory
Compared to some more rigid blog management tools, Staexoctor offers greater flexibility in repository structure adaptation.
5. More Modern Image Workflow
Staexoctor has made relatively comprehensive enhancements to image handling, supporting:
- Click upload
- Drag-and-drop upload
- Paste upload
- Multi-image batch upload
- Insert from gallery
- Insert at current cursor position
- Default return of JSDmirror CDN links
The writing experience is closer to modern content backends, rather than just simple file uploads.
6. Separation of Draft and Published Content Status
Staexoctor supports local draft management and distinguishes articles into:
- Drafts (not published)
- Published articles (published)
This makes the creative process clearer and is more suitable for scenarios where you need to save work in progress.
7. Greater Focus on Responsive Design and Mobile Experience
The project has been specifically optimized for both desktop and mobile devices, including:
- Responsive layout
- Mobile menu
- Mobile editing / preview switching
- Editor toolbar scrolling
- Small screen button layout optimization
This makes it more suitable for light content management on phones or tablets compared to some desktop-only backends.
8. More Unified Global State and Request Control
Staexoctor emphasizes greater consistency in frontend structure:
- All network requests go through the same request file
- List data uses reactive state caching to reduce duplicate requests
Therefore, it is clearer in interaction consistency and code structure.
If you want to develop it into a more complete static blog management platform, Staexoctor's current architecture will make it easier to continue evolving.