Documents vs tables

Pick one

Make a document when…	Make a table when…
You're writing a draft, script, or note	You have many of the same thing: posts, hooks, tasks
Order of paragraphs matters	You want columns like status, date, or platform
There's one thing here	You want to ask "which ones are done?"
You want it to become a post later	You want it as a list, kanban board, or calendar

Not sure? Start with a document. It's the cheaper mistake. When it grows a repeated pattern, turn that part into a table.

Use them together

1. Make a table for your pipeline, like a content calendar.
2. Hover a row's name and click @.
3. Pick New document from this row. Eden makes a document with the row's name, links them, and opens it.

Now the row tracks the piece and the document holds the writing. Rename the document and the row follows.

To add something you already saved as a row, open the chevron next to Add item and pick Add from library.

Ask chat to build a table

Describe what you want to track and chat builds the columns and rows:

• "Build me a hook bank with tier, pillar, and status."
• "Make a content calendar with status, platform, and publish date."
• "Pull these posts out of my note into a table." This swaps the list for a live table and keeps your writing.

Ask for a table and you get a table. If chat also worked out a strategy, it asks at the end if you want a doc with the table inside. If your ask was a plan, like "plan my content season and give me the calendar," it may go straight to a doc and tells you first.

What goes in the Name column

The Name column holds the thing itself: the hook, the idea, the essay title. It's also the item's title in your Library and in search, so it has to make sense on its own.

If a value counts up or repeats across rows, it's a column, not a name.

Wrong: Name	Week	Essay title
Week 1	1	The Second Renaissance
Week 2	2	Why taste is the new moat

Right: Name	Week
The Second Renaissance	1
Why taste is the new moat	2

Need a longer version too? Give it its own column, like Script or Full text.

Edit part of a document with chat

Attach the document to chat and name the part to change: "Tighten the opening paragraph." Chat edits just that part and leaves the rest alone. Earlier text stays in version history.

Common setups

Setup	Use
Content calendar	Table with status, platform, and publish date. Each row opens a draft.
Hook bank	Table named by hook, with a select column for the angle
Client work	Table with a client column. Rows link to briefs and drafts.
Meeting notes	One document per meeting
Research for a piece	Document, with sources connected to it
Reading list	Table filled with Add from library, so you can check items off