docs: reflect Apify-assigned Actor categories#2645
Draft
marcel-rbro wants to merge 1 commit into
Draft
Conversation
Remove the "Categories" field from the "Make your Actor public" steps; creators no longer pick categories from Console. Add a short Categories subsection explaining that Apify assigns categories and pointing to support for disputes. Refs #2581. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
⏳ Preview for this PR (commit |
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.
Refs #2581. Categories will now be Apify-assigned, not creator-selected.
Removes the Categories field from the publish steps in
publish.mdxand adds a short Categories subsection explaining the new behaviour and how creators can dispute their assignment via Apify support.Open questions for Honza Kuželík (Discovery) — blocking final review
categoriesonacts-post/act-putstill accept creator writes, get ignored, or get rejected? Affects whether to mark the parameter deprecated in the OpenAPI spec in a follow-up.https://apify.com/contact(the canonical pattern in other publishing pages). Confirm that's the right route for category disputes vs. a specific email/form.Follow-ups (separate PRs, not this one)
images/actor-display-information.webpwill need re-capture once the Categories field is gone from Console.categoriesare being dropped, update the OpenAPI parameter doc onacts-post/act-put.Draft until the three questions above are confirmed.