Content Creation

PromptPress Documentation

Back

PromptPress is designed for mixed workflows: manual editorial control where needed, automation where it improves speed and consistency.

Core Creation Surfaces

  • Studio (Article Studio): run structured article workflows and manual drafting flows.
  • PromptPress: fast text, image, and video generation.
  • ContentVault: manage draft and published content in one place.
  • ReleaseDeck: review workflow and campaign artifacts before publish.
  • PromptSpace: manage reusable prompts and model sources via Prompt Center and ModelSource.
  • AgentBase: run existing agents and review execution history. Agent Forge creation is planned and currently appears as a coming-soon action.

Which Tool Should You Use?

Use CaseBest Surface
Fast one-off draftPromptPress
Repeatable editorial processStudio + Workflows
Team review before publicationReleaseDeck
Final draft and publishing queueContentVault
Prompt and model governancePromptSpace
Agent execution and historyAgentBase

ContentVault Controls

ContentVault is the last-mile editorial surface for workspace articles and media. The article table includes status filters, category selection, tag/live-event filters, and manual refresh.

The filter bar is designed for narrow screens:

  • status filters remain horizontally scrollable;
  • All categories and Refresh share a compact row;
  • secondary tag/live-event filters wrap below without crowding the category picker.

Use Refresh after background syncs, imports, review actions, or external Strapi/worker updates when you need the newest article state immediately.

Step-by-Step: PromptPress to Published Article

Use this when speed is your priority:

  1. In PromptPress, generate a first draft from a clear topic prompt.
  2. Edit the draft manually for facts, structure, and tone.
  3. Save draft.
  4. Open draft in ContentVault.
  5. Complete metadata (title, category, tags, visibility, and subscriber access).
  6. Publish and verify the live article route.

Subscriber-Only Articles

ContentVault includes an Exclusive subscriber story checkbox in article edit mode. Turn it on when the full article should require an active paid subscription.

When an exclusive story is published:

  • Signed-out readers and readers without an active paid subscription see a locked article prompt instead of the full story.
  • The subscribe action opens the tenant subscription page at /subscribe.
  • The sign-in action returns readers to the article after authentication.
  • Active paid subscribers and the article author can read the full article.

Use this for premium reporting, members-only columns, paid analysis, and other content that should not be exposed in the public article body.

Step-by-Step: Studio Workflow to Published Article

Use this for repeatable team execution:

  1. Open Studio and choose a workflow.
  2. Start a run with a specific brief.
  3. Review step outputs and flagged issues.
  4. Open ReleaseDeck and approve or reject artifacts.
  5. Move approved output to ContentVault.
  6. Final edit and publish.

Artifact Review and Newsletter Reuse

Workflow and campaign artifacts should be treated as reviewable source material, not automatic public output.

  • Use ReleaseDeck for campaign artifacts that need approval before they become article drafts.
  • Use ContentVault for article-ready drafts, media, and workspace RAG assets.
  • Use Newsletter Reuse Campaign and template save flows when a sent or drafted newsletter should seed future campaigns.
  • Use the Newsletter Preview Current tab before scheduling or sending; it renders the current document separately from the editor controls.

When a workflow stops on a reviewable artifact, use Review and fix to edit the candidate output. Saving the fix continues the same workflow run from the failed or blocked step so the remaining downstream steps stay grouped with the original run. Use a full rerun only when the earlier plan, research, or draft should be regenerated.

Nepali Translation Assistance

When a site or PromptPress session is using Nepali output, the publish editor offers selection-based translation help for title, excerpt, and content fields:

  • idiomatic English to Nepali;
  • romanized Nepali to Devanagari;
  • literal English to Nepali for structure-preserving review.

PromptPress chat inherits the saved site language when opened. A manual language change still applies for the current session, but stale local storage or older chat history should not override the site language on the next load.

Step-by-Step: Prompt Governance in PromptSpace

Use this when content quality is inconsistent across runs:

  1. Open PromptSpace > Prompt Center.
  2. Duplicate an existing prompt instead of editing live blindly.
  3. Adjust instructions with one clear change per version.
  4. Test with one representative topic.
  5. Promote the version only after results improve.

Recommended Authoring Paths

Path A: Quick Publish

Use this for rapid turnaround:

  1. Draft with PromptPress.
  2. Edit for voice and factual accuracy.
  3. Save as draft.
  4. Final review in ContentVault.
  5. Publish.

Path B: Structured Campaign Flow

Use this for repeatable quality at scale:

  1. Start from Campaigns and select workflow.
  2. Run in Studio.
  3. Review artifacts in ReleaseDeck.
  4. Apply final edits in ContentVault.
  5. Publish after quality checks.

Quality Controls That Matter Most

Before publishing:

  • Title and key claims are factual and specific.
  • Persona tone matches your publication voice.
  • Guard rails pass for required policy checks.
  • Categories, tags, and metadata are complete.
  • Subscriber access is correct for public, member, or paid content.
  • Links and media render correctly.

Persona, Guard Rails, and Knowledge Graph

Use these together:

  • Personas: enforce style and voice consistency.
  • Guard Rails: enforce minimum quality and policy checks.
  • Knowledge Graph: preserve reusable facts and context.

This combination reduces style drift and post-publish corrections.

Publishing Readiness Checklist

  • Draft reviewed by an editor.
  • Required validations passed.
  • Campaign linkage confirmed if campaign-driven.
  • Public render preview checked.
  • Correct visibility and publish state selected.

Common Pitfalls

  • Publishing first-pass generated output without review.
  • Keeping too many overlapping personas.
  • Treating PromptSpace changes as ad hoc instead of governed updates.
  • Skipping metadata completion before publish.

Related Docs