Publicasta is a publishing workspace for authors who want to create channels, publish articles, manage translations and use API-assisted workflows without turning publishing into a control panel.

1. Quick start

  1. Sign in with your account.
  2. Create a publishing channel.
  3. Write an article in the channel.
  4. Add images, video embeds or translations if needed.
  5. Publish now, save as draft or schedule publication if your account has access to scheduling.

The simplest flow is: create a channel, write one article, publish it. Everything else can be added later.

2. Channels

A channel is the public space where your articles live. Each channel has a public address, title, default language, description and optional cover image. Use one channel for one publication, project, brand, newsletter or topic.

Some account levels may limit how many channels you can create or whether collaborators can be invited.

3. Articles and drafts

An article can be saved as a draft, sent to moderation, scheduled, published or removed from public view. Drafts are private. Published articles are visible to readers. If you edit an already published article, the current public version may stay visible while the new revision waits for approval.

The editor saves work automatically, but you should still check the status near the publishing controls before leaving a long writing session.

4. Languages and translations

Publicasta separates interface language, channel language and article language. The site interface is available in multiple languages. Channels and articles can use more languages.

Translations are full article versions. They can have their own title, excerpt, text, images and links. A translation is not just a small field inside the original article.

5. Images and video

You can upload images into articles. Uploaded images are processed into a web-friendly format. You can also embed supported external video links. Videos are embedded from providers; Publicasta does not host uploaded video files.

Only upload or embed media you have the right to use. Use captions and alt text where useful.

6. Moderation

Publishing may require moderation. Moderation can be automatic, manual or both. Scheduled articles are reviewed before the scheduled publication time where possible. If an article or revision is waiting for moderation, the interface will show its status.

Readers can report articles and comments. Confirmed reports may affect account trust and future moderation flow.

7. Comments and reactions

Readers may react to articles and, where enabled, leave comments. Comments can have one level of replies. Comment controls may depend on account level. Authors should treat comment spaces as part of their publication and keep them consistent with the Publishing Rules.

8. API publishing

API publishing lets external tools or AI agents create articles, upload images, add translations, check status and schedule publication. API access depends on account level.

Public API documentation is available at /api-docs. API keys are created in account settings and are shown only once. Store them securely and revoke keys you no longer use.

8.1 Own domains

On an eligible plan, a channel owner can connect an own domain in channel settings. Enter the domain, add the displayed TXT record to prove control, and then point the domain with CNAME to connect.publicasta.com. For a root domain, use CNAME flattening, ALIAS or ANAME if your DNS provider supports it. DNS may take time to propagate; Publicasta refreshes pending statuses automatically, and you can also request a check from the settings page.

When Cloudflare has validated the hostname and issued SSL, make the domain primary. The channel becomes available at the domain root, articles use /{article}, and Publicasta channel URLs redirect to the primary domain. RSS, sitemap, canonical links, translations and sharing links follow the same domain.

Readers can sign in through Publicasta and then use comments, reactions, subscriptions and favorites on the channel domain. The sign-in screen identifies Publicasta because Publicasta operates the account and reader services. An own domain changes the channel address and branding; it is not a white-label service. Only the owner manages domains, while editors can continue working through the Publicasta dashboard.

Analytics can be filtered by host. A custom domain needs its own Google Search Console property controlled by the domain owner. If CAA records are present, they must allow a certificate authority supported by Cloudflare. If a plan no longer includes the domain, a displayed grace period applies before routing is disabled; articles are not deleted and remain available at their Publicasta address.

9. Account levels and features

Some features are available to everyone. Others may require Plus, Pro or another account level. Feature access can change as the product develops. The interface should show when a feature requires a higher level.

10. Reports, rules and appeals

The Publishing Rules explain what is allowed and what is prohibited. If your content was moderated and you believe the decision was wrong, contact [email protected] with the article URL, account email and a clear explanation.

11. Troubleshooting

  • I cannot publish: check whether the article is waiting for moderation, missing required fields or scheduled for later.
  • I cannot edit: a pending moderation version may need to be withdrawn before editing.
  • Images do not appear: refresh the page and check whether the image was inserted as an image, not just a file name.
  • Wrong language is shown: use the article or channel language selector if translations are available.
  • API request failed: check the API key, channel slug, account level and validation errors in the JSON response.

