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 currently supports English, Spanish and Russian. 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.

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].