Sign in

Pages

What you know sits under the work it concerns

A page in Kalends hangs under the area, directive, project, goal or commitment it is about. The description you have already written is the page, and the subpages sit beneath it. No separate tree to keep in order, because Kalends already has one.

Try KalendsWho may read
Kalends · Pages
ProjectsWithout pages
  • AreaFinance
  • Year-end routineW-12
  • Checklist before the close
  • Approval limits
  • CommitmentVAT return
  • How we file the VAT return

Every page has an address of its own: /acme/W-12.

  • One structure, not another one
  • Markdown you can take with you
  • Written by several at once
  • Every version is kept

Two trees drifting apart

The plan is in one system.What you know is in another.

The routine for the year-end close is in Confluence, the decision about the supplier in Notion and the template in a Word file on OneDrive. Each has a tree of its own, so the organisation keeps two structures that drift apart. After a year the question is no longer what the rule is, but which of the pages is the current one.

Moving to an all-in-one tool only takes the problem inside: there every team gets a workspace of its own and every need its own database. Kalends has one structure, the areas somebody answers for, and the pages hang on it.

In Kalends

How the pages work

The page hangs under the work, Kalends is alive in the text, you write together and the format is open.

1Under what it concerns

The page hangs under what it describes

Areas, directives, projects, goals and commitments take pages directly beneath them, and subpages beneath the pages. The description is the page and carries the name of the thing it belongs to, so renaming an area renames the page with it. A page with subpages works as a folder, and every page has an address of its own to pass on.

  • Pages under areas, directives, projects, goals and commitments
  • The description is the page, under the same name
  • An address of its own per page, W-12
Kalends · Pages
ProjectsWithout pages
  • AreaFinance
  • Year-end routineW-12
  • Checklist before the close
  • Approval limits
  • CommitmentVAT return
  • How we file the VAT return

Every page has an address of its own: /acme/W-12.

2Kalends in the text

Kalends is alive in the text

Type WEB-42 and the task becomes a card with its title, status, owner and date, which you tick off where it stands. A KPI, a commitment or a goal becomes a card the same way. A task list in the page shows the real tasks, filtered by what the reader may see. The tasks still live in projects and goals, never in the page.

  • WEB-42 becomes a card you can tick off
  • Task lists filtered by the reader
  • Turn a page into tasks with Ask Kalends
Kalends · W-12 Year-end routine

Year-end routine

The books close on the fifth banking day. The reconciliations are due before that:

WEB-42Reconcile accounts payableIn progress · 5 NovAS
Tasksproject: WEB · status: open
  • Reconcile accounts receivableAS
  • Accrue the rentAS
  • Lock the period in the ledgerML
KPIDays to a closed monthMonthly · target 56

The tasks live in the project. The page refers to them.

3Written together

You write together, and Kalends AI reads along

Several people can write in the same page at once, each with a cursor of their own, and every version is kept and can be restored. Comments sit beside the text, not inside it. Ask Kalends answers from the pages, names the page an answer came from and turns what a page says needs doing into tasks. The area's agent reads the pages and speaks up when something is missing.

  • Several cursors in the same text
  • Comments beside the text, not inside it
  • History you can restore from
Kalends · W-12 Year-end routine
Year-end routineMLAS

The reconciliations are due before that, and whoever owns the account answers for itMaria L

Comments1

the fifth banking day

ASAnna S

Does that hold after the turn of the year? It tends to be the sixth.

Reply

Saves as you type.

4Markdown

Markdown, so the text stays yours

A page is stored as Markdown in Obsidian's dialect: [[W-12|Heading]] for links between pages, > [!note] for callouts and ordinary Markdown tables. The pages come with the export as a zip holding one .md file per page, and they open in a vault without conversion. No lock-in to a format only Kalends can read.

  • Obsidian's Markdown dialect
  • One .md file per page in the export
  • The links work in a vault
Kalends · W-12 Year-end routine

As you read it

Year-end routine

Closing

The books close on the fifth banking day.

Worth knowing: the rent is accrued in the same run.

As it is stored

## ClosingThe books close on the fifth banking day.> [!note] Worth knowing> The rent is accrued in the same run.See also [[W-18|Approval limits]].

Export · kalends-export.zip

  • pages/Finance/Year-end routine.md
  • pages/Finance/Approval limits.md

The same text in Kalends, in the export and in your vault.

Access

A page is read as the thing it belongs to

Access follows the structure, and can be tightened on a single page.

  • Read as the thing it belongs to

    Whoever may read the area, directive, project, goal or commitment may read its pages. There is no separate list of permissions to keep in step with it.

  • Can be tightened on one page

    The menu item Who may read limits the page, and everything beneath it, to chosen people and departments. Whoever limits the page stays in, and administrators read every page.

  • Guests and watch-only members read

    Guests and watch-only members open pages and comments but write nothing, and an organisation in read-only mode reads on the same terms.

  • Public links can be closed again

    A page can be shared with named people or published by a public link, and the link can be closed again. A limited page is never carried along by accident.

  • History is as private as the page

    What History keeps about a page is shown only to people who may read the page, also after it has moved. Every version stays, with who wrote in it.

  • The AI sees only what the person sees

    Ask Kalends and the area's agent read the pages with the reader's own permissions, using the organisation's own AI key, and never a limited page.

Getting started

Start from a description you already have

There is nothing to move in first.

  1. 1

    Open Pages

    The Pages tab shows the areas, directives, projects, goals and commitments that have pages. The chip Without pages shows the rest, so the first page can be written under any of them.

  2. 2

    Write under what it concerns

    Choose + on a row to add a subpage, or open the description and carry on writing in it. It saves as you type, and everyone reading the same page shows up with their cursor.

  3. 3

    Link the work in

    Type the key of a task, a KPI or a commitment and it becomes a live card. Ask Kalends to turn what the page says should be done into tasks, and give the area an agent that keeps the pages current.

Common questions about Pages

Is this a wiki?

Pages do a wiki's work, without a tree of their own. A page hangs under the area, project, goal or commitment it is about and inherits its place and its access from there. That is why we call it Pages.

What happens to the descriptions we have already written?

They are pages already. The description of an area, a directive, a project, a goal or a commitment is its page, with the same text and the same name, and everything that reads descriptions works exactly as before. An area without a description shows no page until somebody writes one.

Who may write?

Subpages are written by members and administrators who may read the thing the page belongs to. Guests and watch-only members read. An area that has reserved editing for its responsible people keeps that rule, and the description follows the rule it has always followed.

Can we share a page outside Kalends?

Yes. A page can be shared with named people or published by a public link, and the link can be closed again. A page limited to certain people is not carried along when the page above it is shared.

Can we limit who reads a single page?

Yes. The menu item Who may read limits the page, and everything beneath it, to chosen people and departments. Whoever limits the page stays in, administrators read every page, and nobody else sees it anywhere: not in the tree, not in search, not under Mentioned on and not through Ask Kalends. The area's agent never reads a limited page.

Do the tasks live in the page?

No. Tasks live in projects and goals. The page refers to them with a live card, and a checklist in the text is formatting. Make it a task turns a checklist line into a real task, and the line is replaced by a reference to it.

Do we get the text out if we leave?

Yes. The pages come with the export as a zip of Markdown files, one file per page, with the links written so they work in a vault. The files attached to the pages come along as they do today.

What do the pages cost?

Nothing beyond the seats. A page's text does not count towards your storage, just as descriptions do not today. Attached files count as before.

More about Kalends

AI and MCPAsk Kalends answers from the pages and says where from.Agents in areasThe agent reads the area's pages and speaks up when something is missing.ProjectsThe tasks a page refers to live here.

Write the first page under one of your areas

Try Kalends for 30 days. The description you already have is the page you start from.

Try Kalends

Contact Kalends

Tell us a little about what you need and our support team will receive your message.

We use the details you provide to answer your enquiry. Privacy policy