Get AI summaries of any video or article — Sign up free
NEW! Tana Publish: Page thumbnail

NEW! Tana Publish: Page

CortexFutura Tools·
5 min read

Based on CortexFutura Tools's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Publish Page turns structured Tana workspace content into polished, shareable web links without copy-paste workflows.

Briefing

Tana has launched a “Publish Page” feature that turns structured workspace content into polished, shareable web documents—complete with formatting controls, live collections, and optional per-item pages. The practical payoff is simple: instead of copying and pasting notes, highlights, or research summaries into email or docs, users can right-click a structured block (or publish a whole page) and generate a clean link others can read immediately.

The walkthrough starts with meeting notes built from Tana “super tags.” A meeting node includes fields like meeting date, attendees, agenda, and a written summary plus decisions. Publishing is triggered from within the workspace—right-clicking a bullet and selecting publish preview—then producing a visually laid-out document on the web. Formatting isn’t one-size-fits-all: each field can be rendered as a label/value pair, a heading with paragraph text, a list, a quote, or a paragraph-only display. Indentation in the source structure maps to hierarchy on the published page, so nested sections become headings and list items automatically.

Access and lifecycle are also straightforward. Published pages use a shareable URL containing a random string, functioning like “anyone with the link can view,” with no authentication or invite-by-email controls yet. Unpublishing removes the page from public access; attempting to open the old link results in an error.

A second example shows how Publish Page supports “book reviews” using a live search and a card-style overview. A page titled “my book reviews” includes a live query that pulls in all items tagged as book review. When published, the overview can display ratings and review text in a cards view. If content changes after publication, updates require an explicit “publish changes” action rather than auto-updating.

The feature also supports drill-down publishing. Individual book review items can be published as their own pages. Once those exist, the overview cards can switch from showing full text to linking out to each item’s dedicated published page—creating an interconnected reading experience where a short summary lives on the collection page, while the full review sits behind a click.

The third example targets longer research workflows. A “question” super tag gathers synthesis material plus related claims and thoughts into a tabbed published layout. Referenced nodes’ fields and content can appear in the published output, including nested information from linked super-tagged items. There’s limited control over what’s shown: hiding fields is done via a “hide field condition” set to always, rather than context-specific hiding. For longer documents, users can instead publish only a specific section (like synthesis text) as a standalone page, with formatting options such as rendering the date as a quote.

Publish Page also handles rich media. Videos can be embedded by pasting a video into Tana, and images can be added both as inline content and as a draggable header image that becomes the page’s top banner and also appears in card previews. Overall, the launch positions Tana as a system for turning structured knowledge work—notes, reviews, and research—into readable, attractive web pages with minimal friction and clear sharing controls.

Cornell Notes

Tana’s new Publish Page feature converts structured workspace content into clean, shareable web documents. Users can publish meeting notes, book-review collections, and research syntheses directly from Tana super tags, with per-field display options like label/value, headings, lists, quotes, or paragraph-only formats. Published pages are link-based (“anyone with the link can view”) and can be removed by unpublishing, which makes old links stop working. Live queries can build an overview page that pulls in all items matching a tag, while individual items can also be published as separate pages for deeper reading. The system supports embedded videos and images, including draggable header images that appear in both page headers and card previews.

How does Publish Page turn structured Tana content into a readable document?

Publish Page takes content organized in Tana super tags and renders it into a web layout. In the meeting-notes example, fields like meeting date, attendees, agenda, and a written summary become visible sections on the published page. Each field can be displayed in multiple formats—label/value, heading with paragraph, heading with list, quote, or paragraph-only. Indentation in the source structure maps to hierarchy on the published page, so nested items become headings and list bullets automatically.

What controls exist for formatting fields on a published page?

For each field, the published output can switch between several presentation styles. The meeting-date field can show label plus value, appear as a heading with paragraph text, render as a heading with a list, show only the value without the label, or display as a quote or a larger gray paragraph. Attendees can be formatted similarly, and summary sections can be rendered as lists where indented subparts become bullet items.

How do live collections and “publish changes” work for book reviews?

A “my book reviews” page can include a live search that pulls in all nodes tagged as book review. When published, the page shows a cards-style overview (e.g., “Beginning of Infinity,” “Moby Dick”) with ratings and review text. If any underlying content changes after publication, the page does not automatically update; a “publish changes” button must be clicked to publish a new version. This keeps shared pages stable until updates are explicitly approved.

What’s the difference between publishing an overview page and publishing individual items?

Publishing the overview page creates a collection view that can show summaries directly on cards. Publishing individual book-review items creates dedicated pages for each book. After individual pages are published, the overview can switch to linking out instead of showing full review text, turning the collection into a navigation hub where readers click into each item’s published page.

How does Publish Page handle research graphs with referenced nodes and tabs?

For research, a question super tag can publish synthesis material alongside related claims and related thoughts, organized into tabs on the published page. Referenced nodes’ fields and content can also appear in the published output, meaning linked super-tagged items contribute their data to the page. There’s a key limitation: hiding fields uses a “hide field condition” set to always, so it can’t selectively hide fields only in some contexts.

What rich media features are supported in published pages?

Published pages can embed videos by pasting video content into Tana and then publishing. Images can be included inline, with “image text” rendered as an image caption. Header images are supported via drag-and-drop into the header area; the same header image also appears in card previews, making pages and collection cards visually consistent.

Review Questions

  1. When publishing a field in Tana, what display modes are available (e.g., label/value vs list vs quote), and how would you choose between them for meeting notes?
  2. How does the “publish changes” step affect live-search-based overview pages like a book-review collection?
  3. What limitation exists for hiding fields in research-related published pages, and how might that influence how you structure your super tags?

Key Points

  1. 1

    Publish Page turns structured Tana workspace content into polished, shareable web links without copy-paste workflows.

  2. 2

    Field-level formatting options let users choose label/value, headings, lists, quotes, or paragraph-only rendering per published section.

  3. 3

    Published pages use link-based access (“anyone with the link can view”) and unpublishing removes the page from public access.

  4. 4

    Live searches can power collection pages (e.g., all nodes tagged “book review”), but updates require an explicit “publish changes” action.

  5. 5

    Publishing individual items enables drill-down reading: collection cards can link to dedicated item pages instead of showing full text.

  6. 6

    Research publishing can include referenced nodes’ fields and content and uses tabbed organization, but field hiding is limited to a global “hide always” condition.

  7. 7

    Publish Page supports embedded videos and images, including draggable header images that also appear in card previews.

Highlights

Publish Page supports per-field presentation styles—turning the same underlying data into labels, lists, quotes, or paragraph-only blocks.
Live-search collection pages can pull in all tagged items, while “publish changes” prevents automatic updates from surprising readers.
Publishing individual review pages lets a collection page act like a navigable hub, linking out to deeper content.
Research publishing can include referenced nodes’ fields and content, but field hiding is controlled only via a “hide field condition” set to always.
Header images are drag-and-drop and automatically propagate to both page headers and card previews.

Topics