WeChat formatting: let the local engine handle layout
How Easy Post splits the work: layout, numbering and validation run in a local Rust engine, while ideas and final calls stay with you.
Formatting looks trivial and is not. Heading levels, numbering, quotes, line height, card styles, per-platform quirks — none of it is creative, all of it costs time, and one mistake makes the whole piece look careless.
Our position: deterministic work should not be handed to a model. Models are good at finding angles and rewriting tone. They are the wrong tool for deciding how big a level-three heading should be.
Four workbenches, four jobs
- Ideation — talk through angles and outlines with a model. Restart freely; drafts stay untouched.
- Materials — collect links, screenshots and excerpts in one place while you write.
- WeChat formatting — paste plain text, pick a theme, and a local Rust engine applies styles, numbering and structural checks.
- Social cards — turn one argument into shareable images, exported in batches.
The important difference is step 3: no network round trip, no tokens. The same text formatted today and next year looks identical.
A workflow that holds up
- Think first: three rounds of questioning until you can state, in one sentence, what the reader should do after reading.
- Write plain text only. Use
#for headings and-for lists; ignore styling while drafting. - Format once, publish everywhere: the same source text, re-themed per platform.
- Check structure before publishing. Machines are better than eyes at spotting broken numbering.
Offline capable
Layout, numbering and validation run locally. With a local Ollama model, even the creative features work without a network; cloud providers are optional.
Data follows the same rule — drafts, materials and API keys stay on your machine. That suits personal computers; avoid keeping credentials on shared accounts.
Try it from the Easy Post product page — Windows and macOS builds available.