README keeps the pitch and short abstract; outline, architecture, influences, audience, and submission kit move to docs/.
25 lines
1.7 KiB
Markdown
25 lines
1.7 KiB
Markdown
# CFP — `File > Protocol > App`: How a Note‑Taking Habit Became a Voice I Own
|
||
|
||
> A conference talk proposal by **Julien Calixte**. Working draft.
|
||
|
||
For years I was *the child in the room* — agreeing with everyone, able to counter no one. So I started taking notes, and slowly my voice counted. This is the story of how a 5‑year, 800‑note private garden became a public voice I own — **52 notes and counting**, published to the AT Protocol instead of a platform.
|
||
|
||
## Abstract
|
||
|
||
We all keep notes; far fewer publish them — because going public usually means renting your voice from a platform that owns your content, your identity, and your audience. I'll tell the story of turning a five‑year, 800‑note habit into a public blog I own, on the AT Protocol. The thesis is a hierarchy: **`File > Protocol > App`**. Your files outlive apps (Steph Ango); a protocol turns them into a *social filesystem* (Dan Abramov); the app is just a lens.
|
||
|
||
## Proposal
|
||
|
||
| Document | What's in it |
|
||
| --- | --- |
|
||
| [Abstract & titles](docs/abstract.md) | Title options and the long (detailed) abstract |
|
||
| [Outline & format](docs/outline.md) | Timed talk outline, lightning variant, A/V & logistics |
|
||
| [Architecture](docs/architecture.md) | The `File > Protocol > App` system diagram |
|
||
| [Themes & influences](docs/influences.md) | The ideas and people credited on stage |
|
||
| [Audience & takeaways](docs/audience.md) | Why now, who it's for, what they leave with |
|
||
| [Submission kit](docs/submission.md) | Speaker bio, supporting material, tailoring checklist |
|
||
|
||
---
|
||
|
||
*Built on `File > Protocol > App` — own your files, share them over a protocol, read them through any app. Self‑hosted on Coolify + Gitea, GitHub as a push mirror.*
|