Contix Pro Documents
Version 1.0
Build a content project, prepare a topic, review production checkpoints, and deliver a controlled publishing package.
Start with installation →Meet Contix Pro
Contix is a WordPress content workspace that connects project context, topic research, structured production, review, and publishing.
Work from a clear brief. Review the generated evidence and saved revisions before transferring a finished article to WordPress.
The Pro 1.0.x workspace is separate from the historical Dev 2.5.3 line. Use the interface and package belonging to your installed Pro version.
Install and activate Contix
Prepare the installation
Back up the site and obtain the Contix Pro ZIP from your ARN account. Keep an existing content database and historical packages intact during an upgrade.
Upload and activate
Open Plugins → Add New Plugin → Upload Plugin, choose the ZIP, select Install Now, and activate ARN Smart Contix. A network administrator handles plugin upload on multisite.
Activate Pro
Open ARN Contix and use the License screen. Enter the complete one-time ARNA activation code from your account or activation email, select Activate, and confirm active status for this site address. Inspect expiry and connection details.
A Pro license does not provide an AI provider subscription or API balance. Configure those independently in Settings. Keep ARNA codes and provider keys out of screenshots and support messages.
Connect and verify an AI provider
Open System → Settings. Contix supports multiple provider records and requires one verified default provider for engine work.
Choose a provider and save its credential
Select the provider, enter its API key and relevant configuration, and select Save Provider. For a custom provider, use its public HTTPS API base URL. Private or reserved network endpoints are rejected.
Verify storage and runtime
Run SHA256 Control to check the stored credential fingerprint, then Test Runtime to confirm actual provider access. Review connection, permissions, billing/quota, and runtime statuses. A configured key alone does not mean Runtime Ready.
Set the default provider
Select a Runtime Ready provider as the default. Confirm the chosen provider in Production before starting a run. If storage fails, ask your host to enable the supported OpenSSL AES-GCM or Sodium encryption capability.
Enter input and output prices per million tokens if you want cost estimates. Use the rates for the model you actually configure. A zero rate leaves that portion unpriced; the estimate is not your provider invoice.
Use the provider’s current model list and permissions when configuring access. No fixed model name in this guide is required.
Create a project and define its context
Create the project
From Dashboard or Overview → Projects, enter the project name, language, region, and main goal. Select Create Project and Unlock Workspace on the first-run card, or Create Project when more projects already exist.
Describe the site
Open the project and save relevant context: audience, business purpose, content goals, and constraints. Be specific about whom the site serves and what a useful article should accomplish.
Collect the site inventory
Use the project’s site-scan and understanding actions where offered. The inventory collects WordPress information; site understanding organizes that evidence. Saving context does not itself run research or content generation.
Keep project language and region aligned with the intended publication. Revisit context after a major business or website change. Deleting a project can also remove its related context, state, queue, and understanding records; review it carefully before confirming.
Create a structured Topic Request
Open Overview → Topics and select the correct Project.
- Enter the primary keyword or topic and optional secondary keywords.
- Choose the content type: Blog Article, Landing Page, Product Content, Service Page, Comparison, Local SEO, or Refresh Existing.
- Choose search intent and define the audience, priority, language, region, and goal.
- Select Create Topic Only to prepare the request without starting production, or use Create Automatic Draft / Start Guided Workflow after the provider is ready.
Example: How to preserve family photographs, informational intent, a general audience, English language, and a goal of explaining a practical preservation process. Add any exclusions and required facts to the brief rather than relying on the keyword alone.
Existing requests provide Resume, View, Edit, and Delete. Resume opens the appropriate saved stage. Confirm that the selected Topic still belongs to the expected Project.
Start Automatic Draft or Guided Workflow
Open Production → Production. Choose an existing Project and Topic Request.
| Mode | Use it when |
|---|---|
| Automatic Draft | You want the persistent pipeline to work through the topic, language pack, research, and validated draft, stopping for a real blocker. |
| Guided Workflow | You want to pause after each checkpoint, review its result, and approve before continuing. |
Confirm readiness
Check the displayed default provider and Runtime Ready status. Read any blocker explaining a missing project, topic, or provider.
Start and monitor
Select the workflow mode and Start Pipeline. Monitor the current checkpoint, completed stages, and recorded error messages. A persistent run saves backend checkpoints, so navigation alone does not create a new run.
Review guided checkpoints
In Guided Workflow, select Review Current Checkpoint, inspect the contextual review screen, then use Approve & Continue to resume the pipeline. Correct the actual blocker if the run pauses or fails.
Review research, strategy, and architecture
Guided checkpoints open the relevant content workspace. Follow the stage shown by the current run instead of restarting from Topics.
- Language and research: review the locale, audience, evidence, sources, and coverage. Remove unsupported assumptions and verify source relevance.
- Strategy: check the intended page purpose, search intent, and required reader outcomes.
- Architecture: review section structure and the contracts that guide section production. Ensure that the article has a logical sequence and no duplicated sections.
- Writing and validation: inspect section output and reported gaps, then use the available repair or revision workflow for the specific issue.
Changes to an upstream input can make downstream artifacts stale. Regenerate or review affected stages when Contix requests it. An old result should not be treated as current merely because its text remains visible.
Review drafts and saved revisions
Open Production → Drafts for the current Topic and article. Check the selected revision before editing or approving anything.
- Read the full draft and compare it with the topic’s goal and architecture.
- Check factual claims, examples, source references, headings, tone, and required sections.
- Use the available section repair or revision action for a specific issue. Recheck surrounding sections afterward.
- Finalize the intended article revision, then inspect Analysis before moving to publication.
A generated draft is separate from a WordPress post. Completing production does not mean the article has been published on the website.
Resolve content analysis blockers
Open Production → Analysis. Read both the overall diagnostic and the individual issues.
Prioritize missing required content, unsupported claims, inconsistent structure, and outdated inputs. Use the recommended repair or review path, then run the relevant analysis again on the new revision.
Analysis and publication packages depend on the current article revision and upstream artifacts. If you change the article, verify that the analysis and later packages are rebuilt or explicitly current before transfer.
A high diagnostic score is an internal quality signal. It does not guarantee rankings, traffic, conversions, or factual accuracy.
Build the publishing package
Open Publishing → Publishing with a finalized article and current analysis. Read any entry-gate issues first.
Metadata & Schema
Generate and review metadata variations based on the current article. Select and confirm the variation you want. Use only schema types supported by the actual page content.
Links & Sources
Review proposed links and evidence. Confirm destinations and source relevance, then complete the human review confirmation. Metadata selection must be current before this stage opens.
WordPress transfer
Review the available content type, editor mode, and transfer settings. Use the offered draft/review path first and inspect the resulting WordPress item. Publish only after checking the real editor content, metadata, layout, and links.
The package is locked to the current article revision, analysis ID, and upstream package hash. If an earlier stage changes, rebuild the dependent package before transferring again. Record the resulting WordPress post ID so you can identify the correct item.
Monitor queue and operations
Publishing → Queue shows queued work. System → Operations provides the operational view.
- Identify the job by Project, Topic, stage, and run rather than its age alone.
- Distinguish Pending, Running, Retrying, Completed, and Failed states where shown.
- Read the recorded failure before retrying. Fix provider access, missing inputs, or other dependencies first.
- Use the existing run’s continuation controls for durable checkpoints. Avoid starting duplicate pipelines for the same Topic.
Background progress depends on the site’s working scheduling/runtime environment. If jobs stop moving, review operational diagnostics and ask your host to check WordPress cron and server errors.
Refresh and extend existing content
Use these workspaces after the core project, topic, and publication flow is established. Each screen exposes its own required inputs and saved results.
| Workspace | Practical use |
|---|---|
| Refresh | Review an existing item and plan an update from current evidence. |
| Commerce / Social | Prepare product-related or social output in its relevant context. |
| Performance / Relationships | Inspect available performance evidence and relationships between content. |
| Experiments / Learning / Campaigns | Organize controlled improvements and the lessons or campaign context behind them. |
| Integrations / Release Readiness | Review external connections and readiness checks before relying on the workflow. |
An empty panel means the needed data or artifact has not yet been supplied. Complete the screen’s prerequisites before interpreting its outputs. Do not assume that a connected external service has successfully imported data until its result is visible.
Your first successful content workflow
- Activate Contix Pro and verify one default AI provider.
- Create a Project with a specific audience, language, region, and goal.
- Create one Topic Only, then review its brief.
- Start Guided Workflow and approve each checkpoint after checking its evidence.
- Review the draft, fix its issues, and finalize the intended revision.
- Complete Analysis, Metadata & Schema, and Links & Sources.
- Transfer to WordPress for review and inspect the real frontend before publication.
Keep the number of simultaneous first runs small so that failures and usage remain easy to understand. For a plugin update, back up both the website and the content workspace, update the verified Pro package, and check existing projects and saved runs afterward.
Troubleshooting
Production says the provider is not ready
Saving an API key is only the first step. Complete SHA256 Control, Test Runtime, and selection of a Runtime Ready default provider. Review permissions, model access, billing, and quota errors.
Start Pipeline is unavailable
Create a Project and Topic Request, confirm their relationship, and configure a ready default provider. Read the launcher’s readiness notice.
A run paused, failed, or appears stuck
Read the current checkpoint and queue/operation error. Guided Workflow may be intentionally awaiting approval. Fix the stated blocker and resume the existing run. Check cron/runtime health if background jobs do not advance.
Publishing is blocked or a package is stale
Finalize the current article revision and complete its analysis. Confirm metadata selection and human link review in order. Rebuild downstream packages after upstream edits.
My content is not visible on the website
Inspect whether WordPress transfer created a draft or another unpublished state. Open the recorded WordPress item and verify its status and frontend. A completed Contix draft is not itself a published post.
License activation or integrity check fails
Use the license connection details to identify code/domain or HTTPS problems. For missing or altered product files, reinstall the complete verified Pro package instead of modifying protected files.
For support, include Contix version, WordPress/PHP versions, Project/Topic/run IDs, the stage and status, and a sanitized error message. Omit API keys, ARNA codes, and private article inputs.