diff --git a/.github/workers/github-login/github-oauth.js b/.github/workers/github-login/github-oauth.js
deleted file mode 100644
index c6455a5..0000000
--- a/.github/workers/github-login/github-oauth.js
+++ /dev/null
@@ -1,63 +0,0 @@
-addEventListener("fetch", (event) => {
- event.respondWith(handle(event.request));
-});
-
-// use secrets
-const client_id = CLIENT_ID;
-const client_secret = CLIENT_SECRET;
-
-async function handle(request) {
- // handle CORS pre-flight request
- if (request.method === "OPTIONS") {
- return new Response(null, {
- headers: {
- "Access-Control-Allow-Origin": "*",
- "Access-Control-Allow-Methods": "GET, POST, OPTIONS",
- "Access-Control-Allow-Headers": "Content-Type",
- },
- });
- }
-
- // redirect GET requests to the OAuth login page on github.com
- if (request.method === "GET") {
- const scope = new URL(request.url).searchParams.get("scope");
- return Response.redirect(
- `https://github.com/login/oauth/authorize?client_id=${client_id}&scope=${scope}`,
- 302
- );
- }
-
- try {
- const { code } = await request.json();
-
- const response = await fetch(
- "https://github.com/login/oauth/access_token",
- {
- method: "POST",
- headers: {
- "content-type": "application/json",
- accept: "application/json",
- },
- body: JSON.stringify({ client_id, client_secret, code }),
- }
- );
- const result = await response.json();
- const headers = {
- "Access-Control-Allow-Origin": "*",
- };
-
- if (result.error) {
- return new Response(JSON.stringify(result), { status: 401, headers });
- }
-
- return new Response(JSON.stringify({ token: result.access_token }), {
- status: 201,
- headers,
- });
- } catch (error) {
- console.error(error);
- return new Response(error.message, {
- status: 500,
- });
- }
-}
\ No newline at end of file
diff --git a/.github/workers/github-login/wrangler.toml b/.github/workers/github-login/wrangler.toml
deleted file mode 100644
index 9a41642..0000000
--- a/.github/workers/github-login/wrangler.toml
+++ /dev/null
@@ -1,4 +0,0 @@
-name = "treehouse-demo-login"
-workers_dev = true
-compatibility_date = "2023-02-08"
-main = "github-oauth.js"
\ No newline at end of file
diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
deleted file mode 100644
index b9cfe92..0000000
--- a/.github/workflows/deploy.yml
+++ /dev/null
@@ -1,32 +0,0 @@
-name: Website Build and Deploy
-on:
- push:
- branches:
- - main
-permissions:
- contents: write
-jobs:
- build-and-deploy:
- concurrency: ci-${{ github.ref }}
- runs-on: ubuntu-latest
- steps:
- - name: Checkout
- uses: actions/checkout@v3
-
- - name: Setup Deno
- uses: denoland/setup-deno@v1
- with:
- deno-version: v1.x
-
- - name: Build
- run: |
- deno task bundle
- deno task build
- env:
- BACKEND: github
- BACKEND_URL: https://treehouse-demo-login.proteco.workers.dev
-
- - name: Deploy
- uses: JamesIves/github-pages-deploy-action@v4
- with:
- folder: web/_out
\ No newline at end of file
diff --git a/.github/workflows/workers.yml b/.github/workflows/workers.yml
deleted file mode 100644
index c079b64..0000000
--- a/.github/workflows/workers.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-name: Worker Deploys
-on:
- push:
- branches:
- - main
- paths:
- - '.github/workers/**'
- - '.github/workflows/workers.yml'
-jobs:
- github-login:
- concurrency: ci-${{ github.ref }}
- runs-on: ubuntu-latest
- steps:
- - name: Checkout
- uses: actions/checkout@v3
-
- - name: Publish
- uses: cloudflare/wrangler-action@2.0.0
- with:
- command: publish
- apiToken: ${{ secrets.CF_API_TOKEN }}
- accountId: ${{ secrets.CF_ACCOUNT_ID }}
- workingDirectory: '.github/workers/github-login'
- secrets: |
- CLIENT_ID
- CLIENT_SECRET
- env:
- CLIENT_ID: ${{ secrets.DEMO_CLIENT_ID }}
- CLIENT_SECRET: ${{ secrets.DEMO_CLIENT_SECRET }}
\ No newline at end of file
diff --git a/.gitignore b/.gitignore
deleted file mode 100644
index 98ad90e..0000000
--- a/.gitignore
+++ /dev/null
@@ -1,11 +0,0 @@
-/web/_out
-/web/static/lib/treehouse.js
-/web/static/lib/treehouse.js.map
-/web/static/lib/treehouse.min.js
-/web/static/lib/treehouse.min.js.map
-/web/_vendor/**/node_modules
-/web/_vendor/**/package-lock.json
-/web/_vendor/octokit/package.json
-/local
-.DS_Store
-/NOTES
\ No newline at end of file
diff --git a/.vscode/settings.json b/.vscode/settings.json
deleted file mode 100644
index 4b9fb22..0000000
--- a/.vscode/settings.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
- "deno.enable": true
-}
\ No newline at end of file
diff --git a/web/static/CNAME b/CNAME
similarity index 100%
rename from web/static/CNAME
rename to CNAME
diff --git a/LICENSE b/LICENSE
deleted file mode 100644
index 3af2053..0000000
--- a/LICENSE
+++ /dev/null
@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2023 Jeff Lindsay
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
\ No newline at end of file
diff --git a/README.md b/README.md
deleted file mode 100644
index f524d5d..0000000
--- a/README.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# treehouse
-
-Bring your own backend Tana-style frontend. Actively being developed.
-
-
-
-* Outline editor and repurposable workbench shell.
-* Built with [Deno](https://deno.land/) toolchain. Zero Node.js utilization.
-* Minimal dependencies, mainly [Mithril.js](https://mithril.js.org/).
-
-## Demo
-
-This project is meant as a frontend toolkit for your own note-taking app,
-but we're maintaining a usable [live demo](https://treehouse.sh/demo/)
-based on the current state of the main branch.
-
-## Development
-
-Contribute by [installing Deno](https://deno.land/manual@v1.30.0/getting_started/installation),
-cloning the repo, and running:
-
-```
-deno task serve
-```
-
-This will run a development server for the project site that includes the
-demo, which you can use for development.
-
-## Community
-
-* [Devstream](https://www.twitch.tv/progrium) - Majority of development is streamed live on Twitch
-* [Devlog](https://github.com/treehousedev/treehouse/discussions/categories/devlog) - Devlog updates about development
-* [Forums](https://github.com/treehousedev/treehouse/discussions) - Basic discussion on GitHub
-
-## License
-
-MIT
diff --git a/_config.js b/_config.js
deleted file mode 100644
index ded037b..0000000
--- a/_config.js
+++ /dev/null
@@ -1,86 +0,0 @@
-import lume from "lume/mod.ts";
-import attrs from "npm:markdown-it-attrs";
-import jsx from "lume/plugins/jsx_preact.ts";
-import nav from "lume/plugins/nav.ts";
-import feed from "lume/plugins/feed.ts";
-import codeHighlight from "lume/plugins/code_highlight.ts";
-import lang_javascript from "https://unpkg.com/@highlightjs/cdn-assets@11.6.0/es/languages/javascript.min.js";
-import lang_bash from "https://unpkg.com/@highlightjs/cdn-assets@11.6.0/es/languages/bash.min.js";
-import toc from "https://deno.land/x/lume_markdown_plugins@v0.5.1/toc.ts";
-
-import * as esbuild from "https://deno.land/x/esbuild@v0.17.2/mod.js";
-
-let lastBuild = 0;
-
-const site = lume({
- location: new URL("https://treehouse.sh"),
- src: "./web",
- dest: "./web/_out",
- server: {
- middlewares: [
- async (request, next) => {
- const url = new URL(request.url);
- if (url.pathname === "/lib/treehouse.min.js") {
- if (lastBuild < Date.now()-1000) {
- await esbuild.build({
- entryPoints: ["lib/mod.ts"],
- bundle: true,
- outfile: "web/_out/lib/treehouse.js",
- jsxFactory: "m",
- sourcemap: true,
- format: "esm",
- keepNames: true,
- // minify: true
- });
- lastBuild = Date.now();
- }
- Object.defineProperty(request, "url", {value: request.url.replace(".min", "")});
- }
- return await next(request);
- }
- ]
- }
-}, {
- markdown: {
- plugins: [attrs],
- keepDefaultPlugins: true,
- }
-});
-site.copy("static", ".");
-
-site.use(feed({
- output: ["/blog/feed.rss", "/blog/feed.json"],
- query: "layout=layouts/blog.tsx",
- info: {
- title: "=site.title",
- description: "=site.description",
- },
- items: {
- title: "=title",
- },
-}));
-site.use(toc({
- level: 2,
- anchor: false
-}));
-site.use(nav());
-site.use(jsx());
-site.use(codeHighlight({
- languages: {
- javascript: lang_javascript,
- bash: lang_bash,
- },
-}));
-
-site.filter("formatDate", (value) => new Date(value).toLocaleDateString('en-us', { year:"numeric", month:"short", day:"numeric"}));
-
-site.data("site", {
- title: "Treehouse",
- description: "An open source note-taking frontend to extend and customize."
-});
-site.data("backend", JSON.stringify({
- name: Deno.env.get("BACKEND") || "browser",
- url: Deno.env.get("BACKEND_URL")
-}));
-
-export default site;
diff --git a/web/static/analytics.js b/analytics.js
similarity index 100%
rename from web/static/analytics.js
rename to analytics.js
diff --git a/web/static/app/main.css b/app/main.css
similarity index 100%
rename from web/static/app/main.css
rename to app/main.css
diff --git a/web/static/app/main.js b/app/main.js
similarity index 100%
rename from web/static/app/main.js
rename to app/main.js
diff --git a/web/static/app/main.webmanifest b/app/main.webmanifest
similarity index 100%
rename from web/static/app/main.webmanifest
rename to app/main.webmanifest
diff --git a/blog/feed.json b/blog/feed.json
new file mode 100644
index 0000000..5ba2fc1
--- /dev/null
+++ b/blog/feed.json
@@ -0,0 +1 @@
+{"version":"https://jsonfeed.org/version/1","title":"Treehouse","home_page_url":"https://treehouse.sh/","feed_url":"https://treehouse.sh/blog/feed.json","description":"An open source note-taking frontend to extend and customize.","items":[{"id":"https://treehouse.sh/blog/v0-7-0/","url":"https://treehouse.sh/blog/v0-7-0/","title":"Release 0.7.0","content_html":"
Descriptions, better paste, shortcut drawer
\n
We're excited to be adding a handful of minor enhancements in this release. The first is node descriptions, which allow you to add small text below your node content, as part of the same node. Use it to add context or any kind of secondary information. To use, select your node, open the Command Palette with Command/Control + K, and select "Add Description".
\n
We've made several improvements related to cut/copy/pasting text. Now if you paste text containing new lines, we'll convert each newline to a separate node. We've also fixed some bugs and UX flows.
\n
Lastly, check out the keyboard shortcut drawer! We want it to be super easy to learn and use keyboard shortcuts and hope this helps.
\n","date_published":"Fri, 18 Aug 2023 00:00:00 GMT"},{"id":"https://treehouse.sh/blog/v0-6-0/","url":"https://treehouse.sh/blog/v0-6-0/","title":"Release 0.6.0","content_html":"
New Document and Tab Views
\n
In this release we're introducing two new views: Document view, and Tab view. Views are a powerful idea in Treehouse that can either be used to create embedded mini-apps or act as building blocks for you to make your own. These new views are an example of each.
\n
Document view gives you a more conventional note-taking experience. In Document view each child node is rendered as a paragraph in the center of the panel. Documents support simple Markdown formatting like bold, italic, strikethrough, and ordered and unordered lists. Turn a node into a document by choosing "Make Document" from the Command Palette. Unlike other views, changing to Document view is a one-way action and nodes can't be converted back to other views.
\n
Tab view renders each child node as a tab. Their children (grandchild nodes) are shown beneath when the tab is selected. These nodes will retain their view, so you can combine Tab view with others to create a more complex larger view of your data. In general, Tab view is useful for saving vertical space across several categories. Turn nodes into tabs by selecting the parent node and choose "View as Tabs" from the Command Palette. Since Tab view is read-only, you can modify tabs by switching back to List view.
\n
We've also renamed Live Search Nodes to Smart Nodes, which can now be named separate from their query. This also resolves an issue where previously you couldn't use them for tag searches.
Treehouse now supports tags and templates! For example, you can now create a template node with children and fields, name it "book", then any node tagged with #book will automatically get those fields and children. To turn a node into a template, select "Make Template" from the Command Palette. You can also tag nodes without an equivalent template. Tagging is done by simply adding hashtags to a node's text.
\n
You can search for tagged nodes in the search bar using the hashtag notation (#book), however there is a known issue preventing you from searching for nodes by tag in Smart Nodes. This will be resolved in the next release, and in main much sooner.
\n
You can now take a list of nodes with fields and turn them into an easy-to-scan table. Simply go to the parent node of the rows, open the Command Palette with Command+K, and choose "View as Table". We'll be adding more features to the table view in coming releases.
\n
Double-quoted search terms now allow spaces and search results are a little tighter now. Last but not least we've added cut, copy, and paste commands for nodes, making it easier to duplicate and move nodes around.
In this release we focused on making Treehouse more powerful and enjoyable to use from more places. Editing text on mobile is always a tricky prospect, but we've taken our first step to being mobile-friendly with customized navigation and easier touch targets.
\n
White background a bit too bright? We've added several built-in themes (including sepia and dark mode) and we've made it super easy to create your own CSS themes using our component variables.
\n
Otherwise, lots of quality of life improvements as usual, especially for fields and Smart Nodes.
\n","date_published":"Mon, 19 Jun 2023 00:00:00 GMT"},{"id":"https://treehouse.sh/blog/v0-3-0/","url":"https://treehouse.sh/blog/v0-3-0/","title":"Release 0.3.0","content_html":"
New Node Types: Fields, Live Search, and References
\n
This release we added some exciting new features: Fields, Live Search, and References. These new node types represent our first step into becoming much more than a simple outliner. Quality of live improvements include making the node menu easier to click, initial work towards a mobile view, and improving interactivity of the command palette. We also cleaned up all our UI elements to match our design system, allowing for better custom CSS support.
\n
Update 7/10/2023: Live Search is now called Smart Nodes
A field is a node that can store a key-value pair. This introduces structured data to your nodes, letting you create nodes as data records. You can also search for nodes by field. This initial pass supports text values, but we'll soon provide more value types.
\n
To turn a node into a field:
\n\n
Indent underneath the node you want to contain the field, and type the field name
\n
Command/Control + K to open the command palette, and choose "Create Field"
\n
Add your field value in the value section
\n\n
New Feature: Live Search
\n
Live Search allows you to create search nodes where the children are auto-updating search results. Simply type a keyword, or use the format "fieldname:value" to filter by fields. The Live Search nodes will update automatically as your workspace content changes. This is a powerful way to view your data in new configurations.
\n
To create a Live Search:
\n\n
Create a new node where you want your search node, and type your search value
\n
Command/Control + K to open the command palette, and choose "Create Search Node"
\n\n
Tips: Search terms are case-insensitive, and you can filter on multiple fields (uses AND, not OR) like so: "fieldname:value fieldname:value".
\n
New Feature: References
\n
References are nodes that refer to another node and its children inline. They're sort of like symlinks on the filesystem. This lets you have a node exist in multiple places at once. References are differentiated from normal nodes with a dashed outline around their outline bullet. Deleting a reference node does not delete the node it points to. You may notice that Live Search results are reference nodes!
\n
To create a reference node:
\n\n
Select the node you want to make a reference to
\n
Command/Control + K to open the command palette, and choose "Create Reference"
\n","date_published":"Wed, 17 May 2023 00:00:00 GMT"},{"id":"https://treehouse.sh/blog/influences/","url":"https://treehouse.sh/blog/influences/","title":"Treehouse Influences","content_html":"
Over the past few months, we've built a frontend framework for an elegant, quality outliner that's open source, extensible, and gives you control of your data. I’d like to share some of the design influences for the Treehouse frontend, which should give a sense of the unique direction Treehouse is going from here.
\n
The biggest influences for Treehouse are Tana, Notion, and Obsidian. These three represent the state of the art of personal and collaborative information management, sometimes simplified as note-taking tools. However, "note-taking tools" sells them short as they go beyond note-taking and information management. For lack of a better descriptor, many consider them tools for thought.
\n
From Notes to Tools for Thought
\n
For most, note-taking brings to mind simple apps like Apple Notes and Google Keep, or even just a text file editor. These work well for people because they're already there and focus on quick and easy plain text capture. We could call this casual note-taking.
\n
Back in the 2000s, hosted and self-hosted wikis became popular for easy, collaborative web publishing and knowledge management. Like Wikipedia, they could be used to build out hyperlinked knowledge repositories. Many wiki-based tools focused on their use as personal notebooks, one of the most influential examples being TiddlyWiki. The simple versatility of the wiki laid the groundwork for what we call "tools for thought" today.
\n
\n
When Notion appeared in the mid-2010s, it built on the idea of the wiki and introduced structured data management with flexible views that effectively gave you integrated, customizable versions of other productivity tools. Notion, Airtable, and others helped bring in the age of no-code and low-code tools, allowing knowledge workers and entrepreneurs to build their own "apps" or solutions to problems without traditionally building software. Notion brought it all together in a simple, user-friendly experience based around the core idea of wiki-like information management.
\n
\n
Meanwhile, a separate paradigm of note-taking tools emerged, focusing on the nested, tree-like structure of the outline. Perhaps inspired by tools like OmniOutliner and Org Mode for Emacs of the 2000s, Workflowy appeared in 2010 as a no-frills web-based outliner.
\n
\n
Obsidian arrived in 2020 and is a local app focusing on Markdown files stored on your filesystem. Obsidian has a large plugin ecosystem giving it a wide breadth of features, but it’s especially appealing to those that want to own their data. If you strip away the plugins, Obsidian is a pretty simple hyperlinked Markdown editor.
\n
\n
Most recently, a tool in early access called Tana caught my attention. Their key innovation is taking the linked outline model of Workflowy and introducing schemas for nodes, making them into structured data. This gives Tana the embedded database functionality of Notion and Airtable, a step towards bringing the two paradigms of note-taking software together towards powerful, malleable tools for thought.
\n
\n
How Treehouse Fits In
\n
By now there's no shortage of options in this space, both as SaaS and open source. Take a look at this growing encyclopedia of note-taking tools. Like Notion and Tana, many of the apps listed are much more than note-taking tools. Some lean into the framing of "collaborative documents", and some are just categorized more generally as "productivity tools". Tana goes so far as to say "the everything OS".
\n
Note-taking is just the beginning. It's a tangible gateway for something more powerful inherent to computing. Ever since Engelbart's mother of all demos, the computing revolution seems to start with powerful tools for thought, which are, at minimum, good note-taking tools.
\n
\n
Treehouse is a frontend and starter kit for anybody else that wants to explore this space with us. We will release a standalone product based on it soon, but most of the user-facing development will be done in the open source Treehouse project.
\n
\n
Today with Treehouse you can build your own Workflowy equivalent, but soon it will become more comparable to Tana and Notion with the open extensibility of Obsidian. That alone is pretty exciting to have in a minimal open source project, but I can't wait to show you what will come next.
\n
Coming Soon
\n
In the next post, I'll start getting technical and share details on the Treehouse project stack and architecture. If you can't wait, we do have documentation for you to check out.
\n
Thanks for reading, and a big thanks to my sponsors for supporting this kind of open source work. Share your thoughts and favorite note-taking tools in the discussion thread for this post.
New design system, GitHub session locking, and documentation
\n
This release is a refinement of our initial release, fixing a number of bugs and adding interaction improvements. The look and feel of the UI was also updated with the start of a new CSS design system based on custom properties. Session locking was added for the live demo and GitHub backend so multiple devices/browsers/tabs don't clobber changes of each other. Documentation also got an upgrade with the start of a full guide on the website.
\n","date_published":"Mon, 27 Mar 2023 00:00:00 GMT"},{"id":"https://treehouse.sh/blog/v0-1-0/","url":"https://treehouse.sh/blog/v0-1-0/","title":"Release 0.1.0","content_html":"
It begins...
\n
This first development release captures core functionality of the frontend to the point of being internally usable in the demo deployment. For developers, the project source layout, architecture, and backend API is defined in broad strokes in the right direction but is by no means stable.
\n","date_published":"Fri, 03 Mar 2023 00:00:00 GMT"},{"id":"https://treehouse.sh/blog/welcome/","url":"https://treehouse.sh/blog/welcome/","title":"Welcome to Treehouse","content_html":"
I'm excited to announce the start of a new major project that I'll be sharing the journey of on this fancy new blog. The project is called Treehouse, which is starting as an open source note-taking frontend and will evolve into something much more.
\n
\n
We're creating a simple, hackable kernel of a note-taking tool as a web frontend that can be extended and customized by developers. Then we'll use that frontend to build a new kind of note-taking product. Today we have an early preview of our first minimum viable prototype of the frontend, and we'll be finishing up this release in the open on GitHub.
\n
The open source project is a functional app frontend that you can deploy and back in various ways. For developers, this "bring your own backend" approach makes Treehouse a great starting point to build your own note-taking tool, just as we intend to do. We also have pre-made backends for those who want to use it with little-to-no programming. Either way, you'll always own your data, and now the system presenting it to you as well.
\n
In this post, I'm going to talk about our minimum viable prototype and the approach we're taking with Treehouse as an open source project.
\n
Out of the Box
\n
While inspired by powerful tools like Notion, Tana, and Obsidian, we wanted to boil our initial goal down to the essentials while still being usable enough to use ourselves. As we continue to plan our prototype release milestone, we'd love to hear what you think is essential for you to have in a tool and platform like this, but here is what to expect as a baseline.
\n
Outliner with Markdown Pages
\n
At the heart of Treehouse is a graph-like system I've been developing called Manifold. This will play a big part in the long-term extensibility of Treehouse, which I'll talk more about in the future. For now, this maps very cleanly to the outliner model popularized by Workflowy, Tana, and others.
\n
However, I'm also a fan of Notion-style pages and Obsidian's commitment to working with plain Markdown files. The Manifold system allows us to make certain nodes into Markdown pages. This hybrid model gets us the best of both worlds with room for even more possibilities later on.
\n
Quick Add and Daily Notes
\n
Being able to quickly get thoughts and information into the system has been a key aspect of every good note-taking system. This can be exposed a number of ways from browser extensions to desktop shortcuts, but what makes any "quick add" functionality quick is not having to think about where it will be organized.
\n
Luckily, "daily notes" has become such a common pattern that many recent tools have managed daily notes built-in. This typical gives you a "today" note that is automatically organized into a calendar-like structure. This conveniently becomes the perfect destination for "quick add" notes.
\n
Full-text Search
\n
Whether you are an obsessive organizer or are too busy to take the time, solid full-text search is basically a necessity. It's how we quickly get to our data.
\n
Out of the box we have a full-text search that doesn't require a backend. However, our pluggable backend will allow you to power search in a number of ways, and also opens up the ability to search into external systems that are important to you.
\n
Built-in Backends
\n
"Bring your own backend" is a critical part of the design of this project, but Treehouse also needs to be usable by people who prefer not to build their own backend. Our prototype release is planned to include a handful of built-in backends to get started with.
\n
Our preview demo is using a localStorage backend, which works for development and special use cases. Of course, we will have a simple local filesystem backend for desktop scenarios, similar to Obsidian.
\n
However, we're most excited for the GitHub backend. This functions similarly to the local filesystem backend, but it would be versioned in a central repository on your GitHub account and be accessible on any online platform.
\n
Backends will not only let you extend storage, search, and authentication, but other aspects in the future.
\n
Project Overview
\n
The Treehouse codebase and open source project is as much the product as its features. The entire user and developer experience is being designed around simplicity and human ergonomics.
\n
The Treehouse frontend is built with web technologies intended for use across web, mobile, and desktop platforms. The project is written in TypeScript using Deno as its JavaScript toolchain.
\n
The JavaScript ecosystem is a mess, but Deno provides a forward-looking, self-contained toolchain that's easy to love. We actually have a zero Node.js policy and avoid NPM modules as much as possible.
\n
With minimal dependencies and an ongoing effort to keep the codebase small, it will always be easy to understand the entire Treehouse system. This will be further supported with a focus on documentation, both API docs and guides.
\n
We're using a permissive open source license, allowing you to use or change our code as you see fit. Contribution and participation is welcome, but so is simply consuming downstream.
\n
The project is actively being developed but we keep a preview demo running off the main branch that should always be in working order.
\n
Coming Soon
\n
I'm excited to give you a deeper look at the project stack in a future post. For now, keep an eye out for the next post digging into the influences for Treehouse. We'll also try to answer "why another note-taking tool", and tease some long-term ideas for the future.
\n
Lastly, I want to mention the project is being developed in the open, not just with the code on GitHub, but most of my work is streamed and archived on Twitch. Feel free to come and co-work with me.
\n
Thanks for reading, and a big thanks to my sponsors for supporting this kind of open source work.
\n","date_published":"Thu, 23 Feb 2023 00:00:00 GMT"}]}
\ No newline at end of file
diff --git a/blog/feed.rss b/blog/feed.rss
new file mode 100644
index 0000000..abccf5c
--- /dev/null
+++ b/blog/feed.rss
@@ -0,0 +1,385 @@
+
+
+
+ Treehouse
+ https://treehouse.sh/
+
+ An open source note-taking frontend to extend and customize.
+ Tue, 26 Nov 2024 18:57:49 GMT
+ en
+ Lume v1.17.5
+
+ Release 0.7.0
+ https://treehouse.sh/blog/v0-7-0/
+ https://treehouse.sh/blog/v0-7-0/
+
+
+ Descriptions, better paste, shortcut drawer
+
We're excited to be adding a handful of minor enhancements in this release. The first is node descriptions, which allow you to add small text below your node content, as part of the same node. Use it to add context or any kind of secondary information. To use, select your node, open the Command Palette with Command/Control + K, and select "Add Description".
+
We've made several improvements related to cut/copy/pasting text. Now if you paste text containing new lines, we'll convert each newline to a separate node. We've also fixed some bugs and UX flows.
+
Lastly, check out the keyboard shortcut drawer! We want it to be super easy to learn and use keyboard shortcuts and hope this helps.
+ ]]>
+
+ Fri, 18 Aug 2023 00:00:00 GMT
+
+
+ Release 0.6.0
+ https://treehouse.sh/blog/v0-6-0/
+ https://treehouse.sh/blog/v0-6-0/
+
+
+ New Document and Tab Views
+
In this release we're introducing two new views: Document view, and Tab view. Views are a powerful idea in Treehouse that can either be used to create embedded mini-apps or act as building blocks for you to make your own. These new views are an example of each.
+
Document view gives you a more conventional note-taking experience. In Document view each child node is rendered as a paragraph in the center of the panel. Documents support simple Markdown formatting like bold, italic, strikethrough, and ordered and unordered lists. Turn a node into a document by choosing "Make Document" from the Command Palette. Unlike other views, changing to Document view is a one-way action and nodes can't be converted back to other views.
+
Tab view renders each child node as a tab. Their children (grandchild nodes) are shown beneath when the tab is selected. These nodes will retain their view, so you can combine Tab view with others to create a more complex larger view of your data. In general, Tab view is useful for saving vertical space across several categories. Turn nodes into tabs by selecting the parent node and choose "View as Tabs" from the Command Palette. Since Tab view is read-only, you can modify tabs by switching back to List view.
+
We've also renamed Live Search Nodes to Smart Nodes, which can now be named separate from their query. This also resolves an issue where previously you couldn't use them for tag searches.
Treehouse now supports tags and templates! For example, you can now create a template node with children and fields, name it "book", then any node tagged with #book will automatically get those fields and children. To turn a node into a template, select "Make Template" from the Command Palette. You can also tag nodes without an equivalent template. Tagging is done by simply adding hashtags to a node's text.
+
You can search for tagged nodes in the search bar using the hashtag notation (#book), however there is a known issue preventing you from searching for nodes by tag in Smart Nodes. This will be resolved in the next release, and in main much sooner.
+
You can now take a list of nodes with fields and turn them into an easy-to-scan table. Simply go to the parent node of the rows, open the Command Palette with Command+K, and choose "View as Table". We'll be adding more features to the table view in coming releases.
+
Double-quoted search terms now allow spaces and search results are a little tighter now. Last but not least we've added cut, copy, and paste commands for nodes, making it easier to duplicate and move nodes around.
+ ]]>
+
+ Thu, 06 Jul 2023 00:00:00 GMT
+
+
+ Release 0.4.0
+ https://treehouse.sh/blog/v0-4-0/
+ https://treehouse.sh/blog/v0-4-0/
+
+
+ Mobile support and CSS themes
+
In this release we focused on making Treehouse more powerful and enjoyable to use from more places. Editing text on mobile is always a tricky prospect, but we've taken our first step to being mobile-friendly with customized navigation and easier touch targets.
+
White background a bit too bright? We've added several built-in themes (including sepia and dark mode) and we've made it super easy to create your own CSS themes using our component variables.
+
Otherwise, lots of quality of life improvements as usual, especially for fields and Smart Nodes.
+ ]]>
+
+ Mon, 19 Jun 2023 00:00:00 GMT
+
+
+ Release 0.3.0
+ https://treehouse.sh/blog/v0-3-0/
+ https://treehouse.sh/blog/v0-3-0/
+
+
+ New Node Types: Fields, Live Search, and References
+
This release we added some exciting new features: Fields, Live Search, and References. These new node types represent our first step into becoming much more than a simple outliner. Quality of live improvements include making the node menu easier to click, initial work towards a mobile view, and improving interactivity of the command palette. We also cleaned up all our UI elements to match our design system, allowing for better custom CSS support.
+
Update 7/10/2023: Live Search is now called Smart Nodes
A field is a node that can store a key-value pair. This introduces structured data to your nodes, letting you create nodes as data records. You can also search for nodes by field. This initial pass supports text values, but we'll soon provide more value types.
+
To turn a node into a field:
+
+
Indent underneath the node you want to contain the field, and type the field name
+
Command/Control + K to open the command palette, and choose "Create Field"
+
Add your field value in the value section
+
+
New Feature: Live Search
+
Live Search allows you to create search nodes where the children are auto-updating search results. Simply type a keyword, or use the format "fieldname:value" to filter by fields. The Live Search nodes will update automatically as your workspace content changes. This is a powerful way to view your data in new configurations.
+
To create a Live Search:
+
+
Create a new node where you want your search node, and type your search value
+
Command/Control + K to open the command palette, and choose "Create Search Node"
+
+
Tips: Search terms are case-insensitive, and you can filter on multiple fields (uses AND, not OR) like so: "fieldname:value fieldname:value".
+
New Feature: References
+
References are nodes that refer to another node and its children inline. They're sort of like symlinks on the filesystem. This lets you have a node exist in multiple places at once. References are differentiated from normal nodes with a dashed outline around their outline bullet. Deleting a reference node does not delete the node it points to. You may notice that Live Search results are reference nodes!
+
To create a reference node:
+
+
Select the node you want to make a reference to
+
Command/Control + K to open the command palette, and choose "Create Reference"
+ ]]>
+
+ Wed, 17 May 2023 00:00:00 GMT
+
+
+ Treehouse Influences
+ https://treehouse.sh/blog/influences/
+ https://treehouse.sh/blog/influences/
+
+
+ Over the past few months, we've built a frontend framework for an elegant, quality outliner that's open source, extensible, and gives you control of your data. I’d like to share some of the design influences for the Treehouse frontend, which should give a sense of the unique direction Treehouse is going from here.
+
The biggest influences for Treehouse are Tana, Notion, and Obsidian. These three represent the state of the art of personal and collaborative information management, sometimes simplified as note-taking tools. However, "note-taking tools" sells them short as they go beyond note-taking and information management. For lack of a better descriptor, many consider them tools for thought.
+
From Notes to Tools for Thought
+
For most, note-taking brings to mind simple apps like Apple Notes and Google Keep, or even just a text file editor. These work well for people because they're already there and focus on quick and easy plain text capture. We could call this casual note-taking.
+
Back in the 2000s, hosted and self-hosted wikis became popular for easy, collaborative web publishing and knowledge management. Like Wikipedia, they could be used to build out hyperlinked knowledge repositories. Many wiki-based tools focused on their use as personal notebooks, one of the most influential examples being TiddlyWiki. The simple versatility of the wiki laid the groundwork for what we call "tools for thought" today.
+
+
When Notion appeared in the mid-2010s, it built on the idea of the wiki and introduced structured data management with flexible views that effectively gave you integrated, customizable versions of other productivity tools. Notion, Airtable, and others helped bring in the age of no-code and low-code tools, allowing knowledge workers and entrepreneurs to build their own "apps" or solutions to problems without traditionally building software. Notion brought it all together in a simple, user-friendly experience based around the core idea of wiki-like information management.
+
+
Meanwhile, a separate paradigm of note-taking tools emerged, focusing on the nested, tree-like structure of the outline. Perhaps inspired by tools like OmniOutliner and Org Mode for Emacs of the 2000s, Workflowy appeared in 2010 as a no-frills web-based outliner.
+
+
Obsidian arrived in 2020 and is a local app focusing on Markdown files stored on your filesystem. Obsidian has a large plugin ecosystem giving it a wide breadth of features, but it’s especially appealing to those that want to own their data. If you strip away the plugins, Obsidian is a pretty simple hyperlinked Markdown editor.
+
+
Most recently, a tool in early access called Tana caught my attention. Their key innovation is taking the linked outline model of Workflowy and introducing schemas for nodes, making them into structured data. This gives Tana the embedded database functionality of Notion and Airtable, a step towards bringing the two paradigms of note-taking software together towards powerful, malleable tools for thought.
+
+
How Treehouse Fits In
+
By now there's no shortage of options in this space, both as SaaS and open source. Take a look at this growing encyclopedia of note-taking tools. Like Notion and Tana, many of the apps listed are much more than note-taking tools. Some lean into the framing of "collaborative documents", and some are just categorized more generally as "productivity tools". Tana goes so far as to say "the everything OS".
+
Note-taking is just the beginning. It's a tangible gateway for something more powerful inherent to computing. Ever since Engelbart's mother of all demos, the computing revolution seems to start with powerful tools for thought, which are, at minimum, good note-taking tools.
+
+
Treehouse is a frontend and starter kit for anybody else that wants to explore this space with us. We will release a standalone product based on it soon, but most of the user-facing development will be done in the open source Treehouse project.
+
+
Today with Treehouse you can build your own Workflowy equivalent, but soon it will become more comparable to Tana and Notion with the open extensibility of Obsidian. That alone is pretty exciting to have in a minimal open source project, but I can't wait to show you what will come next.
+
Coming Soon
+
In the next post, I'll start getting technical and share details on the Treehouse project stack and architecture. If you can't wait, we do have documentation for you to check out.
+
Thanks for reading, and a big thanks to my sponsors for supporting this kind of open source work. Share your thoughts and favorite note-taking tools in the discussion thread for this post.
This release is a refinement of our initial release, fixing a number of bugs and adding interaction improvements. The look and feel of the UI was also updated with the start of a new CSS design system based on custom properties. Session locking was added for the live demo and GitHub backend so multiple devices/browsers/tabs don't clobber changes of each other. Documentation also got an upgrade with the start of a full guide on the website.
This first development release captures core functionality of the frontend to the point of being internally usable in the demo deployment. For developers, the project source layout, architecture, and backend API is defined in broad strokes in the right direction but is by no means stable.
+ ]]>
+
+ Fri, 03 Mar 2023 00:00:00 GMT
+
+
+ Welcome to Treehouse
+ https://treehouse.sh/blog/welcome/
+ https://treehouse.sh/blog/welcome/
+
+
+ I'm excited to announce the start of a new major project that I'll be sharing the journey of on this fancy new blog. The project is called Treehouse, which is starting as an open source note-taking frontend and will evolve into something much more.
+
+
We're creating a simple, hackable kernel of a note-taking tool as a web frontend that can be extended and customized by developers. Then we'll use that frontend to build a new kind of note-taking product. Today we have an early preview of our first minimum viable prototype of the frontend, and we'll be finishing up this release in the open on GitHub.
+
The open source project is a functional app frontend that you can deploy and back in various ways. For developers, this "bring your own backend" approach makes Treehouse a great starting point to build your own note-taking tool, just as we intend to do. We also have pre-made backends for those who want to use it with little-to-no programming. Either way, you'll always own your data, and now the system presenting it to you as well.
+
In this post, I'm going to talk about our minimum viable prototype and the approach we're taking with Treehouse as an open source project.
+
Out of the Box
+
While inspired by powerful tools like Notion, Tana, and Obsidian, we wanted to boil our initial goal down to the essentials while still being usable enough to use ourselves. As we continue to plan our prototype release milestone, we'd love to hear what you think is essential for you to have in a tool and platform like this, but here is what to expect as a baseline.
+
Outliner with Markdown Pages
+
At the heart of Treehouse is a graph-like system I've been developing called Manifold. This will play a big part in the long-term extensibility of Treehouse, which I'll talk more about in the future. For now, this maps very cleanly to the outliner model popularized by Workflowy, Tana, and others.
+
However, I'm also a fan of Notion-style pages and Obsidian's commitment to working with plain Markdown files. The Manifold system allows us to make certain nodes into Markdown pages. This hybrid model gets us the best of both worlds with room for even more possibilities later on.
+
Quick Add and Daily Notes
+
Being able to quickly get thoughts and information into the system has been a key aspect of every good note-taking system. This can be exposed a number of ways from browser extensions to desktop shortcuts, but what makes any "quick add" functionality quick is not having to think about where it will be organized.
+
Luckily, "daily notes" has become such a common pattern that many recent tools have managed daily notes built-in. This typical gives you a "today" note that is automatically organized into a calendar-like structure. This conveniently becomes the perfect destination for "quick add" notes.
+
Full-text Search
+
Whether you are an obsessive organizer or are too busy to take the time, solid full-text search is basically a necessity. It's how we quickly get to our data.
+
Out of the box we have a full-text search that doesn't require a backend. However, our pluggable backend will allow you to power search in a number of ways, and also opens up the ability to search into external systems that are important to you.
+
Built-in Backends
+
"Bring your own backend" is a critical part of the design of this project, but Treehouse also needs to be usable by people who prefer not to build their own backend. Our prototype release is planned to include a handful of built-in backends to get started with.
+
Our preview demo is using a localStorage backend, which works for development and special use cases. Of course, we will have a simple local filesystem backend for desktop scenarios, similar to Obsidian.
+
However, we're most excited for the GitHub backend. This functions similarly to the local filesystem backend, but it would be versioned in a central repository on your GitHub account and be accessible on any online platform.
+
Backends will not only let you extend storage, search, and authentication, but other aspects in the future.
+
Project Overview
+
The Treehouse codebase and open source project is as much the product as its features. The entire user and developer experience is being designed around simplicity and human ergonomics.
+
The Treehouse frontend is built with web technologies intended for use across web, mobile, and desktop platforms. The project is written in TypeScript using Deno as its JavaScript toolchain.
+
The JavaScript ecosystem is a mess, but Deno provides a forward-looking, self-contained toolchain that's easy to love. We actually have a zero Node.js policy and avoid NPM modules as much as possible.
+
With minimal dependencies and an ongoing effort to keep the codebase small, it will always be easy to understand the entire Treehouse system. This will be further supported with a focus on documentation, both API docs and guides.
+
We're using a permissive open source license, allowing you to use or change our code as you see fit. Contribution and participation is welcome, but so is simply consuming downstream.
+
The project is actively being developed but we keep a preview demo running off the main branch that should always be in working order.
+
Coming Soon
+
I'm excited to give you a deeper look at the project stack in a future post. For now, keep an eye out for the next post digging into the influences for Treehouse. We'll also try to answer "why another note-taking tool", and tease some long-term ideas for the future.
+
Lastly, I want to mention the project is being developed in the open, not just with the code on GitHub, but most of my work is streamed and archived on Twitch. Feel free to come and co-work with me.
+
Thanks for reading, and a big thanks to my sponsors for supporting this kind of open source work.
+ ]]>
+
+ Thu, 23 Feb 2023 00:00:00 GMT
+
+
+
\ No newline at end of file
diff --git a/blog/index.html b/blog/index.html
new file mode 100644
index 0000000..17fa897
--- /dev/null
+++ b/blog/index.html
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/blog/influences/index.html b/blog/influences/index.html
new file mode 100644
index 0000000..1500804
--- /dev/null
+++ b/blog/influences/index.html
@@ -0,0 +1,73 @@
+
+Treehouse Influences - Treehouse
Branching Out
Notes from the Treehouse
Treehouse Influences
Jeff Lindsay
April 20, 2023
Over the past few months, we've built a frontend framework for an elegant, quality outliner that's open source, extensible, and gives you control of your data. I’d like to share some of the design influences for the Treehouse frontend, which should give a sense of the unique direction Treehouse is going from here.
+
The biggest influences for Treehouse are Tana, Notion, and Obsidian. These three represent the state of the art of personal and collaborative information management, sometimes simplified as note-taking tools. However, "note-taking tools" sells them short as they go beyond note-taking and information management. For lack of a better descriptor, many consider them tools for thought.
+
From Notes to Tools for Thought
+
For most, note-taking brings to mind simple apps like Apple Notes and Google Keep, or even just a text file editor. These work well for people because they're already there and focus on quick and easy plain text capture. We could call this casual note-taking.
+
Back in the 2000s, hosted and self-hosted wikis became popular for easy, collaborative web publishing and knowledge management. Like Wikipedia, they could be used to build out hyperlinked knowledge repositories. Many wiki-based tools focused on their use as personal notebooks, one of the most influential examples being TiddlyWiki. The simple versatility of the wiki laid the groundwork for what we call "tools for thought" today.
+
+
When Notion appeared in the mid-2010s, it built on the idea of the wiki and introduced structured data management with flexible views that effectively gave you integrated, customizable versions of other productivity tools. Notion, Airtable, and others helped bring in the age of no-code and low-code tools, allowing knowledge workers and entrepreneurs to build their own "apps" or solutions to problems without traditionally building software. Notion brought it all together in a simple, user-friendly experience based around the core idea of wiki-like information management.
+
+
Meanwhile, a separate paradigm of note-taking tools emerged, focusing on the nested, tree-like structure of the outline. Perhaps inspired by tools like OmniOutliner and Org Mode for Emacs of the 2000s, Workflowy appeared in 2010 as a no-frills web-based outliner.
+
+
Obsidian arrived in 2020 and is a local app focusing on Markdown files stored on your filesystem. Obsidian has a large plugin ecosystem giving it a wide breadth of features, but it’s especially appealing to those that want to own their data. If you strip away the plugins, Obsidian is a pretty simple hyperlinked Markdown editor.
+
+
Most recently, a tool in early access called Tana caught my attention. Their key innovation is taking the linked outline model of Workflowy and introducing schemas for nodes, making them into structured data. This gives Tana the embedded database functionality of Notion and Airtable, a step towards bringing the two paradigms of note-taking software together towards powerful, malleable tools for thought.
+
+
How Treehouse Fits In
+
By now there's no shortage of options in this space, both as SaaS and open source. Take a look at this growing encyclopedia of note-taking tools. Like Notion and Tana, many of the apps listed are much more than note-taking tools. Some lean into the framing of "collaborative documents", and some are just categorized more generally as "productivity tools". Tana goes so far as to say "the everything OS".
+
Note-taking is just the beginning. It's a tangible gateway for something more powerful inherent to computing. Ever since Engelbart's mother of all demos, the computing revolution seems to start with powerful tools for thought, which are, at minimum, good note-taking tools.
+
+
Treehouse is a frontend and starter kit for anybody else that wants to explore this space with us. We will release a standalone product based on it soon, but most of the user-facing development will be done in the open source Treehouse project.
+
+
Today with Treehouse you can build your own Workflowy equivalent, but soon it will become more comparable to Tana and Notion with the open extensibility of Obsidian. That alone is pretty exciting to have in a minimal open source project, but I can't wait to show you what will come next.
+
Coming Soon
+
In the next post, I'll start getting technical and share details on the Treehouse project stack and architecture. If you can't wait, we do have documentation for you to check out.
+
Thanks for reading, and a big thanks to my sponsors for supporting this kind of open source work. Share your thoughts and favorite note-taking tools in the discussion thread for this post.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/blog/v0-1-0/index.html b/blog/v0-1-0/index.html
new file mode 100644
index 0000000..1b109c9
--- /dev/null
+++ b/blog/v0-1-0/index.html
@@ -0,0 +1,91 @@
+
+Release 0.1.0 - Treehouse
Branching Out
Notes from the Treehouse
Release 0.1.0
Jeff Lindsay
March 3, 2023
It begins...
+
This first development release captures core functionality of the frontend to the point of being internally usable in the demo deployment. For developers, the project source layout, architecture, and backend API is defined in broad strokes in the right direction but is by no means stable.
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/blog/v0-2-0/index.html b/blog/v0-2-0/index.html
new file mode 100644
index 0000000..c85ea97
--- /dev/null
+++ b/blog/v0-2-0/index.html
@@ -0,0 +1,77 @@
+
+Release 0.2.0 - Treehouse
Branching Out
Notes from the Treehouse
Release 0.2.0
Jeff Lindsay
March 27, 2023
New design system, GitHub session locking, and documentation
+
This release is a refinement of our initial release, fixing a number of bugs and adding interaction improvements. The look and feel of the UI was also updated with the start of a new CSS design system based on custom properties. Session locking was added for the live demo and GitHub backend so multiple devices/browsers/tabs don't clobber changes of each other. Documentation also got an upgrade with the start of a full guide on the website.
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/blog/v0-3-0/index.html b/blog/v0-3-0/index.html
new file mode 100644
index 0000000..e952882
--- /dev/null
+++ b/blog/v0-3-0/index.html
@@ -0,0 +1,101 @@
+
+Release 0.3.0 - Treehouse
Branching Out
Notes from the Treehouse
Release 0.3.0
Jeff Lindsay
May 17, 2023
New Node Types: Fields, Live Search, and References
+
This release we added some exciting new features: Fields, Live Search, and References. These new node types represent our first step into becoming much more than a simple outliner. Quality of live improvements include making the node menu easier to click, initial work towards a mobile view, and improving interactivity of the command palette. We also cleaned up all our UI elements to match our design system, allowing for better custom CSS support.
+
Update 7/10/2023: Live Search is now called Smart Nodes
A field is a node that can store a key-value pair. This introduces structured data to your nodes, letting you create nodes as data records. You can also search for nodes by field. This initial pass supports text values, but we'll soon provide more value types.
+
To turn a node into a field:
+
+
Indent underneath the node you want to contain the field, and type the field name
+
Command/Control + K to open the command palette, and choose "Create Field"
+
Add your field value in the value section
+
+
New Feature: Live Search
+
Live Search allows you to create search nodes where the children are auto-updating search results. Simply type a keyword, or use the format "fieldname:value" to filter by fields. The Live Search nodes will update automatically as your workspace content changes. This is a powerful way to view your data in new configurations.
+
To create a Live Search:
+
+
Create a new node where you want your search node, and type your search value
+
Command/Control + K to open the command palette, and choose "Create Search Node"
+
+
Tips: Search terms are case-insensitive, and you can filter on multiple fields (uses AND, not OR) like so: "fieldname:value fieldname:value".
+
New Feature: References
+
References are nodes that refer to another node and its children inline. They're sort of like symlinks on the filesystem. This lets you have a node exist in multiple places at once. References are differentiated from normal nodes with a dashed outline around their outline bullet. Deleting a reference node does not delete the node it points to. You may notice that Live Search results are reference nodes!
+
To create a reference node:
+
+
Select the node you want to make a reference to
+
Command/Control + K to open the command palette, and choose "Create Reference"
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/blog/v0-4-0/index.html b/blog/v0-4-0/index.html
new file mode 100644
index 0000000..b6a3eef
--- /dev/null
+++ b/blog/v0-4-0/index.html
@@ -0,0 +1,79 @@
+
+Release 0.4.0 - Treehouse
Branching Out
Notes from the Treehouse
Release 0.4.0
Jeff Lindsay
June 19, 2023
Mobile support and CSS themes
+
In this release we focused on making Treehouse more powerful and enjoyable to use from more places. Editing text on mobile is always a tricky prospect, but we've taken our first step to being mobile-friendly with customized navigation and easier touch targets.
+
White background a bit too bright? We've added several built-in themes (including sepia and dark mode) and we've made it super easy to create your own CSS themes using our component variables.
+
Otherwise, lots of quality of life improvements as usual, especially for fields and Smart Nodes.
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/blog/v0-5-0/index.html b/blog/v0-5-0/index.html
new file mode 100644
index 0000000..e4d9cd4
--- /dev/null
+++ b/blog/v0-5-0/index.html
@@ -0,0 +1,73 @@
+
+Release 0.5.0 - Treehouse
Branching Out
Notes from the Treehouse
Release 0.5.0
Jeff Lindsay
July 6, 2023
Tags, templates, and table view
+
Treehouse now supports tags and templates! For example, you can now create a template node with children and fields, name it "book", then any node tagged with #book will automatically get those fields and children. To turn a node into a template, select "Make Template" from the Command Palette. You can also tag nodes without an equivalent template. Tagging is done by simply adding hashtags to a node's text.
+
You can search for tagged nodes in the search bar using the hashtag notation (#book), however there is a known issue preventing you from searching for nodes by tag in Smart Nodes. This will be resolved in the next release, and in main much sooner.
+
You can now take a list of nodes with fields and turn them into an easy-to-scan table. Simply go to the parent node of the rows, open the Command Palette with Command+K, and choose "View as Table". We'll be adding more features to the table view in coming releases.
+
Double-quoted search terms now allow spaces and search results are a little tighter now. Last but not least we've added cut, copy, and paste commands for nodes, making it easier to duplicate and move nodes around.
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/blog/v0-6-0/index.html b/blog/v0-6-0/index.html
new file mode 100644
index 0000000..739afe5
--- /dev/null
+++ b/blog/v0-6-0/index.html
@@ -0,0 +1,74 @@
+
+Release 0.6.0 - Treehouse
Branching Out
Notes from the Treehouse
Release 0.6.0
Jeff Lindsay
July 20, 2023
New Document and Tab Views
+
In this release we're introducing two new views: Document view, and Tab view. Views are a powerful idea in Treehouse that can either be used to create embedded mini-apps or act as building blocks for you to make your own. These new views are an example of each.
+
Document view gives you a more conventional note-taking experience. In Document view each child node is rendered as a paragraph in the center of the panel. Documents support simple Markdown formatting like bold, italic, strikethrough, and ordered and unordered lists. Turn a node into a document by choosing "Make Document" from the Command Palette. Unlike other views, changing to Document view is a one-way action and nodes can't be converted back to other views.
+
Tab view renders each child node as a tab. Their children (grandchild nodes) are shown beneath when the tab is selected. These nodes will retain their view, so you can combine Tab view with others to create a more complex larger view of your data. In general, Tab view is useful for saving vertical space across several categories. Turn nodes into tabs by selecting the parent node and choose "View as Tabs" from the Command Palette. Since Tab view is read-only, you can modify tabs by switching back to List view.
+
We've also renamed Live Search Nodes to Smart Nodes, which can now be named separate from their query. This also resolves an issue where previously you couldn't use them for tag searches.
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/blog/v0-7-0/index.html b/blog/v0-7-0/index.html
new file mode 100644
index 0000000..0d08712
--- /dev/null
+++ b/blog/v0-7-0/index.html
@@ -0,0 +1,75 @@
+
+Release 0.7.0 - Treehouse
Branching Out
Notes from the Treehouse
Release 0.7.0
Jeff Lindsay
August 18, 2023
Descriptions, better paste, shortcut drawer
+
We're excited to be adding a handful of minor enhancements in this release. The first is node descriptions, which allow you to add small text below your node content, as part of the same node. Use it to add context or any kind of secondary information. To use, select your node, open the Command Palette with Command/Control + K, and select "Add Description".
+
We've made several improvements related to cut/copy/pasting text. Now if you paste text containing new lines, we'll convert each newline to a separate node. We've also fixed some bugs and UX flows.
+
Lastly, check out the keyboard shortcut drawer! We want it to be super easy to learn and use keyboard shortcuts and hope this helps.
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/web/static/blog/v0.1.0/index.html b/blog/v0.1.0/index.html
similarity index 100%
rename from web/static/blog/v0.1.0/index.html
rename to blog/v0.1.0/index.html
diff --git a/web/static/blog/v0.2.0/index.html b/blog/v0.2.0/index.html
similarity index 100%
rename from web/static/blog/v0.2.0/index.html
rename to blog/v0.2.0/index.html
diff --git a/web/static/blog/v0.3.0/index.html b/blog/v0.3.0/index.html
similarity index 100%
rename from web/static/blog/v0.3.0/index.html
rename to blog/v0.3.0/index.html
diff --git a/web/static/blog/v0.4.0/index.html b/blog/v0.4.0/index.html
similarity index 100%
rename from web/static/blog/v0.4.0/index.html
rename to blog/v0.4.0/index.html
diff --git a/blog/welcome/index.html b/blog/welcome/index.html
new file mode 100644
index 0000000..171a022
--- /dev/null
+++ b/blog/welcome/index.html
@@ -0,0 +1,81 @@
+
+Welcome to Treehouse - Treehouse
Branching Out
Notes from the Treehouse
Welcome to Treehouse
Jeff Lindsay
February 23, 2023
I'm excited to announce the start of a new major project that I'll be sharing the journey of on this fancy new blog. The project is called Treehouse, which is starting as an open source note-taking frontend and will evolve into something much more.
+
+
We're creating a simple, hackable kernel of a note-taking tool as a web frontend that can be extended and customized by developers. Then we'll use that frontend to build a new kind of note-taking product. Today we have an early preview of our first minimum viable prototype of the frontend, and we'll be finishing up this release in the open on GitHub.
+
The open source project is a functional app frontend that you can deploy and back in various ways. For developers, this "bring your own backend" approach makes Treehouse a great starting point to build your own note-taking tool, just as we intend to do. We also have pre-made backends for those who want to use it with little-to-no programming. Either way, you'll always own your data, and now the system presenting it to you as well.
+
In this post, I'm going to talk about our minimum viable prototype and the approach we're taking with Treehouse as an open source project.
+
Out of the Box
+
While inspired by powerful tools like Notion, Tana, and Obsidian, we wanted to boil our initial goal down to the essentials while still being usable enough to use ourselves. As we continue to plan our prototype release milestone, we'd love to hear what you think is essential for you to have in a tool and platform like this, but here is what to expect as a baseline.
+
Outliner with Markdown Pages
+
At the heart of Treehouse is a graph-like system I've been developing called Manifold. This will play a big part in the long-term extensibility of Treehouse, which I'll talk more about in the future. For now, this maps very cleanly to the outliner model popularized by Workflowy, Tana, and others.
+
However, I'm also a fan of Notion-style pages and Obsidian's commitment to working with plain Markdown files. The Manifold system allows us to make certain nodes into Markdown pages. This hybrid model gets us the best of both worlds with room for even more possibilities later on.
+
Quick Add and Daily Notes
+
Being able to quickly get thoughts and information into the system has been a key aspect of every good note-taking system. This can be exposed a number of ways from browser extensions to desktop shortcuts, but what makes any "quick add" functionality quick is not having to think about where it will be organized.
+
Luckily, "daily notes" has become such a common pattern that many recent tools have managed daily notes built-in. This typical gives you a "today" note that is automatically organized into a calendar-like structure. This conveniently becomes the perfect destination for "quick add" notes.
+
Full-text Search
+
Whether you are an obsessive organizer or are too busy to take the time, solid full-text search is basically a necessity. It's how we quickly get to our data.
+
Out of the box we have a full-text search that doesn't require a backend. However, our pluggable backend will allow you to power search in a number of ways, and also opens up the ability to search into external systems that are important to you.
+
Built-in Backends
+
"Bring your own backend" is a critical part of the design of this project, but Treehouse also needs to be usable by people who prefer not to build their own backend. Our prototype release is planned to include a handful of built-in backends to get started with.
+
Our preview demo is using a localStorage backend, which works for development and special use cases. Of course, we will have a simple local filesystem backend for desktop scenarios, similar to Obsidian.
+
However, we're most excited for the GitHub backend. This functions similarly to the local filesystem backend, but it would be versioned in a central repository on your GitHub account and be accessible on any online platform.
+
Backends will not only let you extend storage, search, and authentication, but other aspects in the future.
+
Project Overview
+
The Treehouse codebase and open source project is as much the product as its features. The entire user and developer experience is being designed around simplicity and human ergonomics.
+
The Treehouse frontend is built with web technologies intended for use across web, mobile, and desktop platforms. The project is written in TypeScript using Deno as its JavaScript toolchain.
+
The JavaScript ecosystem is a mess, but Deno provides a forward-looking, self-contained toolchain that's easy to love. We actually have a zero Node.js policy and avoid NPM modules as much as possible.
+
With minimal dependencies and an ongoing effort to keep the codebase small, it will always be easy to understand the entire Treehouse system. This will be further supported with a focus on documentation, both API docs and guides.
+
We're using a permissive open source license, allowing you to use or change our code as you see fit. Contribution and participation is welcome, but so is simply consuming downstream.
+
The project is actively being developed but we keep a preview demo running off the main branch that should always be in working order.
+
Coming Soon
+
I'm excited to give you a deeper look at the project stack in a future post. For now, keep an eye out for the next post digging into the influences for Treehouse. We'll also try to answer "why another note-taking tool", and tease some long-term ideas for the future.
+
Lastly, I want to mention the project is being developed in the open, not just with the code on GitHub, but most of my work is streamed and archived on Twitch. Feel free to come and co-work with me.
+
Thanks for reading, and a big thanks to my sponsors for supporting this kind of open source work.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
Treehouse is a frontend written in TypeScript made to be rendered in a browser or webview for building note-taking and information management tools. It is a "thick" frontend in that it holds most application state in-memory and executes user triggered commands to mutate that state. Persistence of that state, and a few other features, are expected to be provided by a "backend", which the frontend code interacts with via a backend adapter.
+Even without a backend adapter, the Treehouse frontend is still a fully functional application packaged as a JavaScript library that can be loaded onto any HTML page.
+
Architecture
+
The library exposes a setup() function that:
+
+
Takes a DOM document and backend adapter object
+
Sets up a central controller for the UI called Workbench
+
Loads a Workspace using the backend adapter
+
Registers built-in commands and keybindings
+
Uses Mithril.js to mount a top level Mithril component to the document
+
+
The UI is represented by a class called Workbench. This class orchestrates and provides most of the API for the rest of the system. The UI is broken down into Mithril components that implement the views for each part of the UI, pulling state from Workbench and connecting interactions to registered commands that represent all user actions. The Workbench and commands manipulate a Workspace, which represents the main data model for the system.
+
Stack
+
To avoid the complexity and dependency hell, Treehouse avoids most common JavaScript tooling such as Node.js and NPM. Instead, Treehouse uses Deno as a toolchain and otherwise avoids dependencies as much as possible. The other main dependency we have is Mithril.js, which was chosen for its simplicity and lack of further dependencies.
+
That said, there are other dependencies beyond this core stack which are chosen very deliberately. Out of the box search indexing depends on MiniSearch, and our most complex (but unavoidable) dependency is CodeMirror. We're very conscious of project dependencies, including development and toolchain dependencies.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/dev/2-data-model/index.html b/docs/dev/2-data-model/index.html
new file mode 100644
index 0000000..46fb8e0
--- /dev/null
+++ b/docs/dev/2-data-model/index.html
@@ -0,0 +1,12 @@
+
+Data Model - Treehouse
Documentation
Developer Guide
Data Model
+
The "document" for Treehouse is the Workspace, which is mostly a container for nodes. These nodes are based on a versatile and extensible API and data model called Manifold. In short, nodes:
+
+
have a unique ID
+
have a text name
+
can be children to other nodes
+
can have key-value attributes
+
can have components
+
+
Most importantly, nodes build a tree-like structure where each node can be extended with components. Components extend the state and functionality of a node. For example, a checkbox component can be added to a node. This gives it a state (checked or not) and allows the UI to render it differently (add a checkbox).
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/dev/3-user-actions/index.html b/docs/dev/3-user-actions/index.html
new file mode 100644
index 0000000..90ab2fa
--- /dev/null
+++ b/docs/dev/3-user-actions/index.html
@@ -0,0 +1,7 @@
+
+User Actions - Treehouse
Documentation
Developer Guide
User Actions
+
All user performable actions are modeled as commands and registered with a command system. Commands are functions with some extra metadata, like a user displayable name and system identifier. They can be called throughout the system by their system identifier, such as when a user clicks a something.
+
Menus are often defined upfront, usually by commands. Commands can have keybindings registered for them for keyboard shortcuts. These systems work together. For example, a menu item for a command will show the keybinding for it.
+
Commands can take arguments and usually take at least a single argument called a context. This is a way to represent state of the user’s current context, such as the currently selected node.
+
In addition to menus, keyboard shortcuts, and UI event handlers, there is a command palette the user can trigger to show all commands that can be run in the current context.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/dev/4-workbench-ui/index.html b/docs/dev/4-workbench-ui/index.html
new file mode 100644
index 0000000..235b43b
--- /dev/null
+++ b/docs/dev/4-workbench-ui/index.html
@@ -0,0 +1,10 @@
+
+Workbench UI - Treehouse
Documentation
Developer Guide
Workbench UI
+
Components
+
The workbench UI is made up of Mithril components, which are similar to React components. They take parameters, can have state, and specify a view using JSX. Instead of many atomic components like buttons and labels, Treehouse focuses on larger functional components that map to areas of the UI. Reusable visual elements are represented by CSS classes. Only if a reusable atomic visual element becomes so re-used and is too complex to re-implement is it made into a Mithril component.
+
All the Mithril components can be found under lib/ui. We use Typescript to make sure their parameters are typed so they're picked up by API documentation; no need for custom documentation for view components. Mithril components are just plain old JavaScript objects with a view method.
+
User Context
+
Most components are explicitly passed a reference to the Workbench, which they can use to execute commands or pull data in the current Workspace or Context. The Workbench provides a top level context that has the current selected node or nodes, the current panel, etc. However, when passing a Context around it can be given overrides. For example, you may be currently editing a particular node, but you use the mouse to perform a command on another node. The menu ensures the command will receive a Context with that node being acted on.
+
Design System
+
Our design system is inspired by projects like Pollen, where instead of generating CSS classes from JavaScript like Tailwind (which requires a compile step and Node.js based tooling), we simply use and override CSS custom properties. This means they can be used in inline styles as well. We also have a subset of common Tailwind utility classes defined, though using the custom properties.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/dev/5-backend-adapters/index.html b/docs/dev/5-backend-adapters/index.html
new file mode 100644
index 0000000..c66daf4
--- /dev/null
+++ b/docs/dev/5-backend-adapters/index.html
@@ -0,0 +1,49 @@
+
+Backend Adapters - Treehouse
Documentation
Developer Guide
Backend Adapters
+
Backend adapters are classes that implement the backend API for a given backend. If you wanted to make your own custom backend, you would implement your own backend adapter
+implementing the APIs you wish to hook into and pass that into the setup function when initializing Treehouse. We also have a handful of built-in adapters for public or
+well-known backend interfaces:
+
lib/backend/browser.ts
+
This backend implements the FileStorage API using localStorage. This means data will be stored in the browser for a particular device. It also implements search indexing
+using MiniSearch. It does not implement the Authenticator API.
+
lib/backend/github.ts
+
This backend implements the FileStorage API using the GitHub API to store data in a GitHub hosted Git repository. It also implements the Authenticator API against a
+script that can be hosted on CloudFlare Workers that implements an OAuth client for the GitHub API. This backend adapter does not implement a search index, it simply
+uses the browser implementation (MiniSearch).
+
lib/backend/filesystem.ts (coming soon)
+
This backend implements the FileStorage API using a local filesystem. Since there isn't a good standard filesystem API in browsers, this implementation operates against
+a simple REST API that can be implemented by a backend host process, such as Electron, Apptron, or something custom.
+
Writing an Adapter
+
An adapter is just an object that implements this API:
The Authenticator API is optional (and soon so might the SearchIndex API, always defaulting to MiniSearch). Typically a backend adapter will
+set auth, index, and files to this and implement each of those interfaces on that same object.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/dev/6-api-reference/index.html b/docs/dev/6-api-reference/index.html
new file mode 100644
index 0000000..a3d657a
--- /dev/null
+++ b/docs/dev/6-api-reference/index.html
@@ -0,0 +1,4 @@
+
+API Reference - Treehouse
Documentation
Developer Guide
API Reference
+
TypeScript documentation for Treehouse is available via Deno Land.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/dev/index.html b/docs/dev/index.html
new file mode 100644
index 0000000..828fe7c
--- /dev/null
+++ b/docs/dev/index.html
@@ -0,0 +1,84 @@
+
+Docs - Treehouse
Documentation
Developer Guide
Overview
+
Treehouse is a frontend written in TypeScript made to be rendered in a browser or webview for building note-taking and information management tools. It is a "thick" frontend in that it holds most application state in-memory and executes user triggered commands to mutate that state. Persistence of that state, and a few other features, are expected to be provided by a "backend", which the frontend code interacts with via a backend adapter.
+Even without a backend adapter, the Treehouse frontend is still a fully functional application packaged as a JavaScript library that can be loaded onto any HTML page.
+
Architecture
+
The library exposes a setup() function that:
+
+
Takes a DOM document and backend adapter object
+
Sets up a central controller for the UI called Workbench
+
Loads a Workspace using the backend adapter
+
Registers built-in commands and keybindings
+
Uses Mithril.js to mount a top level Mithril component to the document
+
+
The UI is represented by a class called Workbench. This class orchestrates and provides most of the API for the rest of the system. The UI is broken down into Mithril components that implement the views for each part of the UI, pulling state from Workbench and connecting interactions to registered commands that represent all user actions. The Workbench and commands manipulate a Workspace, which represents the main data model for the system.
+
Stack
+
To avoid the complexity and dependency hell, Treehouse avoids most common JavaScript tooling such as Node.js and NPM. Instead, Treehouse uses Deno as a toolchain and otherwise avoids dependencies as much as possible. The other main dependency we have is Mithril.js, which was chosen for its simplicity and lack of further dependencies.
+
That said, there are other dependencies beyond this core stack which are chosen very deliberately. Out of the box search indexing depends on MiniSearch, and our most complex (but unavoidable) dependency is CodeMirror. We're very conscious of project dependencies, including development and toolchain dependencies.
Data Model
+
The "document" for Treehouse is the Workspace, which is mostly a container for nodes. These nodes are based on a versatile and extensible API and data model called Manifold. In short, nodes:
+
+
have a unique ID
+
have a text name
+
can be children to other nodes
+
can have key-value attributes
+
can have components
+
+
Most importantly, nodes build a tree-like structure where each node can be extended with components. Components extend the state and functionality of a node. For example, a checkbox component can be added to a node. This gives it a state (checked or not) and allows the UI to render it differently (add a checkbox).
User Actions
+
All user performable actions are modeled as commands and registered with a command system. Commands are functions with some extra metadata, like a user displayable name and system identifier. They can be called throughout the system by their system identifier, such as when a user clicks a something.
+
Menus are often defined upfront, usually by commands. Commands can have keybindings registered for them for keyboard shortcuts. These systems work together. For example, a menu item for a command will show the keybinding for it.
+
Commands can take arguments and usually take at least a single argument called a context. This is a way to represent state of the user’s current context, such as the currently selected node.
+
In addition to menus, keyboard shortcuts, and UI event handlers, there is a command palette the user can trigger to show all commands that can be run in the current context.
Workbench UI
+
Components
+
The workbench UI is made up of Mithril components, which are similar to React components. They take parameters, can have state, and specify a view using JSX. Instead of many atomic components like buttons and labels, Treehouse focuses on larger functional components that map to areas of the UI. Reusable visual elements are represented by CSS classes. Only if a reusable atomic visual element becomes so re-used and is too complex to re-implement is it made into a Mithril component.
+
All the Mithril components can be found under lib/ui. We use Typescript to make sure their parameters are typed so they're picked up by API documentation; no need for custom documentation for view components. Mithril components are just plain old JavaScript objects with a view method.
+
User Context
+
Most components are explicitly passed a reference to the Workbench, which they can use to execute commands or pull data in the current Workspace or Context. The Workbench provides a top level context that has the current selected node or nodes, the current panel, etc. However, when passing a Context around it can be given overrides. For example, you may be currently editing a particular node, but you use the mouse to perform a command on another node. The menu ensures the command will receive a Context with that node being acted on.
+
Design System
+
Our design system is inspired by projects like Pollen, where instead of generating CSS classes from JavaScript like Tailwind (which requires a compile step and Node.js based tooling), we simply use and override CSS custom properties. This means they can be used in inline styles as well. We also have a subset of common Tailwind utility classes defined, though using the custom properties.
Backend Adapters
+
Backend adapters are classes that implement the backend API for a given backend. If you wanted to make your own custom backend, you would implement your own backend adapter
+implementing the APIs you wish to hook into and pass that into the setup function when initializing Treehouse. We also have a handful of built-in adapters for public or
+well-known backend interfaces:
+
lib/backend/browser.ts
+
This backend implements the FileStorage API using localStorage. This means data will be stored in the browser for a particular device. It also implements search indexing
+using MiniSearch. It does not implement the Authenticator API.
+
lib/backend/github.ts
+
This backend implements the FileStorage API using the GitHub API to store data in a GitHub hosted Git repository. It also implements the Authenticator API against a
+script that can be hosted on CloudFlare Workers that implements an OAuth client for the GitHub API. This backend adapter does not implement a search index, it simply
+uses the browser implementation (MiniSearch).
+
lib/backend/filesystem.ts (coming soon)
+
This backend implements the FileStorage API using a local filesystem. Since there isn't a good standard filesystem API in browsers, this implementation operates against
+a simple REST API that can be implemented by a backend host process, such as Electron, Apptron, or something custom.
+
Writing an Adapter
+
An adapter is just an object that implements this API:
The Authenticator API is optional (and soon so might the SearchIndex API, always defaulting to MiniSearch). Typically a backend adapter will
+set auth, index, and files to this and implement each of those interfaces on that same object.
API Reference
+
TypeScript documentation for Treehouse is available via Deno Land.
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/index.html b/docs/index.html
new file mode 100644
index 0000000..8c3e7fa
--- /dev/null
+++ b/docs/index.html
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/docs/project/1-contributing/index.html b/docs/project/1-contributing/index.html
new file mode 100644
index 0000000..31ab795
--- /dev/null
+++ b/docs/project/1-contributing/index.html
@@ -0,0 +1,10 @@
+
+Contributing - Treehouse
Documentation
Project Guide
Contributing
+
We'd love your contributions to the project, especially fixes to long-standing issues. If you'd like to work on something that necessitates discussion first, please create an issue so we can provide feedback and avoid stepping on each other's toes.
We welcome any kind of feedback about features you'd like, and we'd especially love to learn about your use case.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/project/2-roadmap/index.html b/docs/project/2-roadmap/index.html
new file mode 100644
index 0000000..cf8b0d0
--- /dev/null
+++ b/docs/project/2-roadmap/index.html
@@ -0,0 +1,4 @@
+
+Roadmap - Treehouse
Documentation
Project Guide
Roadmap
+
We're still formalizing our roadmap, how to organize it, share it, and collaborate with the community on it. For now, keep an eye on the GitHub issues and discussions.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/project/index.html b/docs/project/index.html
new file mode 100644
index 0000000..848524e
--- /dev/null
+++ b/docs/project/index.html
@@ -0,0 +1,10 @@
+
+Docs - Treehouse
Documentation
Project Guide
Contributing
+
We'd love your contributions to the project, especially fixes to long-standing issues. If you'd like to work on something that necessitates discussion first, please create an issue so we can provide feedback and avoid stepping on each other's toes.
We welcome any kind of feedback about features you'd like, and we'd especially love to learn about your use case.
Roadmap
+
We're still formalizing our roadmap, how to organize it, share it, and collaborate with the community on it. For now, keep an eye on the GitHub issues and discussions.
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/quickstart/1-using/index.html b/docs/quickstart/1-using/index.html
new file mode 100644
index 0000000..221bfa3
--- /dev/null
+++ b/docs/quickstart/1-using/index.html
@@ -0,0 +1,17 @@
+
+Using from CDN - Treehouse
Documentation
Quickstart
Using from CDN
+
First, you have to directly include Mithril and MiniSearch for now:
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/quickstart/2-building/index.html b/docs/quickstart/2-building/index.html
new file mode 100644
index 0000000..351d89b
--- /dev/null
+++ b/docs/quickstart/2-building/index.html
@@ -0,0 +1,10 @@
+
+Building from Source - Treehouse
Documentation
Quickstart
Building from Source
+
You can build from source by cloning or forking the project and installing Deno. Then you can run:
+
deno task bundle
+
This will produce a JS file you can use at web/static/lib/treehouse.min.js.
+
For development or debugging, you can run:
+
deno task serve
+
This will build and serve this website locally, including the live demo site at localhost:9000/demo, which will use
+and watch for changes in the lib source.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/quickstart/3-customizing/index.html b/docs/quickstart/3-customizing/index.html
new file mode 100644
index 0000000..e7fc51a
--- /dev/null
+++ b/docs/quickstart/3-customizing/index.html
@@ -0,0 +1,10 @@
+
+Customizing the Frontend - Treehouse
Documentation
Quickstart
Customizing the Frontend
+
The easiest aspect to customize is the look and feel, which you can do with custom CSS. Our CSS design system is built with
+custom properties, so you can include your own CSS and just override them with basic CSS.
+
Further customization might require you to fork and change the source. The source code is very straight forward, but learn
+more in the Developer Guide.
+
Lastly, of course, you can implement a custom backend adapter. Although there are just a few things to change this way,
+more extension points will be exposed in the future so you won't have to change source. Let us know in the forum what kind
+of extension points you'd like!
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/quickstart/index.html b/docs/quickstart/index.html
new file mode 100644
index 0000000..ef7689d
--- /dev/null
+++ b/docs/quickstart/index.html
@@ -0,0 +1,30 @@
+
+Docs - Treehouse
Documentation
Quickstart
Using from CDN
+
First, you have to directly include Mithril and MiniSearch for now:
You can build from source by cloning or forking the project and installing Deno. Then you can run:
+
deno task bundle
+
This will produce a JS file you can use at web/static/lib/treehouse.min.js.
+
For development or debugging, you can run:
+
deno task serve
+
This will build and serve this website locally, including the live demo site at localhost:9000/demo, which will use
+and watch for changes in the lib source.
Customizing the Frontend
+
The easiest aspect to customize is the look and feel, which you can do with custom CSS. Our CSS design system is built with
+custom properties, so you can include your own CSS and just override them with basic CSS.
+
Further customization might require you to fork and change the source. The source code is very straight forward, but learn
+more in the Developer Guide.
+
Lastly, of course, you can implement a custom backend adapter. Although there are just a few things to change this way,
+more extension points will be exposed in the future so you won't have to change source. Let us know in the forum what kind
+of extension points you'd like!
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/01-what-is-treehouse/index.html b/docs/user/01-what-is-treehouse/index.html
new file mode 100644
index 0000000..5e4a7a1
--- /dev/null
+++ b/docs/user/01-what-is-treehouse/index.html
@@ -0,0 +1,4 @@
+
+What is Treehouse? - Treehouse
Documentation
User Guide
What is Treehouse?
+
Treehouse is an outline editor, which you can think of as a nested bulleted list. Each bullet item is called a node. You can use the nodes to create nested layers of folders and notes.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/02-data-storage/index.html b/docs/user/02-data-storage/index.html
new file mode 100644
index 0000000..03e772d
--- /dev/null
+++ b/docs/user/02-data-storage/index.html
@@ -0,0 +1,11 @@
+
+Data Storage - Treehouse
Documentation
User Guide
Data Storage
+
Localstorage
+
By default, data is stored in your browser’s local storage. That means that the data is linked to your specific browser and device. If you clear your browser cache, the data will be wiped.
+
GitHub
+
If you choose to log in with GitHub, we’ll create a repository and store your data there.
+
To store your workspace, we will create a public repository called .treehouse.sh if it doesn’t already exist. If you want to make the repository private, you can do so in GitHub.
+
To switch back to the local storage backend, log out from the Options menu.
+
Multiple sessions
+
If you log in to Treehouse from multiple devices, the most recent device will have edit and save access. Other sessions will be prompted to refresh the page; if/when you do so, that session becomes the new active session.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/03-nodes/index.html b/docs/user/03-nodes/index.html
new file mode 100644
index 0000000..5e6ec8c
--- /dev/null
+++ b/docs/user/03-nodes/index.html
@@ -0,0 +1,34 @@
+
+Nodes - Treehouse
Documentation
User Guide
Nodes
+
Your Workspace is your top level node, which all other nodes are nested under.
+
Learn how to manage and edit your nodes.
+
Add
+
You can add a new node in a few ways.
+
+
Hit ENTER on your keyboard and start typing.
+
Click into the blank area next to the plus symbol and start typing.
+
+
Indent
+
+
Indent a node using TAB ↹
+
Outdent a node using SHIFT + TAB ⇧ ↹
+
+
Move
+
+
Move a node up with SHIFT + COMMAND + UP ARROW ⇧ ⌘ ↑
+
Move a node down with SHIFT + COMMAND + DOWN ARROW ⇧ ⌘ ↓
+
+
Expand or collapse a node
+
If a node bullet has an outline around it, that’s an indication that it has nested content that is currently hidden. Click the node to expand it.
+
Click an expanded node once to collapse it.
+
Node menu
+
When you hover over a node, you’ll see a menu to the left of the node bullet. Click it to access node options, such as indent/outdent, open in a panel, etc.
+
Node formatting
+
Currently, all nodes are formatted as plain text. You can, however, add a checkbox to a node. With a node selected, open the command palette (⌘ K) and select "Add checkbox".
+
View
+
Double click a node to zoom in.
+
Side-by-side (Panel) view
+
To view two nodes side-by-side:
+
Open the node you want to be in the righthand panel. From its menu, choose “Open in New Panel”.
+
You can close or expand either panel to return to a single panel view.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/04-fields/index.html b/docs/user/04-fields/index.html
new file mode 100644
index 0000000..269b1f7
--- /dev/null
+++ b/docs/user/04-fields/index.html
@@ -0,0 +1,11 @@
+
+Fields - Treehouse
Documentation
User Guide
Fields
+
A field is a node that can store structured information. Fields provide your data with structure, and allow for special search syntax (see Smart Nodes).
+
Create a field
+
To add a field to a node:
+
+
Indent underneath the node you want to contain the field, and type the field name
+
Use Command/Control + K to open the command palette, and choose "Create field"
+
Add your field value in the value section
+
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/05-smart-nodes/index.html b/docs/user/05-smart-nodes/index.html
new file mode 100644
index 0000000..fe512a1
--- /dev/null
+++ b/docs/user/05-smart-nodes/index.html
@@ -0,0 +1,15 @@
+
+Smart Nodes - Treehouse
Documentation
User Guide
Smart Nodes
+
Smart Nodes allow you to create an auto-updating search of all the nodes in your workspace. Simply type your search term, or use the format "fieldname:valuename" to filter specifically by field values. The Smart Node will update automatically as your node content changes. This is a simple but super powerful way to view your data in new configurations.
+
To create a Smart Node:
+
+
Create a new node where you want your Smart Node, and type your search value
+
Use Command/Control + K to open the command palette, and choose "Create Smart Node"
+
+
Tips for using Smart Nodes
+
+
You can filter on multiple fieldname values (using AND, not OR) like so: "fieldname:valuename fieldname:valuename" etc.
+
If your fieldname has spaces, put quotes around it (fieldname:"Value name")
+
Search terms are case-insensitive
+
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/06-tags/index.html b/docs/user/06-tags/index.html
new file mode 100644
index 0000000..2674541
--- /dev/null
+++ b/docs/user/06-tags/index.html
@@ -0,0 +1,13 @@
+
+Tags - Treehouse
Documentation
User Guide
Tags
+
Tags are versatile metadata. Here are some of the ways you can use them:
+
+
Conduct a keyword search in the searchbar
+
Use in Smart Nodes to create custom views
+
Use to add a template to a node
+
+
Create a tag
+
On any node, with your cursor at the end of the text, type "#" then the tag name to create a tag. Any tags you have already created will show up in an autocomplete list when you type "#".
+
Delete a tag
+
Click on the tag and press Backspace on your keyboard to delete it.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/07-templates/index.html b/docs/user/07-templates/index.html
new file mode 100644
index 0000000..dfbf642
--- /dev/null
+++ b/docs/user/07-templates/index.html
@@ -0,0 +1,13 @@
+
+Templates - Treehouse
Documentation
User Guide
Templates
+
Templates allow you to add a set of predefined fields and other child nodes to a node simply by adding a tag to that node.
+
Create and use a template
+
In this example, we'll create a template called "book" with child fields Author and Release Date.
+
+
Wherever you want to store your template, type "book" in the node.
+
Add child fields Author and Release Date, and leave the value fields empty. (To turn a regular node into a Field: Command Palette > Create field)
+
With your cursor in the parent "book" node, open the Command Palette (Command/Control+K) and choose Make Template.
+
Create a list of books wherever you'd like, if you haven't already. With your cursor on one if the individual books, type "#book" and hit ENTER to create the tag.
+
Check out one of your book nodes—it should have the child fields Author and Release Date that you set up in your template.
+
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/07.1-views/index.html b/docs/user/07.1-views/index.html
new file mode 100644
index 0000000..0d83295
--- /dev/null
+++ b/docs/user/07.1-views/index.html
@@ -0,0 +1,32 @@
+
+Views - Treehouse
Documentation
User Guide
Views
+
You can view your data in many different ways using commands in the Command Palette.
+
Document
+
Converting your node(s) to document view centers them in the panel, styles the nodes like paragraphs, and supports basic Markdown formatting.
+
Note: document view is a one-way conversion. Document nodes can't be converted back to List (outline) view.
+
Create a Document
+
With your cursor on the parent node of the node(s) you want to convert to a document, open the Command Palette and select Make Document.
+
Markdown formatting
+
Text styles
+
*italic* or _italic_
+**bold**
+~~strikethrough~~
+
+
Lists
+
- unordered lists
+* with any of
++ these characters
+
+1. ordered
+2. lists
+
+
Table
+
Useful for a set of nodes with common fields. Node fields will become columns.
+
Use Table View
+
With your cursor on the parent node of the nodes you want to convert to a document, open the Command Palette and select View As Table.
+
To revert back to List (outline) view, select the parent node and choose "View as List" from the Command Palette.
+
Tabs
+
The tab view tidies up a common group of nodes, allowing you to view one tab at a time.
+
Use Tabs View
+
With your cursor on the parent node of the nodes you want to convert to a document, open the Command Palette and select View As Tabs.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/08-calendar/index.html b/docs/user/08-calendar/index.html
new file mode 100644
index 0000000..a0a51c8
--- /dev/null
+++ b/docs/user/08-calendar/index.html
@@ -0,0 +1,6 @@
+
+Calendar - Treehouse
Documentation
User Guide
Calendar
+
The Calendar is a default node that is automatically generated for every workspace. Nodes inside the calendar are grouped by date, week, then year.
+
Today
+
The Today shortcut allows you to quickly view the node for Today in your Calendar.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/09-quick-add/index.html b/docs/user/09-quick-add/index.html
new file mode 100644
index 0000000..72e71ca
--- /dev/null
+++ b/docs/user/09-quick-add/index.html
@@ -0,0 +1,4 @@
+
+Quick Add - Treehouse
Documentation
User Guide
Quick Add
+
Quick Add in the top navigation is a shortcut that opens a modal in which you can jot a quick note. It will be added to today’s date in your Calendar.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/10-command-palette/index.html b/docs/user/10-command-palette/index.html
new file mode 100644
index 0000000..c4d0d70
--- /dev/null
+++ b/docs/user/10-command-palette/index.html
@@ -0,0 +1,4 @@
+
+Command Palette - Treehouse
Documentation
User Guide
Command Palette
+
With a node selected, open the command palette (⌘ K) to view all the available actions for that node.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/11-keyboard-shortcuts/index.html b/docs/user/11-keyboard-shortcuts/index.html
new file mode 100644
index 0000000..174a19b
--- /dev/null
+++ b/docs/user/11-keyboard-shortcuts/index.html
@@ -0,0 +1,36 @@
+
+Keyboard Shortcuts - Treehouse
Documentation
User Guide
Keyboard Shortcuts
+
+
+
indent
+
↹
+
+
+
outdent
+
⇧ ↹
+
+
+
move node up
+
⇧ ⌘ ↑
+
+
+
move node down
+
⇧ ⌘ ↓
+
+
+
delete node
+
⇧ ⌘ ⌫
+
+
+
add or remove checkbox
+
⌘ ↵
+
+
+
mark checkbox as done
+
⌘ ↵
+
+
+
open command palette
+
⌘ K
+
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/12-css-theming/index.html b/docs/user/12-css-theming/index.html
new file mode 100644
index 0000000..4182fe8
--- /dev/null
+++ b/docs/user/12-css-theming/index.html
@@ -0,0 +1,104 @@
+
+CSS Theming - Treehouse
Documentation
User Guide
CSS Theming
+
You can create your own custom theme for Treehouse using our built-in variables a.k.a. custom properties.
+
Create a theme
+
+
Add a top level folder called "ext" to your treehouse.sh repository
+
Create a CSS file inside the ext folder
+
Use the format below to populate the variables with hex code values. Tip: Create color variables inside the root block to reuse color styles between custom properties.
If you have multiple CSS files you want to swap between, append ".disabled" to the end of the unused CSS filename(s).
+
Variable Reference
+
+
Variable
Description
+
+
--font
+
Global font definition. Change the font itself but not sizes or styles with this.
+
+
+
--color-primary
+
Background color of primary button
+
+
+
--color-background
+
Background color of main panels, menus, and modals
+
+
+
--color-background-sidebar
+
Background color of sidebar navigation
+
+
+
--color-icon
+
High contrast color used for primary icons. For example: icons in the top navigation
+
+
+
--color-icon-secondary
+
Low-contrast color used for secondary icons
+
+
+
--color-nav-label
+
Used for top and sidebar navigation labels
+
+
+
--color-text
+
Default text color used for body text, navigation, and primary icons
+
+
+
--color-text-placeholder
+
Lower-contrast color used for placeholder text in inputs
+
+
+
--color-text-secondary
+
Lower-contrast color used for secondary text
+
+
+
--color-highlight
+
Lowest-contrast color to subtly highlight selected item in the menu, search, and command palette
+
+
+
--color-node-handle
+
Bullet color for nodes (a.k.a. the node handle)
+
+
+
--color-node-handle-secondary
+
Lower-contrast accent color on node handles. For instance, the outer filled circle on a node indicating collapsed children.
+
+
+
--color-outline
+
High contrast border color on pop-over containers like modals and menus.
+
+
+
--color-outline-secondary
+
Lower contrast border color where less extreme contrast is needed, such as the divider between panels and the navigation.
+
+
+
Fonts
+
To use a non-system font, you may import a font into your CSS file using either the @import method or the @font-face method.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/13-backend-extensions/index.html b/docs/user/13-backend-extensions/index.html
new file mode 100644
index 0000000..f5fb46f
--- /dev/null
+++ b/docs/user/13-backend-extensions/index.html
@@ -0,0 +1,12 @@
+
+Backend Extensions - Treehouse
Documentation
User Guide
Backend Extensions
+
Backends can change or extend how a Treehouse application behaves and are exposed to the frontend via adapters.
+
Workspace Storage
+
The Treehouse frontend uses its backend adapter to store the state of your workspace into a JSON document. The backend can decide where and how that JSON document is stored. For example, the Browser backend adapter will store the JSON into localStorage.
+
User Authentication
+
An optional capability of the frontend is to know whether a particular user is authenticated. You typically want user authentication for cloud or web-based deployments, but not necessarily for a local desktop app.
+
Search Indexing
+
Out of the box, Treehouse will index your workspace for full-text search using Minisearch,
+which will be good enough for many cases. However, a backend adapter can choose to hook into the index and searching
+so that you could have a more powerful search index such as ElasticSearch.
+
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/docs/user/index.html b/docs/user/index.html
new file mode 100644
index 0000000..2501229
--- /dev/null
+++ b/docs/user/index.html
@@ -0,0 +1,260 @@
+
+Docs - Treehouse
Documentation
User Guide
What is Treehouse?
+
Treehouse is an outline editor, which you can think of as a nested bulleted list. Each bullet item is called a node. You can use the nodes to create nested layers of folders and notes.
Data Storage
+
Localstorage
+
By default, data is stored in your browser’s local storage. That means that the data is linked to your specific browser and device. If you clear your browser cache, the data will be wiped.
+
GitHub
+
If you choose to log in with GitHub, we’ll create a repository and store your data there.
+
To store your workspace, we will create a public repository called .treehouse.sh if it doesn’t already exist. If you want to make the repository private, you can do so in GitHub.
+
To switch back to the local storage backend, log out from the Options menu.
+
Multiple sessions
+
If you log in to Treehouse from multiple devices, the most recent device will have edit and save access. Other sessions will be prompted to refresh the page; if/when you do so, that session becomes the new active session.
Nodes
+
Your Workspace is your top level node, which all other nodes are nested under.
+
Learn how to manage and edit your nodes.
+
Add
+
You can add a new node in a few ways.
+
+
Hit ENTER on your keyboard and start typing.
+
Click into the blank area next to the plus symbol and start typing.
+
+
Indent
+
+
Indent a node using TAB ↹
+
Outdent a node using SHIFT + TAB ⇧ ↹
+
+
Move
+
+
Move a node up with SHIFT + COMMAND + UP ARROW ⇧ ⌘ ↑
+
Move a node down with SHIFT + COMMAND + DOWN ARROW ⇧ ⌘ ↓
+
+
Expand or collapse a node
+
If a node bullet has an outline around it, that’s an indication that it has nested content that is currently hidden. Click the node to expand it.
+
Click an expanded node once to collapse it.
+
Node menu
+
When you hover over a node, you’ll see a menu to the left of the node bullet. Click it to access node options, such as indent/outdent, open in a panel, etc.
+
Node formatting
+
Currently, all nodes are formatted as plain text. You can, however, add a checkbox to a node. With a node selected, open the command palette (⌘ K) and select "Add checkbox".
+
View
+
Double click a node to zoom in.
+
Side-by-side (Panel) view
+
To view two nodes side-by-side:
+
Open the node you want to be in the righthand panel. From its menu, choose “Open in New Panel”.
+
You can close or expand either panel to return to a single panel view.
Fields
+
A field is a node that can store structured information. Fields provide your data with structure, and allow for special search syntax (see Smart Nodes).
+
Create a field
+
To add a field to a node:
+
+
Indent underneath the node you want to contain the field, and type the field name
+
Use Command/Control + K to open the command palette, and choose "Create field"
+
Add your field value in the value section
+
Smart Nodes
+
Smart Nodes allow you to create an auto-updating search of all the nodes in your workspace. Simply type your search term, or use the format "fieldname:valuename" to filter specifically by field values. The Smart Node will update automatically as your node content changes. This is a simple but super powerful way to view your data in new configurations.
+
To create a Smart Node:
+
+
Create a new node where you want your Smart Node, and type your search value
+
Use Command/Control + K to open the command palette, and choose "Create Smart Node"
+
+
Tips for using Smart Nodes
+
+
You can filter on multiple fieldname values (using AND, not OR) like so: "fieldname:valuename fieldname:valuename" etc.
+
If your fieldname has spaces, put quotes around it (fieldname:"Value name")
+
Search terms are case-insensitive
+
Tags
+
Tags are versatile metadata. Here are some of the ways you can use them:
+
+
Conduct a keyword search in the searchbar
+
Use in Smart Nodes to create custom views
+
Use to add a template to a node
+
+
Create a tag
+
On any node, with your cursor at the end of the text, type "#" then the tag name to create a tag. Any tags you have already created will show up in an autocomplete list when you type "#".
+
Delete a tag
+
Click on the tag and press Backspace on your keyboard to delete it.
Templates
+
Templates allow you to add a set of predefined fields and other child nodes to a node simply by adding a tag to that node.
+
Create and use a template
+
In this example, we'll create a template called "book" with child fields Author and Release Date.
+
+
Wherever you want to store your template, type "book" in the node.
+
Add child fields Author and Release Date, and leave the value fields empty. (To turn a regular node into a Field: Command Palette > Create field)
+
With your cursor in the parent "book" node, open the Command Palette (Command/Control+K) and choose Make Template.
+
Create a list of books wherever you'd like, if you haven't already. With your cursor on one if the individual books, type "#book" and hit ENTER to create the tag.
+
Check out one of your book nodes—it should have the child fields Author and Release Date that you set up in your template.
+
Views
+
You can view your data in many different ways using commands in the Command Palette.
+
Document
+
Converting your node(s) to document view centers them in the panel, styles the nodes like paragraphs, and supports basic Markdown formatting.
+
Note: document view is a one-way conversion. Document nodes can't be converted back to List (outline) view.
+
Create a Document
+
With your cursor on the parent node of the node(s) you want to convert to a document, open the Command Palette and select Make Document.
+
Markdown formatting
+
Text styles
+
*italic* or _italic_
+**bold**
+~~strikethrough~~
+
+
Lists
+
- unordered lists
+* with any of
++ these characters
+
+1. ordered
+2. lists
+
+
Table
+
Useful for a set of nodes with common fields. Node fields will become columns.
+
Use Table View
+
With your cursor on the parent node of the nodes you want to convert to a document, open the Command Palette and select View As Table.
+
To revert back to List (outline) view, select the parent node and choose "View as List" from the Command Palette.
+
Tabs
+
The tab view tidies up a common group of nodes, allowing you to view one tab at a time.
+
Use Tabs View
+
With your cursor on the parent node of the nodes you want to convert to a document, open the Command Palette and select View As Tabs.
Calendar
+
The Calendar is a default node that is automatically generated for every workspace. Nodes inside the calendar are grouped by date, week, then year.
+
Today
+
The Today shortcut allows you to quickly view the node for Today in your Calendar.
Quick Add
+
Quick Add in the top navigation is a shortcut that opens a modal in which you can jot a quick note. It will be added to today’s date in your Calendar.
Command Palette
+
With a node selected, open the command palette (⌘ K) to view all the available actions for that node.
Keyboard Shortcuts
+
+
+
indent
+
↹
+
+
+
outdent
+
⇧ ↹
+
+
+
move node up
+
⇧ ⌘ ↑
+
+
+
move node down
+
⇧ ⌘ ↓
+
+
+
delete node
+
⇧ ⌘ ⌫
+
+
+
add or remove checkbox
+
⌘ ↵
+
+
+
mark checkbox as done
+
⌘ ↵
+
+
+
open command palette
+
⌘ K
+
+
CSS Theming
+
You can create your own custom theme for Treehouse using our built-in variables a.k.a. custom properties.
+
Create a theme
+
+
Add a top level folder called "ext" to your treehouse.sh repository
+
Create a CSS file inside the ext folder
+
Use the format below to populate the variables with hex code values. Tip: Create color variables inside the root block to reuse color styles between custom properties.
If you have multiple CSS files you want to swap between, append ".disabled" to the end of the unused CSS filename(s).
+
Variable Reference
+
+
Variable
Description
+
+
--font
+
Global font definition. Change the font itself but not sizes or styles with this.
+
+
+
--color-primary
+
Background color of primary button
+
+
+
--color-background
+
Background color of main panels, menus, and modals
+
+
+
--color-background-sidebar
+
Background color of sidebar navigation
+
+
+
--color-icon
+
High contrast color used for primary icons. For example: icons in the top navigation
+
+
+
--color-icon-secondary
+
Low-contrast color used for secondary icons
+
+
+
--color-nav-label
+
Used for top and sidebar navigation labels
+
+
+
--color-text
+
Default text color used for body text, navigation, and primary icons
+
+
+
--color-text-placeholder
+
Lower-contrast color used for placeholder text in inputs
+
+
+
--color-text-secondary
+
Lower-contrast color used for secondary text
+
+
+
--color-highlight
+
Lowest-contrast color to subtly highlight selected item in the menu, search, and command palette
+
+
+
--color-node-handle
+
Bullet color for nodes (a.k.a. the node handle)
+
+
+
--color-node-handle-secondary
+
Lower-contrast accent color on node handles. For instance, the outer filled circle on a node indicating collapsed children.
+
+
+
--color-outline
+
High contrast border color on pop-over containers like modals and menus.
+
+
+
--color-outline-secondary
+
Lower contrast border color where less extreme contrast is needed, such as the divider between panels and the navigation.
+
+
+
Fonts
+
To use a non-system font, you may import a font into your CSS file using either the @import method or the @font-face method.
Backend Extensions
+
Backends can change or extend how a Treehouse application behaves and are exposed to the frontend via adapters.
+
Workspace Storage
+
The Treehouse frontend uses its backend adapter to store the state of your workspace into a JSON document. The backend can decide where and how that JSON document is stored. For example, the Browser backend adapter will store the JSON into localStorage.
+
User Authentication
+
An optional capability of the frontend is to know whether a particular user is authenticated. You typically want user authentication for cloud or web-based deployments, but not necessarily for a local desktop app.
+
Search Indexing
+
Out of the box, Treehouse will index your workspace for full-text search using Minisearch,
+which will be good enough for many cases. However, a backend adapter can choose to hook into the index and searching
+so that you could have a more powerful search index such as ElasticSearch.
Stay in touch
Sign up for our mailing list to receive updates on the project.
We don't share your email.
\ No newline at end of file
diff --git a/web/static/halftone_green.png b/halftone_green.png
similarity index 100%
rename from web/static/halftone_green.png
rename to halftone_green.png
diff --git a/web/static/halftone_white.png b/halftone_white.png
similarity index 100%
rename from web/static/halftone_white.png
rename to halftone_white.png
diff --git a/web/static/halftone_white_15.png b/halftone_white_15.png
similarity index 100%
rename from web/static/halftone_white_15.png
rename to halftone_white_15.png
diff --git a/web/static/halftone_white_50.png b/halftone_white_50.png
similarity index 100%
rename from web/static/halftone_white_50.png
rename to halftone_white_50.png
diff --git a/web/static/icon.png b/icon.png
similarity index 100%
rename from web/static/icon.png
rename to icon.png
diff --git a/index.html b/index.html
new file mode 100644
index 0000000..307e21f
--- /dev/null
+++ b/index.html
@@ -0,0 +1,2 @@
+
+Treehouse: Note-taking Frontend
A lightweight note-taking tool to make your own
An open source note-taking frontend to extend and customize. Bring your own backend or configure a built-in backend to get started.
-
- )
-}
\ No newline at end of file
diff --git a/web/_vendor/codemirror/Makefile b/web/_vendor/codemirror/Makefile
deleted file mode 100644
index 3292cc2..0000000
--- a/web/_vendor/codemirror/Makefile
+++ /dev/null
@@ -1,3 +0,0 @@
-
-bundle:
- npm install && esbuild codemirror.ts --bundle --outfile=../../static/vnd/codemirror-6.0.1.min.js --format=esm --minify
\ No newline at end of file
diff --git a/web/_vendor/codemirror/codemirror.ts b/web/_vendor/codemirror/codemirror.ts
deleted file mode 100644
index c7b25c2..0000000
--- a/web/_vendor/codemirror/codemirror.ts
+++ /dev/null
@@ -1,130 +0,0 @@
-import { EditorState } from "@codemirror/state"
-import { placeholder as placeholderPlugin, EditorView, ViewUpdate } from "@codemirror/view"
-import { markdown, markdownLanguage } from "@codemirror/lang-markdown"
-import { javascript } from "@codemirror/lang-javascript"
-import { defaultHighlightStyle, syntaxHighlighting} from "@codemirror/language"
-import { classHighlighter } from "@lezer/highlight"
-
-const proxyMerge = (...objects: any[]) => {
- const extra = objects.slice(1);
-
- return new Proxy(objects[0], {
- get: (target, name) => {
- const obj = extra.find(o => o[name]);
- return obj
- ? obj[name]
- : target[name];
- },
- });
-};
-
-export class Editor {
- view: EditorView;
- parent: HTMLElement;
- oninput?: Function;
- onblur?: Function;
- onfocus?: Function;
- onkeydown?: Function;
-
- constructor(parent: HTMLElement, value: string, placeholder?: string) {
- this.parent = parent;
- this.view = new EditorView({
- parent: parent,
- state: EditorState.create({
- doc: value,
- extensions: [
- EditorView.lineWrapping,
- placeholderPlugin(placeholder),
- syntaxHighlighting(defaultHighlightStyle),
- syntaxHighlighting(classHighlighter),
- markdown({
- defaultCodeLanguage: javascript(),
- base: markdownLanguage
- }),
- EditorView.updateListener.of((v: ViewUpdate) => {
- if (v.docChanged && this.oninput) {
- this.oninput(proxyMerge(new CustomEvent("UpdateEvent"), {target: this}));
- if (m) m.redraw();
- }
- }),
- EditorView.domEventHandlers({
- // input: (event, view) => {
- // if (this.oninput) {
- // this.oninput(proxyMerge(event, {target: this}));
- // if (m) m.redraw();
- // }
- // },
- blur: (event, view) => {
- if (this.onblur) {
- this.onblur(proxyMerge(event, {target: this}));
- if (m) m.redraw();
- }
- },
- focus: (event, view) => {
- if (this.onfocus) {
- this.onfocus(proxyMerge(event, {target: this}));
- if (m) m.redraw();
- }
- },
- keydown: (event, view) => {
- if (this.onkeydown) {
- let defaultPrevented = false;
- this.onkeydown(proxyMerge(event, {
- target: this,
- preventDefault: () => defaultPrevented = true,
- stopPropagation: () => null,
- }));
- if (m) m.redraw();
- return defaultPrevented;
- }
- },
- }),
- ]
- })
- });
- }
-
- get value(): string {
- return this.view.state.doc.toString();
- }
-
- set value(v: string) {
- if (v !== this.value) {
- const update = this.view.state.update({changes: {from: 0, to: this.view.state.doc.length, insert: v}});
- this.view.update([update]);
- }
- }
-
- get selectionStart(): number {
- return this.view.state.selection.main.anchor;
- }
-
- get selectionEnd(): number {
- return this.view.state.selection.main.head;
- }
-
- get coordsAtCursor(): any {
- return this.view.coordsAtPos(this.view.state.selection.main.head);
- }
-
- focus() {
- this.view.focus();
- }
-
- blur() {
- this.view.contentDOM.blur();
- }
-
- setSelectionRange(start: number, end: number) {
- this.view.dispatch({
- selection: {
- anchor: start,
- head: end,
- },
- });
- }
-
- getBoundingClientRect(): any {
- return this.parent.getBoundingClientRect()
- }
-}
diff --git a/web/_vendor/codemirror/package.json b/web/_vendor/codemirror/package.json
deleted file mode 100644
index 603b0b1..0000000
--- a/web/_vendor/codemirror/package.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "dependencies": {
- "@codemirror/lang-javascript": "^6.1.4",
- "@codemirror/lang-markdown": "^6.1.0",
- "@codemirror/language": "^6.6.0",
- "@codemirror/state": "^6.2.0",
- "@codemirror/view": "^6.9.2",
- "codemirror": "^6.0.1"
- }
-}
\ No newline at end of file
diff --git a/web/_vendor/minisearch/Makefile b/web/_vendor/minisearch/Makefile
deleted file mode 100644
index 94a96f1..0000000
--- a/web/_vendor/minisearch/Makefile
+++ /dev/null
@@ -1,4 +0,0 @@
-VERSION := 6.0.1
-
-download:
- curl -s https://cdn.jsdelivr.net/npm/minisearch@$(VERSION)/dist/umd/index.min.js | grep -v "//# sourceMappingURL=" > ../../static/vnd/minisearch-$(VERSION).min.js
\ No newline at end of file
diff --git a/web/_vendor/mithril/Makefile b/web/_vendor/mithril/Makefile
deleted file mode 100644
index 980b337..0000000
--- a/web/_vendor/mithril/Makefile
+++ /dev/null
@@ -1,4 +0,0 @@
-VERSION := 2.0.3
-
-download:
- curl -s https://cdnjs.cloudflare.com/ajax/libs/mithril/$(VERSION)/mithril.min.js > ../../static/vnd/mithril-$(VERSION).min.js
\ No newline at end of file
diff --git a/web/_vendor/octokit/Makefile b/web/_vendor/octokit/Makefile
deleted file mode 100644
index 8637a46..0000000
--- a/web/_vendor/octokit/Makefile
+++ /dev/null
@@ -1,4 +0,0 @@
-VERSION := 18.12.0
-
-bundle:
- npm install @octokit/rest@$(VERSION) && esbuild octokit.js --bundle --outfile=../../static/vnd/octokit-$(VERSION).min.js --format=esm --minify
\ No newline at end of file
diff --git a/web/_vendor/octokit/octokit.js b/web/_vendor/octokit/octokit.js
deleted file mode 100644
index d3c0e81..0000000
--- a/web/_vendor/octokit/octokit.js
+++ /dev/null
@@ -1 +0,0 @@
-export { Octokit } from "@octokit/rest";
\ No newline at end of file
diff --git a/web/blog/index.tsx b/web/blog/index.tsx
deleted file mode 100644
index 7465d0b..0000000
--- a/web/blog/index.tsx
+++ /dev/null
@@ -1,10 +0,0 @@
-export const title = "Treehouse";
-export default (data) => (
-
-
-
-
-
-
-
-)
diff --git a/web/blog/influences.md b/web/blog/influences.md
deleted file mode 100644
index d8ff711..0000000
--- a/web/blog/influences.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Treehouse Influences"
-author: "Jeff Lindsay"
-date: "2023-04-20"
----
-
-Over the past few months, we've built a frontend framework for an elegant, quality outliner that's open source, extensible, and gives you control of your data. I’d like to share some of the design influences for the Treehouse frontend, which should give a sense of the unique direction Treehouse is going from here.
-
-The biggest influences for Treehouse are Tana, Notion, and Obsidian. These three represent the state of the art of personal and collaborative information management, sometimes simplified as note-taking tools. However, "note-taking tools" sells them short as they go beyond note-taking and information management. For lack of a better descriptor, many consider them [tools for thought](https://www.forthought.tools/).
-
-## From Notes to Tools for Thought
-
-For most, note-taking brings to mind simple apps like Apple Notes and Google Keep, or even just a text file editor. These work well for people because they're already there and focus on quick and easy plain text capture. We could call this casual note-taking.
-
-Back in the 2000s, hosted and self-hosted wikis became popular for easy, collaborative web publishing and knowledge management. Like Wikipedia, they could be used to build out hyperlinked knowledge repositories. Many wiki-based tools focused on their use as personal notebooks, one of the most influential examples being [TiddlyWiki](https://tiddlywiki.com/). The simple versatility of the wiki laid the groundwork for what we call "tools for thought" today.
-
-
-
-When [Notion](https://www.notion.so/) appeared in the mid-2010s, it built on the idea of the wiki and introduced structured data management with flexible views that *effectively gave you integrated, customizable versions of other productivity tools*. Notion, Airtable, and others helped bring in the age of no-code and low-code tools, allowing knowledge workers and entrepreneurs to build their own "apps" or solutions to problems without traditionally building software. Notion brought it all together in a simple, user-friendly experience based around the core idea of wiki-like information management.
-
-
-
-Meanwhile, a separate paradigm of note-taking tools emerged, focusing on the nested, tree-like structure of the outline. Perhaps inspired by tools like [OmniOutliner](https://www.omnigroup.com/omnioutliner/) and [Org Mode](https://orgmode.org/) for Emacs of the 2000s, [Workflowy](https://workflowy.com/) appeared in 2010 as a no-frills web-based outliner.
-
-
-
-[Obsidian](https://obsidian.md/) arrived in 2020 and is a local app focusing on Markdown files stored on your filesystem. Obsidian has a large plugin ecosystem giving it a wide breadth of features, but it’s especially appealing to those that want to own their data. If you strip away the plugins, Obsidian is a pretty simple hyperlinked Markdown editor.
-
-
-
-Most recently, a tool in early access called [Tana](https://tana.inc/) caught my attention. Their key innovation is taking the linked outline model of Workflowy and introducing schemas for nodes, making them into structured data. This gives Tana the embedded database functionality of Notion and Airtable, a step towards bringing the two paradigms of note-taking software together towards powerful, malleable tools for thought.
-
-
-
-## How Treehouse Fits In
-
-By now there's no shortage of options in this space, both as SaaS and open source. Take a look at this growing [encyclopedia of note-taking tools](https://noteapps.info/). Like Notion and Tana, many of the apps listed are much more than note-taking tools. Some lean into the framing of "collaborative documents", and some are just categorized more generally as "productivity tools". Tana goes so far as to say "the everything OS".
-
-Note-taking is just the beginning. It's a tangible gateway for something more powerful inherent to computing. Ever since Engelbart's [mother of all demos](https://en.wikipedia.org/wiki/The_Mother_of_All_Demos), the computing revolution seems to start with powerful tools for thought, which are, at minimum, good note-taking tools.
-
-
-
-Treehouse is a frontend and starter kit for anybody else that wants to explore this space with us. We will release a standalone product based on it soon, but most of the user-facing development will be done in the open source Treehouse project.
-
-
-
-Today with Treehouse you can build your own Workflowy equivalent, but soon it will become more comparable to Tana and Notion with the open extensibility of Obsidian. That alone is pretty exciting to have in a minimal open source project, but I can't wait to show you what will come next.
-
-## Coming Soon
-
-In the next post, I'll start getting technical and share details on the Treehouse project stack and architecture. If you can't wait, we do have [documentation](https://treehouse.sh/docs/dev/) for you to check out.
-
-Thanks for reading, and a big thanks to my [sponsors](https://github.com/sponsors/progrium) for supporting this kind of open source work. Share your thoughts and favorite note-taking tools in the [discussion thread](https://github.com/treehousedev/treehouse/discussions/95) for this post.
\ No newline at end of file
diff --git a/web/blog/v0-1-0.md b/web/blog/v0-1-0.md
deleted file mode 100644
index dd433b3..0000000
--- a/web/blog/v0-1-0.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Release 0.1.0"
-author: "Jeff Lindsay"
-date: "2023-03-03"
----
-## It begins...
-
-This first [development release](https://github.com/treehousedev/treehouse/releases/tag/0.1.0) captures core functionality of the frontend to the point of being internally usable in the demo deployment. For developers, the project source layout, architecture, and backend API is defined in broad strokes in the right direction but is by no means stable.
-
-[](https://www.youtube.com/watch?v=wtJCYlR2_ys)
-[Demo video](https://www.youtube.com/watch?v=wtJCYlR2_ys)
-
-## Initial Functionality
-* Basic outliner
-* Commands, menus, keybindings
-* Workspace model
-* Navigation tree
-* Command palette
-* Multi-view panels
-* Calendar/today notes
-* Quick add notes
-* Full-text search using [Minisearch](https://github.com/lucaong/minisearch)
-* Localstorage backend
-* GitHub backend
-
-## Enhancements
-* Implemented OS detection for registering different keybindings [#1](https://github.com/treehousedev/treehouse/issues/1)
-* Don't collapse new nested node [#3](https://github.com/treehousedev/treehouse/issues/3)
-* Hitting tab on plus sign should create an indented node [#4](https://github.com/treehousedev/treehouse/issues/4)
-* Improve cursor location when manually deleting a node [#5](https://github.com/treehousedev/treehouse/issues/5)
-* Improve backspace behavior when cursor is at the beginning of a node [#6](https://github.com/treehousedev/treehouse/issues/6)
-* Add keyboard shortcut to zoom [#8](https://github.com/treehousedev/treehouse/issues/8)
-* Allow editing title node [#9](https://github.com/treehousedev/treehouse/issues/9)
-* Hide root node [#10](https://github.com/treehousedev/treehouse/issues/10)
-* Clean up sidebar text [#11](https://github.com/treehousedev/treehouse/issues/11)
-* Remember node expansion state [#19](https://github.com/treehousedev/treehouse/issues/19)
-* Typography updates [#21](https://github.com/treehousedev/treehouse/issues/21)
-
-## Bugfixes
-* Enable text wrapping for nodes [#2](https://github.com/treehousedev/treehouse/issues/2)
-* Highlight to delete for nested node gives a TypeError [#12](https://github.com/treehousedev/treehouse/issues/12)
-* Hitting return mid-node copies contents instead of moving [#17](https://github.com/treehousedev/treehouse/issues/17)
-* Quick Add formatting issue [#18](https://github.com/treehousedev/treehouse/issues/18)
-* Error logging in with GitHub [#22](https://github.com/treehousedev/treehouse/issues/22)
-* Node content disappears when it loses focus [#24](https://github.com/treehousedev/treehouse/issues/24)
-* Display issue w/ icons overlapping search bar [#26](https://github.com/treehousedev/treehouse/issues/26)
\ No newline at end of file
diff --git a/web/blog/v0-2-0.md b/web/blog/v0-2-0.md
deleted file mode 100644
index df4ea91..0000000
--- a/web/blog/v0-2-0.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Release 0.2.0"
-author: "Jeff Lindsay"
-date: "2023-03-27"
----
-## New design system, GitHub session locking, and documentation
-
-[This release](https://github.com/treehousedev/treehouse/releases/tag/0.2.0) is a refinement of our initial release, fixing a number of bugs and adding interaction improvements. The look and feel of the UI was also updated with the start of a new CSS design system based on custom properties. Session locking was added for the live demo and GitHub backend so multiple devices/browsers/tabs don't clobber changes of each other. Documentation also got an upgrade with the start of a [full guide](https://treehouse.sh/docs/quickstart/) on the website.
-
-[](https://www.youtube.com/watch?v=wj4uai9yUJ0)
-[Demo video](https://www.youtube.com/watch?v=wj4uai9yUJ0)
-
-## Bugfixes
-* Autosave error when switching between devices [#32](https://github.com/treehousedev/treehouse/issues/32)
-* Deleting a node doesn't delete child nodes [#25](https://github.com/treehousedev/treehouse/issues/25)
-* Hitting return should produce a new node directly below the above node [#29](https://github.com/treehousedev/treehouse/issues/29)
-* TypeError exception when switching back from new panel [#65](https://github.com/treehousedev/treehouse/issues/65)
-* Support emojis [#52](https://github.com/treehousedev/treehouse/issues/52)
-
-## Enhancements and Chores
-* Typography and layout improvements to application [#37](https://github.com/treehousedev/treehouse/issues/37)
-* Add keyboard shortcut to move nodes up or down [#28](https://github.com/treehousedev/treehouse/issues/28)
-* Prevent backspace to delete if there are child nodes [#15](https://github.com/treehousedev/treehouse/issues/15)
-* Allow renaming the workspace [#23](https://github.com/treehousedev/treehouse/issues/23)
-* Clicking outside of the search bar/command palette should close it [#48](https://github.com/treehousedev/treehouse/issues/48)
-* Workspace/workbench separation [#39](https://github.com/treehousedev/treehouse/issues/39)
-* Add API docs [#34](https://github.com/treehousedev/treehouse/issues/34)
-* Set up versioned library bundle [#41](https://github.com/treehousedev/treehouse/issues/41)
-* Allow backspace to delete an empty child node [#53](https://github.com/treehousedev/treehouse/issues/53)
-* Save last location on reloads [#54](https://github.com/treehousedev/treehouse/issues/54)
-* Hide buttons to move a panel up/down [#49](https://github.com/treehousedev/treehouse/issues/49)
-
----
-[*Discuss on GitHub*](https://github.com/treehousedev/treehouse/discussions/82)
\ No newline at end of file
diff --git a/web/blog/v0-3-0.md b/web/blog/v0-3-0.md
deleted file mode 100644
index d169a58..0000000
--- a/web/blog/v0-3-0.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Release 0.3.0"
-author: "Jeff Lindsay"
-date: "2023-05-17"
----
-## New Node Types: Fields, Live Search, and References
-
-This release we added some exciting new features: Fields, Live Search, and References. These new node types represent our first step into becoming much more than a simple outliner. Quality of live improvements include making the node menu easier to click, initial work towards a mobile view, and improving interactivity of the command palette. We also cleaned up all our UI elements to match our design system, allowing for better custom CSS support.
-
-*Update 7/10/2023: Live Search is now called Smart Nodes*
-
-[](https://www.youtube.com/watch?v=PjWibMkKBOE)
-[Demo video](https://www.youtube.com/watch?v=PjWibMkKBOE)
-
-### New Feature: Fields
-
-A field is a node that can store a key-value pair. This introduces structured data to your nodes, letting you create nodes as data records. You can also search for nodes by field. This initial pass supports text values, but we'll soon provide more value types.
-
-To turn a node into a field:
-1. Indent underneath the node you want to contain the field, and type the field name
-2. Command/Control + K to open the command palette, and choose "Create Field"
-3. Add your field value in the value section
-
-### New Feature: Live Search
-
-Live Search allows you to create search nodes where the children are auto-updating search results. Simply type a keyword, or use the format "fieldname:value" to filter by fields. The Live Search nodes will update automatically as your workspace content changes. This is a powerful way to view your data in new configurations.
-
-To create a Live Search:
-1. Create a new node where you want your search node, and type your search value
-2. Command/Control + K to open the command palette, and choose "Create Search Node"
-
-Tips: Search terms are case-insensitive, and you can filter on multiple fields (uses AND, not OR) like so: "fieldname:value fieldname:value".
-
-### New Feature: References
-
-References are nodes that refer to another node and its children inline. They're sort of like symlinks on the filesystem. This lets you have a node exist in multiple places at once. References are differentiated from normal nodes with a dashed outline around their outline bullet. Deleting a reference node does not delete the node it points to. You may notice that Live Search results are reference nodes!
-
-To create a reference node:
-1. Select the node you want to make a reference to
-2. Command/Control + K to open the command palette, and choose "Create Reference"
-
-## Bugfixes
-* Command palette now uses normalized title [#117](https://github.com/treehousedev/treehouse/issues/117)
-* Command palette supports mouse interactivity [#102](https://github.com/treehousedev/treehouse/issues/102)
-* Components no longer fail with bundled library [#119](https://github.com/treehousedev/treehouse/issues/119)
-* Ensure Node IDs are unique [#104](https://github.com/treehousedev/treehouse/issues/104)
-* Reference sub-nodes now include fields [#121](https://github.com/treehousedev/treehouse/issues/121)
-* Search nodes no longer production workspace [#118](https://github.com/treehousedev/treehouse/issues/118)
-* Prevent indenting/outdenting a field node [#116](https://github.com/treehousedev/treehouse/issues/116)
-
-## Enhancements and Chores
-* New feature: Field nodes
-* New feature: Live Search nodes
-* New feature: Reference nodes
-* Clear out non-existent node keys in workspace document under expanded [#120](https://github.com/treehousedev/treehouse/issues/120)
-* Don't show bullet for empty nodes [#31](https://github.com/treehousedev/treehouse/issues/31)
-* Allow hovering over menu area to show menu [#76](https://github.com/treehousedev/treehouse/issues/76)
-* Clean up styles on search bar, palette, quick add, menu, buttons [#81](https://github.com/treehousedev/treehouse/issues/81), [#85](https://github.com/treehousedev/treehouse/issues/85), [#96](https://github.com/treehousedev/treehouse/issues/96), [#108](https://github.com/treehousedev/treehouse/issues/108), [#110](https://github.com/treehousedev/treehouse/issues/110)
-* Show placeholder text for empty field key/value inputs [#135](https://github.com/treehousedev/treehouse/issues/135)
-* Implement initial version of mobile web app [#103](https://github.com/treehousedev/treehouse/issues/103)
-
----
-[*Discuss on GitHub*](https://github.com/treehousedev/treehouse/discussions/156)
\ No newline at end of file
diff --git a/web/blog/v0-4-0.md b/web/blog/v0-4-0.md
deleted file mode 100644
index 543c058..0000000
--- a/web/blog/v0-4-0.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Release 0.4.0"
-author: "Jeff Lindsay"
-date: "2023-06-19"
----
-## Mobile support and CSS themes
-
-In this release we focused on making Treehouse more powerful and enjoyable to use from more places. Editing text on mobile is always a tricky prospect, but we've taken our first step to being mobile-friendly with customized navigation and easier touch targets.
-
-White background a bit too bright? We've added several built-in themes (including sepia and dark mode) *and* we've made it super easy to [create your own CSS themes](https://treehouse.sh/docs/user/#css-theming) using our component variables.
-
-Otherwise, lots of quality of life improvements as usual, especially for fields and Smart Nodes.
-
-[](https://www.youtube.com/watch?v=byZnYzzrP7E)
-[Demo video](https://www.youtube.com/watch?v=byZnYzzrP7E)
-
-## Enhancements and Chores
-* Support setting a theme in the UI, and custom CSS themes [#168](https://github.com/treehousedev/treehouse/issues/168), [#122](https://github.com/treehousedev/treehouse/issues/122)
-* Mobile improvements: new navigation and improved interactivity [#114](https://github.com/treehousedev/treehouse/issues/114), [#115](https://github.com/treehousedev/treehouse/issues/115)
-* Allow partial phrase match for command palette search [#148](https://github.com/treehousedev/treehouse/issues/148)
-* UX improvements for search nodes [#134](https://github.com/treehousedev/treehouse/issues/134)
-* Only show new-node plus sign if a node is expanded and has no children [#149](https://github.com/treehousedev/treehouse/issues/149)
-* Add keyboard shortcuts to command palette [#129](https://github.com/treehousedev/treehouse/issues/129)
-* Prevent turning nodes with children into search nodes [#161](https://github.com/treehousedev/treehouse/issues/161)
-* Support multiple workflows for creating fields [#152](https://github.com/treehousedev/treehouse/issues/152)
-* Show visual indicator when search node is collapsed [#150](https://github.com/treehousedev/treehouse/issues/150)
-* Consolidate search logic [#159](https://github.com/treehousedev/treehouse/issues/159)
-* Consolidate overlays with dialog element [#158](https://github.com/treehousedev/treehouse/issues/158)
-* Support multiple workflows for creating fields[#152](https://github.com/treehousedev/treehouse/issues/152)
-
-## Bugfixes
-* Backspace behavior on fields should be predictable [#130](https://github.com/treehousedev/treehouse/issues/130)
-* Don't collapse above node when outdenting [#131](https://github.com/treehousedev/treehouse/issues/131)
-* Backspacing from beginning of node deletes children [#151](https://github.com/treehousedev/treehouse/issues/151)
-* Prevent edit interactions on search node [#105](https://github.com/treehousedev/treehouse/issues/105)
-
----
-[*Discuss on GitHub*](https://github.com/treehousedev/treehouse/discussions/215)
\ No newline at end of file
diff --git a/web/blog/v0-5-0.md b/web/blog/v0-5-0.md
deleted file mode 100644
index 109b0ad..0000000
--- a/web/blog/v0-5-0.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Release 0.5.0"
-author: "Jeff Lindsay"
-date: "2023-07-06"
----
-## Tags, templates, and table view
-
-Treehouse now supports tags and templates! For example, you can now create a template node with children and fields, name it "book", then any node tagged with #book will automatically get those fields and children. To turn a node into a template, select "Make Template" from the Command Palette. You can also tag nodes without an equivalent template. Tagging is done by simply adding hashtags to a node's text.
-
-You can search for tagged nodes in the search bar using the hashtag notation (#book), however there is a known issue preventing you from searching for nodes by tag in Smart Nodes. This will be resolved in the next release, and in `main` much sooner.
-
-You can now take a list of nodes with fields and turn them into an easy-to-scan table. Simply go to the parent node of the rows, open the Command Palette with Command+K, and choose "View as Table". We'll be adding more features to the table view in coming releases.
-
-Double-quoted search terms now allow spaces and search results are a little tighter now. Last but not least we've added cut, copy, and paste commands for nodes, making it easier to duplicate and move nodes around.
-
-[](https://www.youtube.com/watch?v=qzsGuO6sfC0)
-[Demo video](https://www.youtube.com/watch?v=qzsGuO6sfC0)
-
-## Enhancements and Chores
-* Tags and templates [#206](https://github.com/treehousedev/treehouse/issues/206)
-* Cut/copy/paste nodes [#194](https://github.com/treehousedev/treehouse/issues/194)
-* Table view for nodes [#106](https://github.com/treehousedev/treehouse/issues/106), [#120](https://github.com/treehousedev/treehouse/issues/210)
-* Support field search terms containing spaces [#153](https://github.com/treehousedev/treehouse/issues/153)
-* Link to documentation from within Treehouse [#175](https://github.com/treehousedev/treehouse/issues/175)
-
-## Bugfixes
-* Search bug when capitalizing search term [#217](https://github.com/treehousedev/treehouse/issues/217)
-* Search is behaving too broadly when matching [#197](https://github.com/treehousedev/treehouse/issues/197)
-* Support multiple concurrent dialogs [#203](https://github.com/treehousedev/treehouse/issues/203)
-* Support editing "Calendar" node without Today making a new one [#232](https://github.com/treehousedev/treehouse/issues/232)
-
-
----
-[*Discuss on GitHub*](https://github.com/treehousedev/treehouse/discussions/244)
\ No newline at end of file
diff --git a/web/blog/v0-6-0.md b/web/blog/v0-6-0.md
deleted file mode 100644
index f60fec3..0000000
--- a/web/blog/v0-6-0.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Release 0.6.0"
-author: "Jeff Lindsay"
-date: "2023-07-20"
----
-## New Document and Tab Views
-In this release we're introducing two new views: Document view, and Tab view. Views are a powerful idea in Treehouse that can either be used to create embedded mini-apps or act as building blocks for you to make your own. These new views are an example of each.
-
-Document view gives you a more conventional note-taking experience. In Document view each child node is rendered as a paragraph in the center of the panel. Documents support simple Markdown formatting like bold, italic, strikethrough, and ordered and unordered lists. Turn a node into a document by choosing "Make Document" from the Command Palette. Unlike other views, changing to Document view is a one-way action and nodes can't be converted back to other views.
-
-Tab view renders each child node as a tab. Their children (grandchild nodes) are shown beneath when the tab is selected. These nodes will retain their view, so you can combine Tab view with others to create a more complex larger view of your data. In general, Tab view is useful for saving vertical space across several categories. Turn nodes into tabs by selecting the parent node and choose "View as Tabs" from the Command Palette. Since Tab view is read-only, you can modify tabs by switching back to List view.
-
-We've also renamed Live Search Nodes to Smart Nodes, which can now be named separate from their query. This also resolves an issue where previously you couldn't use them for tag searches.
-
-[](https://www.youtube.com/watch?v=-CsRlyJx2cU)
-[Demo video](https://www.youtube.com/watch?v=-CsRlyJx2cU)
-
-## Enhancements and Chores
-* Tabs view [#126](https://github.com/treehousedev/treehouse/issues/126)
-* Document view [#246](https://github.com/treehousedev/treehouse/issues/246)
-* Support setting a name for a Smart Node [#235](https://github.com/treehousedev/treehouse/issues/235)
-* Clean up command palette commands [#242](https://github.com/treehousedev/treehouse/issues/242)
-* Rename live search/search node to Smart Node [#248](https://github.com/treehousedev/treehouse/issues/248)
-
-## Bugfixes
-* Range error when turning a tag into a search node [#236](https://github.com/treehousedev/treehouse/issues/236)
-* Don't allow outdenting a top-level node [#234](https://github.com/treehousedev/treehouse/issues/234)
-* Can't interact with an empty node in Quick Add (mobile) [#204](https://github.com/treehousedev/treehouse/issues/204)
-* Capital letters in GitHub username prevent login [#245](https://github.com/treehousedev/treehouse/issues/245)
-* Can't select a theme in Chrome [#266](https://github.com/treehousedev/treehouse/issues/266)
-
----
-[*Discuss on GitHub*](https://github.com/treehousedev/treehouse/discussions/273)
\ No newline at end of file
diff --git a/web/blog/v0-7-0.md b/web/blog/v0-7-0.md
deleted file mode 100644
index 82e81e4..0000000
--- a/web/blog/v0-7-0.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Release 0.7.0"
-author: "Jeff Lindsay"
-date: "2023-08-18"
----
-## Descriptions, better paste, shortcut drawer
-
-We're excited to be adding a handful of minor enhancements in this release. The first is node descriptions, which allow you to add small text below your node content, as part of the same node. Use it to add context or any kind of secondary information. To use, select your node, open the Command Palette with Command/Control + K, and select "Add Description".
-
-We've made several improvements related to cut/copy/pasting text. Now if you paste text containing new lines, we'll convert each newline to a separate node. We've also fixed some bugs and UX flows.
-
-Lastly, check out the keyboard shortcut drawer! We want it to be super easy to learn and use keyboard shortcuts and hope this helps.
-
-
-## Enhancements and Chores
-* Node descriptions [#295](https://github.com/treehousedev/treehouse/issues/295)
-* Support searching for field keys containing spaces [#277](https://github.com/treehousedev/treehouse/issues/277)
-* Newlines should be translated as new nodes when pasting from outside sources [#250](https://github.com/treehousedev/treehouse/issues/250)
-* When multiple panels, all panels should be equal width [#259](https://github.com/treehousedev/treehouse/issues/259)
-* Keyboard shortcut reference drawer [#264](https://github.com/treehousedev/treehouse/issues/264)
-* Sublime theme - adjust pink to improve contrast [#284](https://github.com/treehousedev/treehouse/issues/284)
-* Use real italics/bold font variant for Codemirror (treehouse) [#272](https://github.com/treehousedev/treehouse/issues/272)
-
-## Bugs
-* Can't paste into (+) node [#275](https://github.com/treehousedev/treehouse/issues/275)
-* Prevent multiple checkboxes [#299](https://github.com/treehousedev/treehouse/issues/299)
-* Cut node pastes when you select cut, not paste [#293](https://github.com/treehousedev/treehouse/issues/293)
-* "Back" link should not require two clicks [#257](https://github.com/treehousedev/treehouse/issues/257)
-* Cutting the node should remove it from view [#274](https://github.com/treehousedev/treehouse/issues/274)
-* TypeError when smart node returns results [#269](https://github.com/treehousedev/treehouse/issues/269)
-* TypeError related to command palette + tags [#258](https://github.com/treehousedev/treehouse/issues/258)
-
----
-[*Discuss on GitHub*](https://github.com/treehousedev/treehouse/discussions/302)
\ No newline at end of file
diff --git a/web/blog/welcome.md b/web/blog/welcome.md
deleted file mode 100644
index 8dce442..0000000
--- a/web/blog/welcome.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-layout: layouts/blog.tsx
-title: "Welcome to Treehouse"
-author: "Jeff Lindsay"
-date: "2023-02-23"
----
-I'm excited to announce the start of a new major project that I'll be sharing the journey of on this fancy new blog. The project is called [Treehouse](https://treehouse.sh/), which is starting as an open source note-taking frontend and will evolve into something much more.
-
-
-
-We're creating a simple, hackable kernel of a note-taking tool as a web frontend that can be extended and customized by developers. Then we'll use that frontend to build a new kind of note-taking product. Today we have an early preview of our first minimum viable prototype of the frontend, and we'll be finishing up this release in the open on GitHub.
-
-The [open source project](https://github.com/treehousedev/treehouse) is a functional app frontend that you can deploy and back in various ways. For developers, this "bring your own backend" approach makes Treehouse a great starting point to build your own note-taking tool, just as we intend to do. We also have pre-made backends for those who want to use it with little-to-no programming. Either way, you'll always own your data, and now the system presenting it to you as well.
-
-In this post, I'm going to talk about our minimum viable prototype and the approach we're taking with Treehouse as an open source project.
-
-## Out of the Box
-
-While inspired by powerful tools like [Notion](https://www.notion.so/), [Tana](https://tana.inc/), and [Obsidian](https://obsidian.md/), we wanted to boil our initial goal down to the essentials while still being usable enough to use ourselves. As we continue to plan our prototype release milestone, we'd love to hear what you think is essential for you to have in a tool and platform like this, but here is what to expect as a baseline.
-
-### Outliner with Markdown Pages
-
-At the heart of Treehouse is a graph-like system I've been developing called Manifold. This will play a big part in the long-term extensibility of Treehouse, which I'll talk more about in the future. For now, this maps very cleanly to the outliner model popularized by Workflowy, Tana, and others.
-
-However, I'm also a fan of Notion-style pages and Obsidian's commitment to working with plain Markdown files. The Manifold system allows us to make certain nodes into Markdown pages. This hybrid model gets us the best of both worlds with room for even more possibilities later on.
-
-### Quick Add and Daily Notes
-
-Being able to quickly get thoughts and information into the system has been a key aspect of every good note-taking system. This can be exposed a number of ways from browser extensions to desktop shortcuts, but what makes any "quick add" functionality quick is not having to think about where it will be organized.
-
-Luckily, "daily notes" has become such a common pattern that many recent tools have managed daily notes built-in. This typical gives you a "today" note that is automatically organized into a calendar-like structure. This conveniently becomes the perfect destination for "quick add" notes.
-
-### Full-text Search
-
-Whether you are an obsessive organizer or are too busy to take the time, solid full-text search is basically a necessity. It's how we quickly get to our data.
-
-Out of the box we have a full-text search that doesn't require a backend. However, our pluggable backend will allow you to power search in a number of ways, and also opens up the ability to search into external systems that are important to you.
-
-### Built-in Backends
-
-"Bring your own backend" is a critical part of the design of this project, but Treehouse also needs to be usable by people who prefer not to *build* their own backend. Our prototype release is planned to include a handful of built-in backends to get started with.
-
-Our preview demo is using a localStorage backend, which works for development and special use cases. Of course, we will have a simple local filesystem backend for desktop scenarios, similar to Obsidian.
-
-However, we're most excited for the GitHub backend. This functions similarly to the local filesystem backend, but it would be versioned in a central repository on your GitHub account and be accessible on any online platform.
-
-Backends will not only let you extend storage, search, and authentication, but other aspects in the future.
-
-## Project Overview
-
-The Treehouse codebase and open source project is as much the product as its features. The entire user and developer experience is being designed around simplicity and human ergonomics.
-
-The Treehouse frontend is built with web technologies intended for use across web, mobile, and desktop platforms. The project is written in TypeScript using [Deno](https://deno.land/) as its JavaScript toolchain.
-
-The JavaScript ecosystem is a mess, but Deno provides a forward-looking, self-contained toolchain that's easy to love. We actually have a zero Node.js policy and avoid NPM modules as much as possible.
-
-With minimal dependencies and an ongoing effort to keep the codebase small, it will always be easy to understand the entire Treehouse system. This will be further supported with a focus on documentation, both API docs and guides.
-
-We're using a permissive open source license, allowing you to use or change our code as you see fit. Contribution and participation is welcome, but so is simply consuming downstream.
-
-The project is actively being developed but we keep a [preview demo](https://treehouse.sh/demo/) running off the main branch that should always be in working order.
-
-## Coming Soon
-
-I'm excited to give you a deeper look at the project stack in a future post. For now, keep an eye out for the next post digging into the influences for Treehouse. We'll also try to answer "why another note-taking tool", and tease some long-term ideas for the future.
-
-Lastly, I want to mention the project is being developed in the open, not just with the code on GitHub, but most of my work is streamed and archived on [Twitch](https://www.twitch.tv/progrium). Feel free to come and co-work with me.
-
-Thanks for reading, and a big thanks to my [sponsors](https://github.com/sponsors/progrium/) for supporting this kind of open source work.
\ No newline at end of file
diff --git a/web/docs/dev/1-overview.md b/web/docs/dev/1-overview.md
deleted file mode 100644
index 044c642..0000000
--- a/web/docs/dev/1-overview.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Overview
----
-## Overview
-
-Treehouse is a frontend written in TypeScript made to be rendered in a browser or webview for building note-taking and information management tools. It is a "thick" frontend in that it holds most application state in-memory and executes user triggered commands to mutate that state. Persistence of that state, and a few other features, are expected to be provided by a "backend", which the frontend code interacts with via a backend adapter.
-Even without a backend adapter, the Treehouse frontend is still a fully functional application packaged as a JavaScript library that can be loaded onto any HTML page.
-
-### Architecture
-
-The library exposes a `setup()` function that:
-
-1. Takes a DOM document and backend adapter object
-1. Sets up a central controller for the UI called Workbench
-1. Loads a Workspace using the backend adapter
-1. Registers built-in commands and keybindings
-1. Uses [Mithril.js](https://mithril.js.org/) to mount a top level Mithril component to the document
-
-The UI is represented by a class called Workbench. This class orchestrates and provides most of the API for the rest of the system. The UI is broken down into Mithril components that implement the views for each part of the UI, pulling state from Workbench and connecting interactions to registered commands that represent all user actions. The Workbench and commands manipulate a Workspace, which represents the main data model for the system.
-
-### Stack
-
-To avoid the complexity and dependency hell, Treehouse avoids most common JavaScript tooling such as Node.js and NPM. Instead, Treehouse uses [Deno](https://deno.land/) as a toolchain and otherwise avoids dependencies as much as possible. The other main dependency we have is [Mithril.js](https://mithril.js.org/), which was chosen for its simplicity and lack of further dependencies.
-
-That said, there are other dependencies beyond this core stack which are chosen very deliberately. Out of the box search indexing depends on [MiniSearch](https://lucaong.github.io/minisearch/), and our most complex (but unavoidable) dependency is [CodeMirror](https://codemirror.net/). We're very conscious of project dependencies, including development and toolchain dependencies.
\ No newline at end of file
diff --git a/web/docs/dev/2-data-model.md b/web/docs/dev/2-data-model.md
deleted file mode 100644
index 200d715..0000000
--- a/web/docs/dev/2-data-model.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Data Model
----
-## Data Model
-
-The "document" for Treehouse is the Workspace, which is mostly a container for nodes. These nodes are based on a versatile and extensible API and data model called Manifold. In short, nodes:
-
-* have a unique ID
-* have a text name
-* can be children to other nodes
-* can have key-value attributes
-* can have components
-
-Most importantly, nodes build a tree-like structure where each node can be extended with components. Components extend the state and functionality of a node. For example, a checkbox component can be added to a node. This gives it a state (checked or not) and allows the UI to render it differently (add a checkbox).
\ No newline at end of file
diff --git a/web/docs/dev/3-user-actions.md b/web/docs/dev/3-user-actions.md
deleted file mode 100644
index fae3a59..0000000
--- a/web/docs/dev/3-user-actions.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-layout: layouts/docs.tsx
-title: User Actions
----
-## User Actions
-
-All user performable actions are modeled as commands and registered with a command system. Commands are functions with some extra metadata, like a user displayable name and system identifier. They can be called throughout the system by their system identifier, such as when a user clicks a something.
-
-Menus are often defined upfront, usually by commands. Commands can have keybindings registered for them for keyboard shortcuts. These systems work together. For example, a menu item for a command will show the keybinding for it.
-
-Commands can take arguments and usually take at least a single argument called a context. This is a way to represent state of the user’s current context, such as the currently selected node.
-
-In addition to menus, keyboard shortcuts, and UI event handlers, there is a command palette the user can trigger to show all commands that can be run in the current context.
\ No newline at end of file
diff --git a/web/docs/dev/4-workbench-ui.md b/web/docs/dev/4-workbench-ui.md
deleted file mode 100644
index 90418b0..0000000
--- a/web/docs/dev/4-workbench-ui.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Workbench UI
----
-## Workbench UI
-
-### Components
-
-The workbench UI is made up of Mithril components, which are similar to React components. They take parameters, can have state, and specify a view using JSX. Instead of many atomic components like buttons and labels, Treehouse focuses on larger functional components that map to areas of the UI. Reusable visual elements are represented by CSS classes. Only if a reusable atomic visual element becomes so re-used and is too complex to re-implement is it made into a Mithril component.
-
-All the Mithril components can be found under `lib/ui`. We use Typescript to make sure their parameters are typed so they're picked up by API documentation; no need for custom documentation for view components. Mithril components are just plain old JavaScript objects with a `view` method.
-
-### User Context
-
-Most components are explicitly passed a reference to the Workbench, which they can use to execute commands or pull data in the current Workspace or Context. The Workbench provides a top level context that has the current selected node or nodes, the current panel, etc. However, when passing a Context around it can be given overrides. For example, you may be currently editing a particular node, but you use the mouse to perform a command on another node. The menu ensures the command will receive a Context with that node being acted on.
-
-### Design System
-
-Our design system is inspired by projects like [Pollen](https://www.pollen.style/), where instead of generating CSS classes from JavaScript like Tailwind (which requires a compile step and Node.js based tooling), we simply use and override CSS custom properties. This means they can be used in inline styles as well. We also have a subset of common Tailwind utility classes defined, though using the custom properties.
\ No newline at end of file
diff --git a/web/docs/dev/5-backend-adapters.md b/web/docs/dev/5-backend-adapters.md
deleted file mode 100644
index 75b3edb..0000000
--- a/web/docs/dev/5-backend-adapters.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Backend Adapters
----
-## Backend Adapters
-
-Backend adapters are classes that implement the backend API for a given backend. If you wanted to make your own custom backend, you would implement your own backend adapter
-implementing the APIs you wish to hook into and pass that into the `setup` function when initializing Treehouse. We also have a handful of built-in adapters for public or
-well-known backend interfaces:
-
-### lib/backend/browser.ts
-
-This backend implements the FileStorage API using localStorage. This means data will be stored in the browser for a particular device. It also implements search indexing
-using MiniSearch. It does not implement the Authenticator API.
-
-### lib/backend/github.ts
-
-This backend implements the FileStorage API using the GitHub API to store data in a GitHub hosted Git repository. It also implements the Authenticator API against a
-script that can be hosted on CloudFlare Workers that implements an OAuth client for the GitHub API. This backend adapter does not implement a search index, it simply
-uses the browser implementation (MiniSearch).
-
-### lib/backend/filesystem.ts (coming soon)
-
-This backend implements the FileStorage API using a local filesystem. Since there isn't a good standard filesystem API in browsers, this implementation operates against
-a simple REST API that can be implemented by a backend host process, such as Electron, Apptron, or something custom.
-
-### Writing an Adapter
-
-An adapter is just an object that implements this API:
-
-```js
-interface Backend {
- auth: Authenticator|null;
- index: SearchIndex;
- files: FileStore;
-}
-
-interface Authenticator {
- login();
- logout();
- currentUser(): User|null;
-}
-
-interface User {
- userID(): string;
- displayName(): string;
- avatarURL(): string;
-}
-
-interface SearchIndex {
- index(node: RawNode);
- remove(id: string);
- search(query: string): string[];
-}
-
-interface FileStore {
- async readFile(path: string): string|null;
- async writeFile(path: string, contents: string);
-}
-```
-
-The Authenticator API is optional (and soon so might the SearchIndex API, always defaulting to MiniSearch). Typically a backend adapter will
-set `auth`, `index`, and `files` to `this` and implement each of those interfaces on that same object.
\ No newline at end of file
diff --git a/web/docs/dev/6-api-reference.md b/web/docs/dev/6-api-reference.md
deleted file mode 100644
index 34989d7..0000000
--- a/web/docs/dev/6-api-reference.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: layouts/docs.tsx
-title: API Reference
----
-## API Reference
-
-TypeScript documentation for Treehouse is available via [Deno Land](https://deno.land/x/treehouse@0.1.0).
\ No newline at end of file
diff --git a/web/docs/dev/index.tsx b/web/docs/dev/index.tsx
deleted file mode 100644
index 0c9e63c..0000000
--- a/web/docs/dev/index.tsx
+++ /dev/null
@@ -1,11 +0,0 @@
-export const title = "Docs";
-export const active = "docs";
-export const heading = "Documentation";
-export const layout = "layouts/docs.tsx";
-export default (data, filters) => {
- const url = data.url;
- const nav = data.nav;
- const menu = nav.menu(url);
- const children = menu.children || [];
- return children.map(child => );
-}
\ No newline at end of file
diff --git a/web/docs/index.tsx b/web/docs/index.tsx
deleted file mode 100644
index c14478d..0000000
--- a/web/docs/index.tsx
+++ /dev/null
@@ -1,10 +0,0 @@
-export const title = "Treehouse";
-export default (data) => (
-
-
-
-
-
-
-
-)
diff --git a/web/docs/project/1-contributing.md b/web/docs/project/1-contributing.md
deleted file mode 100644
index bdaa6f0..0000000
--- a/web/docs/project/1-contributing.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Contributing
----
-## Contributing
-
-We'd love your contributions to the project, especially fixes to long-standing issues. If you'd like to work on something that necessitates discussion first, please create an issue so we can provide feedback and avoid stepping on each other's toes.
-
-You can also contribute by:
-* submitting bugs as [issues](https://github.com/treehousedev/treehouse/issues)
-* sharing feedback on our [discussion forum](https://discord.gg/6Ae3VNqJbr)
-
-We welcome any kind of feedback about features you'd like, and we'd especially love to learn about your use case.
\ No newline at end of file
diff --git a/web/docs/project/2-roadmap.md b/web/docs/project/2-roadmap.md
deleted file mode 100644
index 1ba02f0..0000000
--- a/web/docs/project/2-roadmap.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Roadmap
----
-## Roadmap
-
-We're still formalizing our roadmap, how to organize it, share it, and collaborate with the community on it. For now, keep an eye on the [GitHub issues](https://github.com/treehousedev/treehouse/issues) and [discussions](https://discord.gg/6Ae3VNqJbr).
\ No newline at end of file
diff --git a/web/docs/project/index.tsx b/web/docs/project/index.tsx
deleted file mode 100644
index 0c9e63c..0000000
--- a/web/docs/project/index.tsx
+++ /dev/null
@@ -1,11 +0,0 @@
-export const title = "Docs";
-export const active = "docs";
-export const heading = "Documentation";
-export const layout = "layouts/docs.tsx";
-export default (data, filters) => {
- const url = data.url;
- const nav = data.nav;
- const menu = nav.menu(url);
- const children = menu.children || [];
- return children.map(child => );
-}
\ No newline at end of file
diff --git a/web/docs/quickstart/1-using.md b/web/docs/quickstart/1-using.md
deleted file mode 100644
index 97bbef5..0000000
--- a/web/docs/quickstart/1-using.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Using from CDN
----
-## Using from CDN
-
-First, you have to directly include Mithril and MiniSearch for now:
-
-```html
-
-
-```
-
-If you want to use our CSS, you'll also need to include the Google Font it uses:
-
-```html
-
-
-```
-
-Then you just need some JavaScript to import and call setup with a built-in or custom backend adapter:
-
-```html
-
-```
diff --git a/web/docs/quickstart/2-building.md b/web/docs/quickstart/2-building.md
deleted file mode 100644
index 99d1c45..0000000
--- a/web/docs/quickstart/2-building.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Building from Source
----
-## Building from Source
-
-You can build from source by cloning or forking the project and installing [Deno](https://deno.land/). Then you can run:
-
-`deno task bundle`
-
-This will produce a JS file you can use at `web/static/lib/treehouse.min.js`.
-
-For development or debugging, you can run:
-
-`deno task serve`
-
-This will build and serve this website locally, including the live demo site at `localhost:9000/demo`, which will use
-and watch for changes in the `lib` source.
\ No newline at end of file
diff --git a/web/docs/quickstart/3-customizing.md b/web/docs/quickstart/3-customizing.md
deleted file mode 100644
index 07ef80c..0000000
--- a/web/docs/quickstart/3-customizing.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Customizing the Frontend
----
-## Customizing the Frontend
-
-The easiest aspect to customize is the look and feel, which you can do with custom CSS. Our CSS design system is built with
-custom properties, so you can include your own CSS and just override them with basic CSS.
-
-Further customization might require you to fork and change the source. The source code is very straight forward, but learn
-more in the Developer Guide.
-
-Lastly, of course, you can implement a custom backend adapter. Although there are just a few things to change this way,
-more extension points will be exposed in the future so you won't have to change source. Let us know in the forum what kind
-of extension points you'd like!
\ No newline at end of file
diff --git a/web/docs/quickstart/index.tsx b/web/docs/quickstart/index.tsx
deleted file mode 100644
index 0c9e63c..0000000
--- a/web/docs/quickstart/index.tsx
+++ /dev/null
@@ -1,11 +0,0 @@
-export const title = "Docs";
-export const active = "docs";
-export const heading = "Documentation";
-export const layout = "layouts/docs.tsx";
-export default (data, filters) => {
- const url = data.url;
- const nav = data.nav;
- const menu = nav.menu(url);
- const children = menu.children || [];
- return children.map(child => );
-}
\ No newline at end of file
diff --git a/web/docs/user/01-what-is-treehouse.md b/web/docs/user/01-what-is-treehouse.md
deleted file mode 100644
index 8694cfe..0000000
--- a/web/docs/user/01-what-is-treehouse.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: layouts/docs.tsx
-title: What is Treehouse?
----
-## What is Treehouse?
-
-Treehouse is an outline editor, which you can think of as a nested bulleted list. Each bullet item is called a **node**. You can use the nodes to create nested layers of folders and notes.
\ No newline at end of file
diff --git a/web/docs/user/02-data-storage.md b/web/docs/user/02-data-storage.md
deleted file mode 100644
index 05bd522..0000000
--- a/web/docs/user/02-data-storage.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Data Storage
----
-## Data Storage
-
-### Localstorage
-
-By default, data is stored in your browser’s local storage. That means that the data is linked to your specific browser and device. If you clear your browser cache, the data will be wiped.
-
-### GitHub
-
-If you choose to log in with GitHub, we’ll create a repository and store your data there.
-
-To store your workspace, we will create a public repository called .treehouse.sh if it doesn’t already exist. If you want to make the repository private, you can do so in GitHub.
-
-To switch back to the local storage backend, log out from the Options menu.
-
-#### Multiple sessions
-
-If you log in to Treehouse from multiple devices, the most recent device will have edit and save access. Other sessions will be prompted to refresh the page; if/when you do so, that session becomes the new active session.
\ No newline at end of file
diff --git a/web/docs/user/03-nodes.md b/web/docs/user/03-nodes.md
deleted file mode 100644
index 25a364d..0000000
--- a/web/docs/user/03-nodes.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Nodes
----
-## Nodes
-
-Your **Workspace** is your top level node, which all other nodes are nested under.
-
-Learn how to manage and edit your nodes.
-
-### Add
-
-You can add a new node in a few ways.
-
-1. Hit ENTER on your keyboard and start typing.
-2. Click into the blank area next to the plus symbol and start typing.
-
-### Indent
-
-* Indent a node using TAB ↹
-* Outdent a node using SHIFT + TAB ⇧ ↹
-
-### Move
-
-* Move a node up with SHIFT + COMMAND + UP ARROW ⇧ **⌘ ↑**
-* Move a node down with SHIFT + COMMAND + DOWN ARROW ⇧ **⌘** ↓
-
-### Expand or collapse a node
-
-If a node bullet has an outline around it, that’s an indication that it has nested content that is currently hidden. Click the node to expand it.
-
-Click an expanded node once to collapse it.
-
-### Node menu
-
-When you hover over a node, you’ll see a menu to the left of the node bullet. Click it to access node options, such as indent/outdent, open in a panel, etc.
-
-### Node formatting
-
-Currently, all nodes are formatted as plain text. You can, however, add a checkbox to a node. With a node selected, open the command palette (⌘ K) and select "Add checkbox".
-
-### View
-
-Double click a node to zoom in.
-
-### Side-by-side (Panel) view
-
-To view two nodes side-by-side:
-
-Open the node you want to be in the righthand panel. From its menu, choose “Open in New Panel”.
-
-You can close or expand either panel to return to a single panel view.
\ No newline at end of file
diff --git a/web/docs/user/04-fields.md b/web/docs/user/04-fields.md
deleted file mode 100644
index 833c0b2..0000000
--- a/web/docs/user/04-fields.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Fields
----
-## Fields
-
-A **field** is a node that can store structured information. Fields provide your data with structure, and allow for special search syntax (see [Smart Nodes](#smart-nodes)).
-
-### Create a field
-
-To add a field to a node:
-1. Indent underneath the node you want to contain the field, and type the field name
-2. Use Command/Control + K to open the command palette, and choose "Create field"
-3. Add your field value in the value section
\ No newline at end of file
diff --git a/web/docs/user/05-smart-nodes.md b/web/docs/user/05-smart-nodes.md
deleted file mode 100644
index fc228d8..0000000
--- a/web/docs/user/05-smart-nodes.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Smart Nodes
----
-## Smart Nodes
-
-Smart Nodes allow you to create an auto-updating search of all the nodes in your workspace. Simply type your search term, or use the format "fieldname:valuename" to filter specifically by field values. The Smart Node will update automatically as your node content changes. This is a simple but super powerful way to view your data in new configurations.
-
-To create a Smart Node:
-1. Create a new node where you want your Smart Node, and type your search value
-2. Use Command/Control + K to open the command palette, and choose "Create Smart Node"
-
-### Tips for using Smart Nodes
-* You can filter on multiple fieldname values (using AND, not OR) like so: "fieldname:valuename fieldname:valuename" etc.
-* If your fieldname has spaces, put quotes around it (fieldname:"Value name")
-* Search terms are case-insensitive
\ No newline at end of file
diff --git a/web/docs/user/06-tags.md b/web/docs/user/06-tags.md
deleted file mode 100644
index d75052a..0000000
--- a/web/docs/user/06-tags.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Tags
----
-## Tags
-
-Tags are versatile metadata. Here are some of the ways you can use them:
-
-* Conduct a keyword search in the searchbar
-* Use in Smart Nodes to create custom views
-* Use to add a template to a node
-
-### Create a tag
-On any node, with your cursor at the end of the text, type "#" then the tag name to create a tag. Any tags you have already created will show up in an autocomplete list when you type "#".
-
-### Delete a tag
-Click on the tag and press Backspace on your keyboard to delete it.
\ No newline at end of file
diff --git a/web/docs/user/07-templates.md b/web/docs/user/07-templates.md
deleted file mode 100644
index 1b01046..0000000
--- a/web/docs/user/07-templates.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Templates
----
-## Templates
-
-Templates allow you to add a set of predefined fields and other child nodes to a node simply by adding a tag to that node.
-
-### Create and use a template
-
-In this example, we'll create a template called "book" with child fields Author and Release Date.
-
-1. Wherever you want to store your template, type "book" in the node.
-2. Add child fields Author and Release Date, and leave the value fields empty. (To turn a regular node into a Field: Command Palette > Create field)
-3. With your cursor in the parent "book" node, open the Command Palette (Command/Control+K) and choose Make Template.
-4. Create a list of books wherever you'd like, if you haven't already. With your cursor on one if the individual books, type "#book" and hit ENTER to create the tag.
-5. Check out one of your book nodes—it should have the child fields Author and Release Date that you set up in your template.
\ No newline at end of file
diff --git a/web/docs/user/07.1-views.md b/web/docs/user/07.1-views.md
deleted file mode 100644
index 0de4b49..0000000
--- a/web/docs/user/07.1-views.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Views
----
-## Views
-
-You can view your data in many different ways using commands in the Command Palette.
-
-### Document
-Converting your node(s) to document view centers them in the panel, styles the nodes like paragraphs, and supports basic Markdown formatting.
-
-*Note: document view is a one-way conversion. Document nodes can't be converted back to List (outline) view.*
-
-#### Create a Document
-With your cursor on the parent node of the node(s) you want to convert to a document, open the Command Palette and select **Make Document**.
-
-#### Markdown formatting
-
-##### Text styles
-```html
-*italic* or _italic_
-**bold**
-~~strikethrough~~
-```
-##### Lists
-```html
-- unordered lists
-* with any of
-+ these characters
-
-1. ordered
-2. lists
-```
-
-### Table
-Useful for a set of nodes with common fields. Node fields will become columns.
-
-#### Use Table View
-With your cursor on the parent node of the nodes you want to convert to a document, open the Command Palette and select **View As Table**.
-
-To revert back to List (outline) view, select the parent node and choose "View as List" from the Command Palette.
-
-### Tabs
-The tab view tidies up a common group of nodes, allowing you to view one tab at a time.
-
-#### Use Tabs View
-With your cursor on the parent node of the nodes you want to convert to a document, open the Command Palette and select **View As Tabs**.
\ No newline at end of file
diff --git a/web/docs/user/08-calendar.md b/web/docs/user/08-calendar.md
deleted file mode 100644
index 7a89cfa..0000000
--- a/web/docs/user/08-calendar.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Calendar
----
-## Calendar
-
-The Calendar is a default node that is automatically generated for every workspace. Nodes inside the calendar are grouped by date, week, then year.
-
-### Today
-
-The Today shortcut allows you to quickly view the node for Today in your Calendar.
\ No newline at end of file
diff --git a/web/docs/user/09-quick-add.md b/web/docs/user/09-quick-add.md
deleted file mode 100644
index c620094..0000000
--- a/web/docs/user/09-quick-add.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Quick Add
----
-## Quick Add
-
-Quick Add in the top navigation is a shortcut that opens a modal in which you can jot a quick note. It will be added to today’s date in your Calendar.
\ No newline at end of file
diff --git a/web/docs/user/10-command-palette.md b/web/docs/user/10-command-palette.md
deleted file mode 100644
index aef5b39..0000000
--- a/web/docs/user/10-command-palette.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Command Palette
----
-## Command Palette
-
-With a node selected, open the command palette (⌘ K) to view all the available actions for that node.
\ No newline at end of file
diff --git a/web/docs/user/11-keyboard-shortcuts.md b/web/docs/user/11-keyboard-shortcuts.md
deleted file mode 100644
index b0ef751..0000000
--- a/web/docs/user/11-keyboard-shortcuts.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Keyboard Shortcuts
----
-## Keyboard Shortcuts
-
-
-
-
indent
-
↹
-
-
-
outdent
-
⇧ ↹
-
-
-
move node up
-
⇧ ⌘ ↑
-
-
-
move node down
-
⇧ ⌘ ↓
-
-
-
delete node
-
⇧ ⌘ ⌫
-
-
-
add or remove checkbox
-
⌘ ↵
-
-
-
mark checkbox as done
-
⌘ ↵
-
-
-
open command palette
-
⌘ K
-
-
\ No newline at end of file
diff --git a/web/docs/user/12-css-theming.md b/web/docs/user/12-css-theming.md
deleted file mode 100644
index 495d9e2..0000000
--- a/web/docs/user/12-css-theming.md
+++ /dev/null
@@ -1,112 +0,0 @@
----
-layout: layouts/docs.tsx
-title: CSS Theming
----
-## CSS Theming
-
-You can create your own custom theme for Treehouse using our built-in variables a.k.a. custom properties.
-
-### Create a theme
-1. Add a top level folder called "ext" to your treehouse.sh repository
-2. Create a CSS file inside the ext folder
-3. Use the format below to populate the variables with hex code values. *Tip: Create color variables inside the root block to reuse color styles between custom properties.*
-
-```css
-:root {
- --font: 'Font name';
-
- --color-primary: #hex;
-
- --color-background: #hex;
- --color-background-sidebar: #hex;
-
- --color-icon: #hex;
- --color-icon-secondary: #hex;
-
- --color-nav-label: #hex;
-
- --color-text: #hex;
- --color-text-placeholder: #hex;
- --color-text-secondary: #hex;
-
- --color-highlight: #hex;
-
- --color-node-handle: #hex;
- --color-node-handle-secondary: #hex;
-
- --color-outline: #hex;
- --color-outline-secondary: #hex;
-}
-```
-
-### Managing multiple CSS files
-If you have multiple CSS files you want to swap between, append ".disabled" to the end of the unused CSS filename(s).
-
-### Variable Reference
-
-
Variable
Description
-
-
--font
-
Global font definition. Change the font itself but not sizes or styles with this.
-
-
-
--color-primary
-
Background color of primary button
-
-
-
--color-background
-
Background color of main panels, menus, and modals
-
-
-
--color-background-sidebar
-
Background color of sidebar navigation
-
-
-
--color-icon
-
High contrast color used for primary icons. For example: icons in the top navigation
-
-
-
--color-icon-secondary
-
Low-contrast color used for secondary icons
-
-
-
--color-nav-label
-
Used for top and sidebar navigation labels
-
-
-
--color-text
-
Default text color used for body text, navigation, and primary icons
-
-
-
--color-text-placeholder
-
Lower-contrast color used for placeholder text in inputs
-
-
-
--color-text-secondary
-
Lower-contrast color used for secondary text
-
-
-
--color-highlight
-
Lowest-contrast color to subtly highlight selected item in the menu, search, and command palette
-
-
-
--color-node-handle
-
Bullet color for nodes (a.k.a. the node handle)
-
-
-
--color-node-handle-secondary
-
Lower-contrast accent color on node handles. For instance, the outer filled circle on a node indicating collapsed children.
-
-
-
--color-outline
-
High contrast border color on pop-over containers like modals and menus.
-
-
-
--color-outline-secondary
-
Lower contrast border color where less extreme contrast is needed, such as the divider between panels and the navigation.
-
-
-
-### Fonts
-
-To use a non-system font, you may import a font into your CSS file using either the @import method or the @font-face method.
\ No newline at end of file
diff --git a/web/docs/user/13-backend-extensions.md b/web/docs/user/13-backend-extensions.md
deleted file mode 100644
index e1b8aa9..0000000
--- a/web/docs/user/13-backend-extensions.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: layouts/docs.tsx
-title: Backend Extensions
----
-## Backend Extensions
-
-Backends can change or extend how a Treehouse application behaves and are exposed to the frontend via adapters.
-
-### Workspace Storage
-
-The Treehouse frontend uses its backend adapter to store the state of your workspace into a JSON document. The backend can decide where and how that JSON document is stored. For example, the Browser backend adapter will store the JSON into localStorage.
-
-### User Authentication
-
-An optional capability of the frontend is to know whether a particular user is authenticated. You typically want user authentication for cloud or web-based deployments, but not necessarily for a local desktop app.
-
-### Search Indexing
-
-Out of the box, Treehouse will index your workspace for full-text search using [Minisearch](https://lucaong.github.io/minisearch/),
-which will be good enough for many cases. However, a backend adapter can choose to hook into the index and searching
-so that you could have a more powerful search index such as ElasticSearch.
\ No newline at end of file
diff --git a/web/docs/user/index.tsx b/web/docs/user/index.tsx
deleted file mode 100644
index 0c9e63c..0000000
--- a/web/docs/user/index.tsx
+++ /dev/null
@@ -1,11 +0,0 @@
-export const title = "Docs";
-export const active = "docs";
-export const heading = "Documentation";
-export const layout = "layouts/docs.tsx";
-export default (data, filters) => {
- const url = data.url;
- const nav = data.nav;
- const menu = nav.menu(url);
- const children = menu.children || [];
- return children.map(child => );
-}
\ No newline at end of file
diff --git a/web/index.tsx b/web/index.tsx
deleted file mode 100644
index 704e1e8..0000000
--- a/web/index.tsx
+++ /dev/null
@@ -1,236 +0,0 @@
-export const title = "Treehouse";
-export default (data) => (
-
-
-
-
-
-
-
-
-
-
-
-
- Treehouse: Note-taking Frontend
-
-
-
-
-
-
-
-
-
-
-
- A lightweight note-taking tool to make your own
-
-
- An open source note-taking frontend to extend and customize. Bring your own backend or configure a built-in backend to get started.
-
![\"Watch](\"http://i3.ytimg.com/vi/-CsRlyJx2cU/hqdefault.jpg\")
![\"Watch](\"http://i3.ytimg.com/vi/qzsGuO6sfC0/hqdefault.jpg\")
![\"Watch](\"http://i3.ytimg.com/vi/byZnYzzrP7E/hqdefault.jpg\")
![\"Watch](\"http://i3.ytimg.com/vi/PjWibMkKBOE/hqdefault.jpg\")
![\"TiddlyWiki](\"https://treehouse.sh/photos/blog/tiddlywiki.png\")
![\"Notion](\"https://treehouse.sh/photos/blog/notion.jpeg\")
![\"Workflowy](\"https://treehouse.sh/photos/blog/workflowy.png\")
![\"Obsidian](\"https://treehouse.sh/photos/blog/obsidian.png\")
![\"Tana](\"https://treehouse.sh/photos/blog/tana.webp\")
![\"Engelbart](\"https://treehouse.sh/photos/blog/nls.jpeg\")
![\"Treehouse](\"https://treehouse.sh/photos/hero-image.png\")
![\"Watch](\"http://i3.ytimg.com/vi/wj4uai9yUJ0/hqdefault.jpg\")
![\"Watch](\"http://i3.ytimg.com/vi/wtJCYlR2_ys/hqdefault.jpg\")
