Content & publishing

Turn an assignment into a transparent writing plan.

Choose a page type, define the audience, and optionally paste reference headings. Plainview Tools builds a versioned planning scaffold and shows exactly what came from the template versus the pasted lines.

Runs in your browser
Deterministic templates
No page fetching
No signup required

Step 1 · Define the assignment

Set the editorial direction.

Target topic

Describe the page subject plainly. This is a planning label, not a measured search keyword.

52 characters200 maximum

Page type

A multi-section resource that supports a complete task.

Intended audience (optional)

49 characters500 maximum

Assignment context (optional)

112 characters1,000 maximum

Reference headings (optional)

Paste one heading per line. Plain lines, Markdown headings, and H1–H6 labels are accepted. Plainview Tools does not fetch competitor pages.

269 characters100,000 characters · 500 unique headings maximum

Everything runs in this browser. Nothing is uploaded, stored, searched, or sent to an AI service.

Step 2 · Review the planning scaffold

Structured content brief

Example brief

Brief ready. 8 outline sections, 4 reader questions, and 8 unique reference headings.

Working title

Website accessibility checklist for small businesses

Help Small business owners and freelance web designers understand “Website accessibility checklist for small businesses” and identify a practical next step.

Page type: Detailed guide
Audience: Small business owners and freelance web designers

Assignment context: Help a reader complete a practical pre-publish review without implying that one checklist guarantees compliance.

Reader questions

Questions the draft should resolve

What does “Website accessibility checklist for small businesses” mean in this page's specific context?
Which decisions, tasks, or questions should the page help the reader resolve?
What evidence is needed for the important factual claims?
What should the reader understand or do after using the page?

Outline

Suggested section sequence

Scope and outcome
Page-type template
Define the task, intended outcome, and boundaries of the guide.
- State what the guide covers and excludes.
- Describe the intended reader and outcome.
Prerequisites
Page-type template
List what the reader needs before starting.
- List tools, access, skills, or source material.
- Add safety or compatibility notes where relevant.
Core concepts
Page-type template
Explain concepts the reader must understand before the process.
- Define specialized terms with sources.
- Keep background tied to the task.
Step-by-step process
Page-type template
Break the task into a verifiable sequence.
- Give each true step one action and expected result.
- Add checkpoints instead of promising success.
Examples and edge cases
Page-type template
Demonstrate decisions and variations that affect the process.
- Use original or clearly attributed examples.
- Explain why an edge case changes the approach.
Troubleshooting
Page-type template
Help readers diagnose common, verifiable failure modes.
- Pair each symptom with checks before fixes.
- State when expert help or another source is appropriate.
Review and next step
Page-type template
Summarize completion checks and related actions.
- Provide a completion checklist.
- Link to a logical follow-up resource.
Reference themes to evaluate
Reference review
Review recurring terms from the pasted headings without copying their wording or order into the outline.
- Decide whether “test” belongs in this brief; it appeared in 2 pasted headings.

Research checklist

Evidence to gather before drafting

Verify every factual claim with an appropriate primary or otherwise trustworthy source.
Record publication dates and review whether time-sensitive details are still current.
Add original examples, experience, data, or analysis instead of mirroring reference pages.
Check that headings describe the section beneath them and follow a readable hierarchy.
Review the finished page for accessibility, accuracy, and a clear next step.

Source placeholders

[Source needed: definition, standard, or primary guidance]
[Source needed: evidence for a factual or numerical claim]
[Source needed: current product, policy, or process detail]
[Original evidence: example, test, interview, or first-hand observation]

Reference-heading review

Patterns in the supplied lines

8 unique

Parsed: 8
Unique: 8
Duplicates: 0
Omitted by limit: 0

Repeated terms to review

test2 headings

These are literal frequency patterns in the pasted headings—not search intent, demand, difficulty, semantic similarity, or a recommendation to copy another page.

Optional editorial planning range1,200–4,000 words per page

Detailed guide or tutorial. Plainview Tools editorial planning preset This is an editorial planning reference, not a ranking factor, quality target, or report of competitor performance.

Editable working draft

Revise the Markdown before export

3,216

Edit titles, prompts, source placeholders, and checklists here. The structured preview above stays unchanged so the original scaffold remains visible.

Editable content brief Markdown

# Website accessibility checklist for small businesses

