Journal · guide
Writing for the Journal.
You tell the story, your AI agent writes it, the team reads it. No editor to learn: your agent fills a template with your words, and Pulsers draws the patches, racks and modules you cite itself.
Asking your agent
Your agent must first be connected to Pulsers. Then tell it what you want to talk about, and give it the material: what you did, why, what you heard.
“Write an article for the Pulsers Journal explaining my patch "Night pad". First suggest a template and a layout.”
Your patch
"Explain my patch 812, the one with Maths looping."
A module
"Review Plaits: what I like, what is missing."
Your rack
"Give a tour of my live rack, row by row."
A question
"Ask the members my question about syncing Pam's."
Choosing a template
The template sets what the article holds. It is also its section in the Journal. Your agent suggests one, and you can ask for another.
- Patch explained
- A public patch, and 2 to 8 sections on how it sounds and why. Tips, lists and videos on top.
- Module review
- A module from the catalogue, your sections, and at least one list: strong points, limits. Up to 3 patches to hear it.
- Tutorial
- Numbered steps, 2 to 15, each with a photo if you like. A "You need" list and patches on top.
- Rack tour
- A public rack, 2 to 8 sections to show it around, up to 4 patches played on it.
- Post
- The free format: up to 12 sections, 6 patches, 6 videos or sounds, modules and racks.
- Question
- A single text, and what it is about: a patch, a rack, modules. It opens a discussion.
Choosing a layout
Whatever the template, the article takes the site's width and keeps the text at reading width.
Column
The text on the left, what is cited beside it. For an article about one thing: a patch, a module.
Spread
A large title beside the first thing cited, then the sections side by side. For a short, visual article: a rack tour.
In the margin
Each heading in the margin, its text beside it. For a long article or a tutorial.
Pairs
Alternating chapters: a section beside what it shows. For an article that shows something for each idea.
Writing well
Your agent follows these rules. You can remind it of them.
- Your words
- The agent shapes what you say. It invents no setting, story or opinion you did not give.
- The title
- It says what the reader will learn or hear, in 100 characters at most.
- The standfirst
- Two or three sentences that make people want to read on, in 300 characters at most.
- One section, one idea
- A short heading, then the text. Four clear sections are better than a long one.
- Precise settings
- "CUTOFF at 11 o'clock, RES at a quarter", rather than "filter a little open".
- Show it
- Cite the patch, rack or module you talk about, right after the section that explains it. Pulsers draws it, playable.
- Tips
- What you wish you had known before. Three at most.
- Form
- Bold, italics, links and lists. ==A few words== between double equals signs are highlighted.
Photos, videos and sounds
- Photos
- In a tutorial, your agent keeps a place beside each step. You drop your photo or screenshot there on the preview page: JPEG, PNG or WebP, 10 MB at most. Your agent sends no file.
- Videos and sounds
- A public SoundCloud or YouTube link, played in the page.
- What is cited
- A patch, rack or module cited must be public: your readers must be able to open it. Publish a draft your agent made first.
Review and publication
- Private preview
- Your agent gives you a link: the article as it will appear, visible to you and the team only.
- Review
- The team publishes the article, asks for a change with its reason, or turns it down. Your agent reads the reason and sends the next version.
- Translation
- Write in your own language: the article is translated automatically for readers of the other one (French, English).
- After publication
- The article is frozen. To correct it, write to the team.
- Price
- Free, with no limit on numbers.