Skip to content

docs(stack): pick Payload over Webflow when needed - #182

Merged
hcarreras merged 1 commit into
mainfrom
payload-vs-webflow-guidelines
Sep 9, 2026
Merged

hcarreras merged 1 commit into
mainfrom
payload-vs-webflow-guidelines

Conversation

@hcarreras

Copy link
Copy Markdown
Contributor

The CMS table picks a CMS purely on how much content flexibility the client needs. That misses the cases where Webflow simply can't do the job — third-party integrations, custom logic, or content behind a login — and those should land on Payload no matter how static the content is.

This adds one line after the table saying so. Payload stays the recommendation for medium customization needs; nothing else in the table changes.

How to test

  • Open the Stack and services page from this branch's preview (or read tools_and_services/stack_and_services.md).
  • Scroll to Frameworks → Websites → CMS.
  • Confirm the customization-needs table is unchanged, with Payload still listed for medium needs.
  • Confirm a new sentence appears below the Strapi/Payload bullets, saying to pick Payload over Webflow — even at low customization needs — when the site needs third-party integrations, custom logic, or content behind a login.

Webflow cannot cover third-party integrations, custom logic, or
gated content, so those projects need Payload even when the
content needs are small.
Copilot AI lite review requested due to automatic review settings September 8, 2026 12:10

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

The change is a clear, consistent documentation clarification that matches the stated intent and does not introduce any conflicting guidance in the CMS section.

Pull request overview

This PR clarifies CMS selection guidance on the “Stack and services” documentation by adding an explicit exception: even for low content-flexibility needs, choose Payload when the project requires capabilities that Webflow can’t support.

Changes:

  • Adds a single sentence under Frameworks → Websites → CMS advising Payload over Webflow when third-party integrations, custom logic, or login-gated content are required.
File summaries
File Description
tools_and_services/stack_and_services.md Adds an exception note to the CMS recommendation guidance to choose Payload when Webflow is insufficient, independent of content flexibility needs.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@hcarreras
hcarreras merged commit 3878e54 into main Sep 9, 2026
6 checks passed
@hcarreras
hcarreras deleted the payload-vs-webflow-guidelines branch September 9, 2026 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants