docs: update publish task naming and add unpublish section - #2855
Draft
jgagne wants to merge 9 commits into
Draft
Conversation
Contributor
|
❌ Preview build for this PR (commit |
jgagne
changed the title
- Fixes the SEO title field label mismatch with its own required-field error. - Renames the Publication tab to Publishing. - Renames the Display information section to Page details. - Renames SERP preview to Google preview. - Fixes Page preview and Google preview from Title Case to sentence case. - Renames the Examples tab to Example tasks. - Removes redundant phrasing across the page. - Adds a section on unpublishing a task. - Placeholder: unpublish screenshot pending capture. - Placeholder: Publish status filter pending shipping.
jgagne
force-pushed
the
docs/publish-task-update
branch
2 times, most recently
from
August 5, 2026 21:05
55b393b to
0ce96c8
Compare
Copy fixes: - "what it does, what inputs to provide, and what output to expect" (parallel and user-centered, replaces "it produces") - "more discoverability means more paid runs" (docs voice, not marketing) - Slug: spell out constraints (lowercase, hyphens, no spaces) - "preview updates as you type" (replaces "live preview how fields propagate") - "your original task" (consistent possessive) - Remove "automatically" from AI generation line (redundant with AI icon) - Unpublish: state outcome of confirm action New feature documentation: - Use case field (required, for Store categorization) - AI icon for generating SEO title and description - Publishing tab progress guide - Publish confirmation (privacy reassurance) - After publishing: share dialog and View landing page button - Privacy note in "After a user tries your task" - Prerequisites: blocking state when schemas are missing
- Remove "public use-case" (redundant, not a search term)
- Remove implementation detail ("by completing the... sections")
- Add benefit: discoverable on Google and by AI agents
- Plain language pass on AI discovery section
jgagne
force-pushed
the
docs/publish-task-update
branch
from
August 5, 2026 21:09
0ce96c8 to
2f0165c
Compare
jgagne
force-pushed
the
docs/publish-task-update
branch
from
August 5, 2026 21:13
540686a to
bf5e6d3
Compare
- "task-publication-tab" to "task-publishing-tab" (matches renamed UI) - "task-display-information" to "task-page-details" (matches renamed section) - Alt text now describes what the screenshot shows, not just labels it
jgagne
force-pushed
the
docs/publish-task-update
branch
from
August 5, 2026 21:22
741d4ce to
540e821
Compare
- Replaces two rows with real example task titles currently live on Google Maps Scraper, verified on apify.com. - Keeps the "Generic task/Specific task" table headers as-is. - Tightens the Amazon and Yahoo Finance strong titles to a single focus each, matching the section's own stated principle. - Fixes the intro line to name all three Actors shown in the table. - Updates a leftover "dentist" reference and the URL structure example to match the new table.
- Changes "Analyze local business competitors with AI" to "Analyze San Francisco business competitors with AI", naming an actual location instead of the placeholder word "local". - Updates the matching sentence below the table to reference the new phrase. - Simplifies the sentence after the table to "Each task focuses on a specific industry, location, or workflow", removing a redundant modifier on "task". - Note: the San Francisco example is no longer verbatim from the live Google Maps Scraper Examples tab, it's a modified version. The other two rows in this table remain our own examples, not live ones.
jgagne
force-pushed
the
docs/publish-task-update
branch
from
August 6, 2026 14:21
d0ba748 to
8885897
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
New feature documentation
SEO
Naming (from original PR)
Screenshots to update
task-publishing-tab.webptask-page-details.webptask-unpublish-dialog.webpactor-examples-tab.webptask-input-section.webptask-dataset-schema.webptask-landing-page.webpCopy lint pass