Skip to content

docs: add sunset note to Flowise integration page - #2852

Open
marcel-rbro wants to merge 4 commits into
masterfrom
docs/flowise-sunset
Open

docs: add sunset note to Flowise integration page#2852
marcel-rbro wants to merge 4 commits into
masterfrom
docs/flowise-sunset

Conversation

@marcel-rbro

Copy link
Copy Markdown
Contributor

The Flowise team has discontinued the project. The code stays open source and existing deployments keep working, so the walkthrough stays for now - this just flags the status and links to their announcement, which carries the timeline. The page can be removed once usage dies out.

🤖 Generated with Claude Code

The Flowise team has discontinued the project. The code stays open source
and existing deployments keep working, so the walkthrough stays for now -
this just flags the status and links to their sunset announcement. The page
can be removed once usage dies out.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the t-docs Issues owned by technical writing team. label Aug 5, 2026
@apify-service-account

apify-service-account commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

✅ Preview for this PR (commit 37446e3f) is ready at https://pr-2852.preview.docs.apify.com (see action run).

marcel-rbro and others added 2 commits August 5, 2026 15:35
"Flowise is sunset" reads as a description of a sunset rather than a
product status. Uses the house noun-phrase pattern instead, matching
"Rental model sunset" and "SSE transport deprecated".

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
"Flowise is sunset" read as a description of a sunset rather than a
product status.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@marcel-rbro
marcel-rbro requested a review from TC-MO August 5, 2026 14:05

@TC-MO TC-MO 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.

Shouldn't this be absolutely upfront even before explanation of what Flowise is? I'd rather know that project is semi-dead before I start to invest time. Furthermore with this setup we have admonition next to admonition which visually is not great

Put the discontinuation warning first, before the description of what
Flowise is, so readers see it before investing time. Also stops the note
sitting directly next to the third-party disclaimer admonition.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@marcel-rbro

Copy link
Copy Markdown
Contributor Author

I assumed (👀) that anyone coming to this page would already know that since they'd probably be coming from a Flowise resource. Anyways, I've fixed it, now it's unmissable.

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

Labels

t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants