Inkpilots

Article Lifecycle and Editor

Workflow

Articles are the production layer of Inkpilots. Planning and schedules decide what should happen. Articles are where that planned work becomes an actual deliverable: a draft, a structured document, a revised editorial asset, and eventually a published or archived record.

This page explains how articles behave in the current product, what users manage inside the article editor, and how article states should be used operationally.

What the article area is for

Use the article area when your team needs to:

  • create a new draft manually,
  • queue a new AI-assisted article,
  • filter content by status or assigned agent,
  • edit article structure and metadata,
  • prepare content for publication or archival.

Articles are not only text containers. In Inkpilots they are structured content records with editing history, metadata, layout blocks, and workflow state.

How an article enters the system

The current dashboard supports two practical starting points for article creation.

Create an empty article

Use this when a writer or editor wants to start from a blank draft. This is the right path when the team already knows the topic and wants direct control over structure from the beginning.

Assign an article to AI

Use this when the workspace wants the system to generate a draft from a supplied title. In the current create flow, AI-assisted creation can be configured with:

  • file search,
  • image generation,
  • web search.

This makes AI article creation a controlled drafting path rather than a generic one-click generator.

Article states in the product

At the article level, Inkpilots keeps status deliberately simple. The dashboard currently filters and organizes articles using three states:

  • Draft for work still being developed,
  • Published for work that is ready for external visibility or final delivery,
  • Archived for work that should be retained without staying in the active publishing stream.

This simplicity is useful. More detailed operational movement usually belongs upstream in schedules and assignments. The article status should answer one practical question clearly: is this content still being worked on, already live, or intentionally set aside?

What users can do from the article list

The Articles tab is the operating surface for browsing and managing article inventory. In its current form it supports:

  • filtering by assigned agent,
  • filtering by status,
  • sorting by updated date, created date, title, or status,
  • switching between card and row layouts,
  • paging through the article set,
  • opening the article editor for direct work.

This matters because article management is not only about opening one document at a time. Teams need a fast way to inspect the state of a whole workspace and decide what deserves attention next.

Editor

Block editor has many capabilities. One of the most important is inline ai features use / to open command tools then you can ask for review, modification, image generation inline without leaving the editor. Agentic action can be run inside the editor writing, ai will create modification and suggestions, results will not be applied automatically, editor will show you a difference, it is your decision to accept and reject the ai changes.

What the editor is designed for

The article editor is where structured content is produced and refined. It is not a plain text field. It is a block-based editing surface intended for real editorial work.

The current editor stack supports structured blocks such as:

  • paragraphs,
  • headings,
  • lists,
  • quotes,
  • dividers,
  • code blocks,
  • embeds,
  • images.

This structure matters for two reasons. First, it makes long-form content easier to shape and scan. Second, it gives the article enough internal structure to support richer publishing and downstream reuse.

What belongs inside an article

In practice, an article in Inkpilots includes more than its body copy.

The current editing flow supports or exposes:

  • title,
  • cover image,
  • SEO description,
  • keywords,
  • tags,
  • structured content blocks,
  • article status,
  • workspace and agent relationships where relevant.

The header update flow is especially important because it keeps title, image, and discoverability data in one place. Users can update cover imagery, manage descriptions, and maintain keywords and tags without treating metadata as an afterthought.

Cover image and metadata management

Inkpilots provides a dedicated header-editing surface for article presentation metadata.

Users can currently:

  • upload a cover image,
  • paste a cover image URL,
  • update the article title,
  • edit the meta description,
  • manage keywords,
  • manage tags.

This is an important part of article quality. A strong article is not only well written. It is also well packaged for discovery, reuse, and public presentation.

AI-assisted editing inside the article workflow

The current editor is more than a writing space. It also includes agentic assistance and suggestion handling within the edit experience.

That matters because AI in Inkpilots is not limited to initial generation. It can also support revision work inside the article lifecycle itself. The correct operating model is:

  • use AI to accelerate drafting or revision,
  • keep the article as the controlled source of truth,
  • review suggestions before treating them as final content.

Users should think of the editor as a supervised AI-supported environment, not an automatic publishing channel.

Recommended lifecycle in practice

For most teams, the article lifecycle should look like this:

  1. Start from a planned topic or a clear title.
  2. Create an empty draft or queue an AI-assisted draft.
  3. Shape the body using structured blocks.
  4. Update header metadata, cover image, and discoverability fields.
  5. Keep the article in draft until the output is genuinely ready.
  6. Publish only after the content and presentation are aligned.
  7. Archive content intentionally when it should remain in the system without staying active.

This sequence keeps the article area focused on production quality rather than on informal note storage.

Good operating practice

Use draft status actively

Draft should mean active work, not abandoned work. If a draft is no longer relevant, archive it or move it back into planning discussion.

Treat metadata as part of the article

Do not postpone title, image, keywords, and description decisions until the last minute. They are part of the final output quality.

Use structured blocks deliberately

Strong articles are easier to read and maintain when headings, lists, code, quotes, and media are used intentionally rather than as decoration.

Keep AI assistance supervised

AI can accelerate drafting, but the article editor should still be the place where human editorial judgment decides what remains in the final document.

Common mistakes to avoid

  • Treating articles as disconnected from planning and schedules.
  • Letting draft status become a permanent holding area.
  • Writing body content without completing metadata and cover information.
  • Using AI-assisted creation without reviewing structure and accuracy afterward.
  • Treating the editor as a plain text field instead of a structured publishing surface.

How this page connects to the rest of the handbook

Use this page together with:

Related guides