**Content type:** Detailed guide
**Audience:** Small business owners and freelance web designers
**Editorial goal:** Help Small business owners and freelance web designers understand “Website accessibility checklist for small businesses” and identify a practical next step.
**Purpose / context:** Help a reader complete a practical pre-publish review without implying that one checklist guarantees compliance.

## Questions this page should resolve

- What does “Website accessibility checklist for small businesses” mean in this page's specific context?
- Which decisions, tasks, or questions should the page help the reader resolve?
- What evidence is needed for the important factual claims?
- What should the reader understand or do after using the page?

## Proposed outline

### Scope and outcome

Define the task, intended outcome, and boundaries of the guide.

- State what the guide covers and excludes.
- Describe the intended reader and outcome.

### Prerequisites

List what the reader needs before starting.

- List tools, access, skills, or source material.
- Add safety or compatibility notes where relevant.

### Core concepts

Explain concepts the reader must understand before the process.

- Define specialized terms with sources.
- Keep background tied to the task.

### Step-by-step process

Break the task into a verifiable sequence.

- Give each true step one action and expected result.
- Add checkpoints instead of promising success.

### Examples and edge cases

Demonstrate decisions and variations that affect the process.

- Use original or clearly attributed examples.
- Explain why an edge case changes the approach.

### Troubleshooting

Help readers diagnose common, verifiable failure modes.

- Pair each symptom with checks before fixes.
- State when expert help or another source is appropriate.

### Review and next step

Summarize completion checks and related actions.

- Provide a completion checklist.
- Link to a logical follow-up resource.

### Reference themes to evaluate

Review recurring terms from the pasted headings without copying their wording or order into the outline.

- Decide whether “test” belongs in this brief; it appeared in 2 pasted headings.

## Word-count planning reference

1,200–4,000 words per page.

This is an editorial planning reference, not a ranking factor, quality target, or report of competitor performance.

## Research checklist

- [ ] Verify every factual claim with an appropriate primary or otherwise trustworthy source.
- [ ] Record publication dates and review whether time-sensitive details are still current.
- [ ] Add original examples, experience, data, or analysis instead of mirroring reference pages.
- [ ] Check that headings describe the section beneath them and follow a readable hierarchy.
- [ ] Review the finished page for accessibility, accuracy, and a clear next step.

## Source placeholders

- \[Source needed: definition, standard, or primary guidance\]
- \[Source needed: evidence for a factual or numerical claim\]
- \[Source needed: current product, policy, or process detail\]
- \[Original evidence: example, test, interview, or first-hand observation\]

3,216 characters100,000 maximum

This is a deterministic planning template, not an AI-generated strategy.

Method version 1.0. It does not fetch results, identify search intent, estimate traffic or competition, judge coverage, or predict rankings. An editor should revise every section for the real reader and available evidence.

How the brief is assembled

A visible method with an editor still in charge.

This tool does not search the web or ask a language model to infer a strategy. It combines a fixed page-type template with the details supplied in the form, then reports literal repeated terms from optional reference headings for review.

Template scaffold

The selected content type chooses a fixed, versioned outline template. The target topic, audience, and context only fill clearly identified planning fields; they do not generate factual claims.

Reference review

Reference headings are pasted by the user and parsed locally. Their order is not copied into the outline. Repeated Unicode word terms are summarized as themes for the editor to evaluate.

Optional length context

Optional word-count guidance reuses Plainview Tools' versioned editorial planning presets. It is a planning reference, not a ranking target or a statement about competitors.

Version 1.0 boundary

Theme frequency counts how many unique pasted headings contain each normalized Unicode term. A term must occur in at least two unique headings to appear as a theme. Target-topic terms, common English function words, and generic outline labels are excluded. Scripts without spaces may remain one contiguous term because no language dictionary or AI model is used.

Generation is deterministic and browser-only. The helper does not fetch pages, call an API, store input, or execute pasted markup.

The output contains prompts and placeholders, not factual research. It cannot determine search intent, demand, competition, topical authority, or whether a section is necessary for a particular reader.

Primary planning and structure guidance

The guardrails behind the prompts.

Source check: August 24, 2026. These sources support people-first planning, descriptive headings, accessible writing, and explicit user needs. They do not validate the generated section sequence, supply keyword data, or promise rankings.