Skip to content

Homepage: say what an app platform means - #5500

Draft
dimitrieh wants to merge 1 commit into
feat/platform-pagefrom
feat/homepage-app-platform
Draft

Homepage: say what an app platform means#5500
dimitrieh wants to merge 1 commit into
feat/platform-pagefrom
feat/homepage-app-platform

Conversation

@dimitrieh

Copy link
Copy Markdown
Contributor

Description

Stacked on #5499. Base is feat/platform-page because this section links to /platform/, which #5499 adds; the link checker would fail against main. Retarget to main once #5499 merges.

The homepage asserts that FlowFuse is a platform and then moves straight to capabilities, so a visitor never learns what the platform is made of or why the word applies. The next step offered is the Expert, which is the wrong place to send someone who does not yet understand the components.

Adds one section after the solution statement that:

  • States the claim, that "app platform" is about how FlowFuse distributes and manages code.
  • Backs it with the two distribution models, shipping a whole application by pipeline versus shipping building blocks via a library.
  • Lists the major components grouped by what they do, as a compact scannable list rather than another card grid.
  • Hands off to /platform/ for the detail instead of dead-ending at the Expert.

No existing homepage content is removed or reordered.

Related Issue(s)

None.

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

The homepage asserts that FlowFuse is a platform and then moves straight to
capabilities, so a visitor never learns what the platform is made of or why
the word applies. The next step offered was the Expert, which is the wrong
place to send someone who does not yet understand the components.

Adds a section after the solution statement that states the claim, backs it
with the two ways FlowFuse distributes and manages code, lists the major
components grouped by what they do, and hands off to /platform/ for detail.
@dimitrieh

Copy link
Copy Markdown
Contributor Author

@dimitrieh
dimitrieh marked this pull request as draft August 4, 2026 20:19
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.

1 participant