Skip to documentation

Send & Export

Choose how each reviewed Article leaves Tallpine.

How Export Works

Tallpine is designed to be your writing and editing workspace. When your Articles are ready, you can export them for any existing blog or CMS. An export is a ZIP containing your Articles and attached Images, everything you need, neatly packaged and ready to drop into your publishing platform.

Send to WordPress (Optional)

Prefer not to copy files around? Connect a WordPress site, mark it as the Site default Publishing Destination, and choose whether reviewed Articles should be held, sent, or scheduled. WordPress Images are uploaded to the media library and the first is set as the featured Image. The remote permalink and delivery state appear on the Article. ZIP export does not consume Articles and keeps your content portable.

To connect WordPress:

  • In Site Profile & Settings, open Publishing Destinations and add WordPress with the Site URL, username, and an Application Password (create one in WordPress under Users, Profile, Application Passwords).
  • Choose Save & Test to verify the connection, then Set as default.
  • Choose the Site's default delivery behavior. You can override it in Customize. If delivery fails, the Draft remains in Tallpine and the Article page provides the safe recovery action.

Need a different stack? A generic webhook target using the Standard Webhooks specification hands each delivered Article to Zapier, Make, a custom endpoint, or a GitHub Action that commits the markdown to trigger a static-site rebuild. A webhook does not natively publish to Webflow, Framer, or Notion. Use the ZIP for those.

Choose a Delivery Outcome

  • Hold for Review: keep the Draft in Tallpine with no remote request.
  • Schedule: choose a future time and bind the schedule to one exact Publishing Destination. A later Site-default change does not retarget it.
  • Send: deliver now through a usable Publishing Destination. If delivery fails, Tallpine keeps the local Draft and exposes a recovery path.
  • Export: download portable files. Export records local export activity but does not claim that the Article is live.

What's in the Export

Each exported Article includes:

  • A markdown file with the full article content
  • YAML frontmatter (optional) with title, slug, excerpt, tags, and date
  • Associated images downloaded and included in the ZIP
  • Images are referenced with configurable paths so they work in your target system

How to Export

Export Drafts individually or in a batch. Re-download Exported Articles individually or in a batch.

  • Single Article: Open Articles, then choose Export on a Draft or an already exported Article.
  • Multiple Articles: Select several Articles with checkboxes and click "Export Selected" in the batch actions bar. Great for publishing a whole content series at once.
  • Re-export: Exported Articles can be re-exported anytime from the Exported tab. Handy when you've made updates or need the files again.

Export Settings

When the export dialog opens, you can configure a few options to match your blog setup:

  • Image path prefix: Where Images will live in your blog (e.g., /assets/img/). Set this to match your blog's image directory so that image references in your markdown point to the right place.
  • Include frontmatter: Add structured metadata at the top of each markdown file. Most static site generators (Hugo, Gatsby, Next.js) expect this. Turn it off if your CMS doesn't use frontmatter.
  • Save as Site defaults: Remember these settings for the next export from this Site.

What the First Export Changes

When you export a Draft:

  • The Article is marked as Exported in Tallpine
  • An export timestamp is recorded
  • The Article moves to the Exported tab

Re-exporting downloads the latest files and keeps the Article marked Exported. If you edited and saved it as a Draft first, the new export restores its Exported state. Remote delivery state remains separate.

Using Your Exports

The exported ZIP works with any blog platform. Here's how to use it with common tools:

  • Static site generators (Hugo, Gatsby, Next.js, Jekyll): Drop the Markdown files into your content directory and images into your assets folder. Frontmatter fields map directly to what these tools expect.
  • WordPress: Add it in Publishing Destinations for direct delivery, or use a Markdown importer with the ZIP.
  • Ghost, Substack, Medium: Copy the rendered content or use their import tools to bring your Articles in.
  • Any CMS: Markdown is portable and can be converted to the format your platform needs.

Tallpine is the workshop where you build your content. Direct Send to WordPress is optional; ZIP export means you always own your files and can move to any platform, any time.

Site Defaults

Choose Save as Site Defaults in the Export dialog to reuse the Image path and frontmatter choices next time.

Tips

  • Set your Image path prefix once and save it as default, so you will not have to think about it again
  • Use batch export when publishing a content series to save time
  • Keep frontmatter enabled if you use a static site generator. It saves a manual step
  • Re-export is non-destructive. Your Articles and settings are preserved, so feel free to export as many times as you need
PreviousImages