Edited 2m ago

This page is in Trash.

Getting started

Welcome to Folio - a home for your notes, docs and projects. Click anywhere and start typing.

The basics

Click anywhere and just start typing

Hit / to see all the kinds of blocks you can add - headings, lists, toggles, callouts, code

Select any text and use the menu that pops up to style it

Drag the handle on the left of a block to move it

Type #, -, [] or > and a space for a heading, a bullet, a to-do or a quote

Add a page with the pen button at the top of the sidebar

Want to know more? Open this toggle

Toggles keep details out of the way until you need them. Press ⌘K to jump between pages, or open 🗺️Product Roadmap for a database with table, board and gallery views.

Everything stays in the page: press Enter for a new block, Backspace on an empty one to remove it.

Every page here is plain HTML - the whole app is one source you can read on the docs page.

Keyboard

⌘K search and jump to any page

/ insert any kind of block

⌘B ⌘I bold and italic, or use the floating menu

Edited yesterday

This page is in Trash.

Engineering Wiki

How we build, review and ship. Start with the pages below, and add what you wish you had known on day one.

Start here

🚀Onboarding - your first week, accounts and the local setup

🔍Code review guidelines - what we look for and how we leave comments

Principles

Prefer the platform: if the browser can do it, we don't ship code for it

Small pull requests, reviewed within a day

Every change is verified - green checks or it doesn't merge

Make it work, make it right, make it fast - in that order.

Edited 3 days ago

This page is in Trash.

Onboarding

Welcome aboard! This page gets you from a fresh laptop to your first merged change.

Week one

Meet your onboarding buddy

Set up the development environment

Ship a small fix to production

Local setup

git clone git@example.com:folio/app.git cd app bun install bun dev

Stuck for more than 30 minutes? Ask in #help - nobody expects you to know everything yet.

Edited last week

This page is in Trash.

Code review guidelines

Reviews are a conversation, not a gate. Be kind, be specific, and say what would make you approve.

What we look for

Does it do what the description says?

Is it covered by a test that would fail without it?

Would the next person understand it without you?

Prefix nits with "nit:" - the author may ignore them.

How fast should I review?

Within one working day. If you can't, say so and suggest someone who can.

Edited 5m ago

This page is in Trash.

Product Roadmap

What we are building this quarter. Switch views, drag cards between columns, or open an item to edit it.

Table Board Gallery

Owner	Tags	Due
Marco Rossi	EditorSync	Oct 18, 2026
Priya Natarajan	Sync	Nov 2, 2026
Anna Silva	API	Nov 20, 2026
Sophie Tan	Editor	Sep 26, 2026
Aron Homberg	Mobile	Dec 4, 2026
Marco Rossi	AIEditor	Dec 15, 2026
Aron Homberg	Editor	Sep 19, 2026