Skip to content

docs: document FAQ section for published task - #3015

Merged
Valentin-B117 merged 10 commits into
masterfrom
feat/add-faq-section
Oct 29, 2026
Merged

Valentin-B117 merged 10 commits into
masterfrom
feat/add-faq-section

Conversation

@Valentin-B117

Copy link
Copy Markdown
Contributor

Documents the optional FAQ section in the task Publishing tab: AI generation, manual editing, the 10-item and 120/250-character limits, publicConfig.faq in the API, and how the FAQ renders on the landing page and its markdown version. Follows apify/apify-core#30398 and apify/apify-web#6592, ref apify/apify-web#6477.

The feature is still admin-only so the merge will not happen until the feature flag is off. Otherwise the docs describe a section most users can't see yet.

@apify-service-account

apify-service-account commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

🗑️ Preview for this PR was deleted.

@Valentin-B117 Valentin-B117 self-assigned this Sep 25, 2026
@Valentin-B117
Valentin-B117 marked this pull request as ready for review October 6, 2026 07:06
@apify-service-account apify-service-account added the t-growth Issues owned by the Growth team. label Oct 6, 2026

@katzino katzino left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a single question - since this is still behind feature flag, shouldn't the docs section have beta label or something?

@Valentin-B117

Valentin-B117 commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor Author

Just a single question - since this is still behind feature flag, shouldn't the docs section have beta label or something?

As it will soon be made public, the marker is no longer necessary.

@jgagne jgagne left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a few suggestions, mostly to fix details that don’t match the product. Give them a sanity check before you accept them. The screenshot of the Publishing tab also needs retaking, since it still shows the old tab name.

Comment thread sources/platform/actors/publishing/publish-task.mdx Outdated
Comment thread sources/platform/actors/publishing/publish-task.mdx Outdated
Comment thread sources/platform/actors/publishing/publish-task.mdx Outdated
Comment thread sources/platform/actors/publishing/publish-task.mdx Outdated
Comment thread sources/platform/actors/publishing/publish-task.mdx Outdated
@Valentin-B117
Valentin-B117 requested a review from jgagne October 21, 2026 08:47

@jgagne jgagne left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for the updates.

@Valentin-B117
Valentin-B117 merged commit a40a44b into master Oct 29, 2026
14 checks passed
@Valentin-B117
Valentin-B117 deleted the feat/add-faq-section branch October 29, 2026 13:31
@TC-MO

TC-MO commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

@Valentin-B117 @katzino @jgagne why was no Technical Writer pulled for review for addition to documentation? Your group assigned TW is @marcel-rbro if you did not know, and since we are responsible for docs we would appreciate if you pulled us for any changes to docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-growth Issues owned by the Growth team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants