We need a landing page for kodu.work.
Here is a start: four files, one for each part. Open the ones you want.
- Landing copy
- Page map
- Launch pitch
- Intro video
Private workspace · Live pages
kodu.work is a private workspace where notes, canvases, decks, tables and videos sit on one desk. Ask in a project chat, review what comes back, and publish the parts you choose as a live page.
A private project chat starts with one request: “We need a landing page for kodu.work.”
The chat proposes four files, and each one opens as its own working surface: a note, a canvas, a deck and a video.
Each file does its own job. The note gets the copy, the canvas maps the page, the deck holds the pitch, the video gets a timeline.
A second chat picks up the four files and asks: “Make this a live page.”
The selected work assembles into one browser page. The round green dot means the page is live.
Tools
Every file lives in the same Files list, with the same folders, sharing and comments. Pick the tool that fits the job, then put the pieces together.
Notes in a quiet serif editor, with blocks for headings, lists, images, tables and canvases. Notes work offline and sync when you reconnect.
Slides with speaker notes, a presenter view and version history. Export a PDF, send a share link, or record yourself presenting the deck as a video.
Records with typed columns: text, number, date, checkbox, tags and links to rows in other tables. Save the views you use, with their filters and sort order.
A live page can ask visitors for an email address before it opens. Each address goes into a list that only you can read, and you can delete any entry.
An open board for maps, flows and storyboards, drawn by hand or by shape. Place a canvas inside a note so the picture stays next to the words.
Short videos made of scenes on a timeline, with voice-over and your own clips. kodu.work renders them to MP4 on its own renderer.
HTML files and live-page layouts let you write your own markup, style and script. They run in a sandboxed frame, next to the rest of your library.
Principles
Four decisions shape every tool. They are why a file can move from your desk to a reader, or to an agent, without a copy in between.
Share any file with a person as viewer, commenter or editor. A folder passes its access down to what it holds. Decks get share links, notes get write links, and a live page is public on purpose.
Every file type has the same operations over REST, MCP and a command-line tool, from one contract. An agent key acts as the person who issued it, with the scopes they choose, and sees only what that person can see.
Assistants make proposals; you decide. Deck, video-scene and live-page proposals change nothing until you apply them. You can revert an applied deck proposal while nothing else has changed.
A note or a deck becomes a public live page in one step, at a name you choose. Unpublish it just as fast. Publishing to your own domain is the next step and is not available yet.
Own domain: not yet
Access is by invitation while the tools settle. If you have an account, sign in and your library opens here, on kodu.work.