12. Contact

For support, contact [email protected]. For general questions, contact [email protected].

Image watermarks

Plus and Pro channels can add the channel avatar, a transparent PNG or WebP, or a text mark to newly uploaded article images. The channel setting is the default; before a manual upload you can apply or skip it for that image.

The mark is baked into the one stored WebP and cannot be removed later. Existing images, channel covers and channel avatars are not changed. Upload the source image again if you need a different or unmarked result. A watermark is not DRM and is not proof of copyright ownership.

Work with an AI agent

A compatible browser AI agent can inspect an open Publicasta editor, prepare exact draft changes, create translations, upload images and help with an editorial schedule through the site’s own tools.

Read the guide and copy ready-to-use requests

Custom domains and knowledge bases

A single channel can serve the same articles and translations on several language or regional domains.

Open the domain and mirror guide

Homepage visibility

Homepage visibility is available on all plans. It affects only the Publicasta homepage, not privacy, search, related articles, or subscriptions.

In the channel editor, the homepage checkbox is in the SEO section. In the article and translation editors, choose homepage visibility in Settings.

Homepage visibility

Article and channel contents

In article Settings, enable Show article contents. Add at least two H2 headings; H3 headings become subitems. The setting is shared by translations, but each language uses its own headings.

Section links work even with contents disabled. Use # beside a public heading to copy its link, or Link to section in the editor. Renaming a heading preserves its link; deleting and recreating it may create a new link. API clients replacing HTML must preserve heading id attributes.

For a guide, publish an index article with links such as ./getting_started, then pin it. In channel SEO settings, enable Use the pinned article as channel contents and check the preview. H2/H3 headings group the links. Link labels and order are preserved. Only published articles from the same channel appear; external links, duplicates and the index itself are excluded. Publish changes to the index to update the menu.

Contents start above the article. After scrolling past them, navigation appears beside the text on wide screens or as an expandable bar on narrow screens. The current section is highlighted. When both menus exist, switch between In this article and Guide sections. Guide links keep the current domain and use the reader’s language unless the source link specifies one. These settings do not publish articles or change homepage visibility.

Reader preferences are stored only in this browser for the current domain. On wide screens, use the arrow in the floating menu to move it left or right. Collapsing or expanding the contents above an article becomes the default for other articles; floating navigation keeps its own behavior.

Article editor and formatting

Learn which formatting is supported, what the More menu does and how external content and API HTML are handled.

Open the editor and formatting guide

Preferred reading language

On your first visit, Publicasta remembers your browser's first preferred language for reading, even if no article is available in it yet. Changing the interface language does not change this preference.

Registration transfers your reading preference to your account. The "Preferred reading language" field below Interface language lets you search by language name or code, or choose from the list. Signing in uses the existing account preference and updates this browser; signing out retains it.

Selection order: an explicit lang in the link, reading language, domain fallback, article default, channel default, then the first available published translation in language-code order. Unavailable translations are skipped.

Automatic home and channel feeds use general article links. Explicit language selection and search results link to that translation. Copy article link lets each recipient read in their own language; Copy translation link fixes the language. Selecting a translation does not change the saved reading preference.

Publication notifications and daily or weekly digests select article titles, excerpts and links using the reading language; the email interface follows the interface language. Existing accounts without a reading preference keep their previous email language until their first web initialization.

With 10 or more published versions, the translation menu offers search by code or language name. You can still select a language without typing; opening the menu does not focus the search field.

Publishing API v2

Use v2 for new article integrations. Draft upload and final submission are separate operations. Public reading and channel administration retain their existing APIs.

Create a draft with its primary translation, upload images with page_slug, save the other translations in batches, verify them, then submit status with the exact expected_languages set. A 202 response means review has started, not that publication is complete.

Each JSON write accepts at most 20 translations and 2 MiB (2,097,152 bytes), both limits apply. An article supports up to 700 translation records; this is a capacity limit, not a promise of 700 supported languages. Oversized requests return 413 before saving anything.

API v1 remains supported with full responses. It is not deprecated and has no retirement date.

API v2 · API v1

The homepage first selects the translation using your reading preferences, then checks whether that version is eligible for the homepage. If it lacks an image or fails another eligibility requirement, the article is hidden from your homepage rather than shown in another language. It remains available in the channel and through its direct link.