Publishing & Queue

Choose a content mode, destination, daily publishing time, and queue order.

Approved Articles publish through a tested destination in queue order, one per day. Connections and automatic publishing are optional; ZIP export remains available without a CMS connection.

Choose the policy deliberately: Review first requires a person at both the Idea and finished-Draft gates. Autopilot keeps manually queued work first, then prepares, approves, and publishes one Article for an otherwise empty daily slot.

Follow the Article from Draft to Published

• Drafts are waiting for review or approval.
• Queued Articles have been approved for managed CMS delivery. Review first waits for your approval; Autopilot queues them automatically.
• Published Articles have either been confirmed by a connected CMS or manually published as a ZIP.

Badges preserve the important detail within those tabs, including who approved an Article and whether CMS delivery is scheduled, publishing, failed, or delivered. Publish as ZIP moves an Article directly to Published without sending it to a CMS.

Supported Publishing Connections

Open Connections for the current Site. Tallpine supports:

• Self-hosted WordPress using a WordPress Application Password.
• Payload CMS 3.x using its public REST API, a collection API key, and a field mapping.

Tallpine's worker calls the selected CMS directly. You do not deploy a receiver, install a Tallpine SDK, or add a route to your website. Tallpine marks an Article delivered only after it refetches and verifies the CMS record.

Connect Self-Hosted WordPress

WordPress setup uses a dedicated user and a revocable Application Password. Follow Connect WordPress for the complete WordPress Admin walkthrough, screenshots, permission check, Tallpine form, first-delivery warning, and recovery steps.

Public delivery: Tallpine creates or updates a public WordPress Post. Use Review first when a person must approve the Article before it reaches WordPress.

Connect Payload CMS

Payload setup starts with a compatible Article collection, upload collection, and dedicated API-key user. Tallpine then connects directly to the Payload 3.x REST API. Your website needs no Tallpine plugin, SDK, or receiver route.

Follow Connect Payload CMS for the complete setup checklist, field mapping, tenant guidance, security steps, screenshots, and connection troubleshooting.

Choose Public Article Checks

When you add or edit a CMS Destination, Tallpine always checks the real public URL after a successful CMS delivery. The page must return HTML and remain tied to that exact Delivery. Additional checks for the visible Article title, URL or canonical slug, and published Images are all enabled by default. You can turn off an individual check when a Site's routing or rendering contract cannot support it; document-title, Open Graph, and heading structure are not required.

Check Access and Choose the Primary Link

A primary Connection is required for the managed queue to deliver completed Drafts. It is not required for Article preparation to begin. WordPress verification confirms its user capabilities and core REST shapes. Payload's access check confirms authentication and collection reachability, while its first authorized delivery proves mapped writes.

• Retest after changing credentials, permissions, URLs, or fields.
• Read the connection card's exact failure before replacing credentials.
• Changing the primary link affects the next queue delivery.

Daily Publishing

Publishing owns the Site's Content mode. Review first is the default. Autopilot becomes active only with an active subscription, a healthy primary Connection, and a saved daily time. When active, it uses the normal Idea-batch and Article allowances and requires no approval clicks for new work. Pause is always available.

Use Publishing when you want Tallpine to turn approved Ideas into a steady flow of Articles:

When a Site has no saved time, Tallpine starts at 09:00 in your browser's current timezone. Change the time or timezone whenever you like. Publishing always runs once on every local calendar day.

1. Connect, check, and make a destination the Site's primary link.
2. Set the Site's one daily publishing time and timezone.
3. Choose Review first and approve Ideas yourself, or turn on Autopilot to keep your queue first and prepare one Article ahead of an otherwise empty publishing day.
4. Reorder waiting Ideas when priorities change. Tallpine recalculates their future daily dates without changing the one-per-day limit.
5. Follow preparation and delivery in the Queue.

Workers claim Article work only when your account has available Article allowance and Pipeline execution capacity. A waiting item can safely remain in the queue until those prerequisites are available. Empty daily slots are skipped, and the publishing queue does not reserve Articles: the allowance remains pooled across the account's Sites. In Review first, the finished Draft stays private until its second approval. In Autopilot, the Site policy records that approval and the row is labeled Approved by Autopilot.

Publish Now or Export

• Publish now sends any ready Articles you select, one at a time in their visible queue order. Unselected Articles keep their automatic dates, and Tallpine stops the batch if a delivery needs attention.
• Publish as ZIP prepares portable files, moves the Article directly to Published, and makes no remote publishing request.

Publishing and exporting do not consume an Article. Allowance is charged once when fresh generation, Guided rewrite, or From scratch starts. Ready Articles can still publish when no generation allowance remains. See Billing for the full usage model.

ZIP export does not consume an Article. For exact Image-path examples, archive layout, Astro, Next.js, Hugo, and Eleventy setup, screenshots, and deployment checks, follow Publish a Static ZIP.

Export and Delivery Recovery

• ZIP preparation fails: keep the Article, check your connection, and retry. If a prepared download has expired, start a fresh export or re-export.
• Connection test fails: correct the URL, credentials, permissions, collection names, or field mapping, then test again before making the destination default.
• Queue delivery fails: the local Article remains in Tallpine. Read the delivery message, repair the exact bound destination, and use the recovery action shown.
• Status is still queued or running: do not submit a duplicate. Wait for the current action to complete or expose a retry.

For step-by-step failure guidance and what to include in a support request, see Troubleshooting & Support. For the final editorial check, return to Review & Edit Articles.