Articles

Article Generator creates queued AI-assisted article drafts inside a Screpy project. The aim is not to publish more pages; it is to produce a draft that a knowledgeable editor can turn into a complete, useful answer with a sensible next step.

Create a draft

1. Select Generate Article.
2. Enter a specific title or article brief.
3. Choose the output language and tone.
4. Select the reasoning level—Low, Medium, or High—and add system instructions when your editorial standards need extra context.
5. Choose Generate to send the draft to the generation queue.
6. Return to the project list to follow the status, language, tone, model, and generated date. Export the list as CSV or Excel when needed.

Generation uses the project’s available article allowance. The counter beside the page title shows the current usage against the project allowance.

Choose the job the article must do

Define the reader, the question, and the outcome before drafting. A beginner explainer, a technical implementation guide, and a product comparison can cover the same phrase but require different structure and evidence. The title and introduction should make that scope clear so the reader can quickly decide whether the page is for them.

Build the article around the decisions the reader must make. Include practical steps, limits, examples, and links to first-party sources when a claim depends on a product, platform, or policy. Remove sections that restate the obvious without helping the reader choose or act.

Publish with a maintenance plan

Article Generator creates a draft; it does not publish content to your website. Review factual claims, tone, links, uniqueness, and the final on-site format before moving the content into your CMS. Mark the content owner and review it when the product, interface, provider, or search behavior changes. A short, accurate article is more valuable than a long guide that no longer reflects the workflow.

Before you publish

• Does the opening answer the main question?
• Can a reader follow the process without guessing at a missing step?
• Are examples and claims based on the current product or a cited source?
• Does the page link to the next relevant task rather than ending at a dead end?