Contribute to Linelark
Linelark is small enough that one careful afternoon changes it. Pick the lane that fits the time you actually have — each one ends on something specific, not on a contact form.
See the three lanesBack an open roadmap item, or say in two sentences what is missing.
Votes are counted in public. Comments reach the same desk the roadmap is written at.30 minutesWalk a release checklist on your own machine, or answer a question one machine cannot answer.
A reproduction is worth more than a report, because it is the half that is hard.a weekendFork the example repository, or claim one of the small plugin ideas below.
A plugin is a folder, a manifest, and one JavaScript file. Reviewed releases go in the catalog.5 minutes · Shape it
These are the items the roadmap has open right now, published from the same diary the work is planned in. Voting is a click. Saying why takes a paragraph and counts for more.
needs a per-language fold-region model on top of the tokenizer
One vote per item, per network, each day. Enforcing that stores no address: only a one-way hash of the date, the item, and your network address mixed with a secret this site does not publish, deleted after thirty days. Your browser remembers what you backed so the buttons stay right. A second machine or tomorrow still counts again, so the total is direction, never a mandate.
30 minutes · Test it
Five checks against Studio 1.10.0, in the order most likely to find something. Work on copies. If a step behaves differently on your machine, that step is the whole report.
Not a defect list. These are things that depend on hardware, displays, and files nobody here has, so the honest position is a question rather than a claim.
A minified bundle on a single line is the hardest case in the editor, and the point where it stops being smooth depends on the machine and the display more than on the file.
Restore is exercised heavily with one window and lightly with two on different multi-root workspaces.
A file of a few dozen bytes carries little evidence of its encoding, and the useful threshold has never been measured against real files.
A weekend · Build it
No build step and no toolchain. Read the developer guide, copy an example, and install the folder directly. A reviewed release then goes in the catalog without waiting for an editor release.
Four examples written to be read and copied. Two are reviewed catalog releases; two stay small on purpose.
Start from the guideYour first pluginThe manifest, the host API, panels, previews, generated buffers, and the boundary of what a plugin may not do.
Ideas small enough to finish and useful enough to publish. Claiming one is a message, not a lock — two people building the same small plugin is a better problem than nobody building either.
Reformat the selection or the buffer, with an option to sort object keys. The failure case matters more than the success one: invalid JSON must report where it broke and change nothing.
Scan the open folder, list every marker in a side panel, and jump to one on click. Refresh on save rather than on a timer.
Draw the current CSV as a table in the right dock, using the preview API rather than a web view. Quoted fields and embedded newlines are the whole difficulty.
Keep a notes buffer tied to the current branch and swap it when the branch changes. Read-only git is enough, so the plugin asks for no permission at all.
What happens next
The failure this page is built against is silence. Here is the whole path, including the part where an answer is no.
Requests, reports, claims and testimonials all reach the same review desk, tagged with the item they came from and given a reference you can quote.
Every submission with an address on it gets a reply within two business days. That reply says what is happening to it, including when the answer is nothing.
A request that is taken up appears in the published roadmap; a reproduction appears in the release it fixes; a plugin appears in the catalog once reviewed. An idea that is turned down is turned down in writing.
Approved stories
Only testimonials cleared for publication appear here. Requests, reports, claims, and private feedback never do.
Loading approved stories…