13 · Shell and backslashes
npm run dev
# A multiline command
node ./scripts/example.mjs \
--message "hello world" \
--path "C:\notes\fragments"
Brief thoughts, kept along the way.
npm run dev
# A multiline command
node ./scripts/example.mjs \
--message "hello world" \
--path "C:\notes\fragments"
0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
const signal01 = 'packet-1';
const signal02 = 'packet-2';
const signal03 = 'packet-3';
const signal04 = 'packet-4';
const signal05 = 'packet-5';
const signal06 = 'packet-6';
const signal07 = 'packet-7';
const signal08 = 'packet-8';
const signal09 = 'packet-9';
const signal10 = 'packet-10';
const signal11 = 'packet-11';
const signal12 = 'packet-12';
const signal13 = 'packet-13';
const signal14 = 'packet-14';
const signal15 = 'packet-15';
const signal16 = 'packet-16';
const signal17 = 'packet-17';
const signal18 = 'packet-18';
const signal19 = 'packet-19';
const signal20 = 'packet-20';
const signal21 = 'packet-21';
const signal22 = 'packet-22';
const signal23 = 'packet-23';
const signal24 = 'packet-24';
const signal25 = 'packet-25';
const signal26 = 'packet-26';
const signal27 = 'packet-27';
const signal28 = 'packet-28';
<script>
console.log('literal text only');
</script>
<div data-value="a & b"><content></div>
<!-- This stays code, never an active page element. -->
Hello, Matrix. 你好,世界。日本語のメモ。한국어 메모。
👩🏽💻 🧑🚀 🌧️ 🐇 é café — excerpts should preserve Unicode code points.
A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀 A quiet signal 😀
matrix://fragment/signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-signal-without-a-break-
Keep the thought. Some ideas need quiet time to grow.
Another quoted paragraph with a project link.
A softer aside and one point to remember.
A normal paragraph follows the list.
| Item | State | Notes |
|---|---|---|
| Image | Ready | Local asset |
| Code | Ready | Indentation |
| Link | Ready | Full fragment |
A long title with a short body. It should wrap rather than widen the panel.
🌱
This note shares the previous note’s timestamp but has a different stable ID. Ordering should stay deterministic and both share links should remain reachable across pages.
A small question for today: do you prefer writing complete articles, or collecting short notes first?
This is a comment demo fragment. Open its comments to explore switching between short and long entries.
A wrapping example for narrow screens:
a-small-but-very-long-fragment-identifier-to-check-how-inline-code-wraps-on-a-narrow-mobile-screen-without-overflow
A long token should still fit the reading area.
Some sentences want a heading. Others can stand on their own.
This demo keeps a small heading to explore how it reads in the feed.
It is late.
Leave the cursor here.
Continue tomorrow.
🌙
Small details that fit in a fragment: a point of emphasis, a softer voice, and an inline marker small-notes/2026-11-11.
Formatting helps the reader. The sentence still carries the thought.
This longer demo fragment explores the rhythm of several paragraphs.
Sometimes the difficult part is knowing where to stop. Writing can work the same way: removing a sentence occasionally makes the original thought clearer.
An unfinished idea does not always need a conclusion. Leave a little space and come back tomorrow. Small notes let us observe without pretending that every question has already been answered.
For now: keep looking, and stay patient.
A starting point for the next thought:
User Guide 5: Publish Fragments
A record can be a few words or a link worth returning to.
A tiny snippet can be a fragment too:
const thought = {
id: 'keep-a-small-signal',
text: 'Keep going, quietly.',
};
Keep the thought; find the perfect words later.