Documents, Whiteboards, Spreadsheets, and Databases in One Knowledge Hub
Learn how infolio brings writing, visual thinking, data tracking, and structured project material into one local-first workflow.
Quick answer
When a project needs writing, mapping, tracking, and relationships, switching tools spends attention. infolio gives four content modes a shared home.
Choose the surface that matches the thought
Documents make decisions and long-form material clear. Whiteboards make relationships visible. Spreadsheets expose plans and changing numbers. Databases organize objects, status, filters, and connections. These modes often serve the same project, yet they are usually split across disconnected tools.
infolio brings them back to one personal knowledge hub. You do not need to decide whether something is “just a note”; choose the surface that helps you express and move the work forward now.
- Use documents for decisions, explanations, and durable material.
- Use whiteboards for paths, relationships, and unresolved thinking.
- Use spreadsheets for time, budget, planning, and numeric tracking.
- Use databases for objects, status, tags, filters, and connections.
Let one project move naturally between four views
For a content project, start by mapping topics and audience on a whiteboard, then write the direction as a brief. Keep schedule and budget in a spreadsheet, and use a database for assets, status, and ownership. The work stays in one space, so search, organization, and sync do not need to be configured again.
The goal is not to make every page look the same. It is to make each one discoverable through the same workspace, folders, and cross-device workflow, so context does not disappear when the mode changes.
Start light instead of building a system on day one
You do not need a complicated database on the first day. Start with a project document and a whiteboard. Add a table when repeated status, filtering, or changing plans make one useful. Structure should grow from real work instead of creating a maintenance burden upfront.
That gradual approach keeps the roles clear: documents preserve narrative, whiteboards preserve exploration, spreadsheets preserve rhythm, and databases preserve structure.
FAQ
When should I use a spreadsheet versus a database?
Spreadsheets fit continuous data, calculations, and time series. Databases fit attributes, states, filters, and connections among many objects. Start with the simplest useful view.
Do whiteboards become separated from documents?
No. Whiteboards and documents live in the same knowledge-base structure, so they can be organized, searched, and synced around the same project.