From cf80f5399120a2c12ed7648c77be2a191d94280f Mon Sep 17 00:00:00 2001 From: Jamie Strusz <5758031+allthedoll@users.noreply.github.com> Date: Fri, 15 May 2026 09:21:14 +0300 Subject: [PATCH 1/4] Update dependency update guidelines Added a note to check all repositories for dependabot activity. --- src/handbook/engineering/dependency-updates.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/handbook/engineering/dependency-updates.md b/src/handbook/engineering/dependency-updates.md index ef4f9677bb..c2e3a4a6f9 100644 --- a/src/handbook/engineering/dependency-updates.md +++ b/src/handbook/engineering/dependency-updates.md @@ -23,6 +23,7 @@ Work through Dependabot PRs in this order: 3. **Read the release notes for each bump.** Confirm there are no breaking changes that affect how we use the package. Patch and minor bumps still occasionally ship behavior changes worth knowing about. 4. **Merge the safe, small bumps first.** Patch and minor updates with a contained diff and clean release notes go in early. Leave anything with an unusually large diff for closer review. 5. **CI must pass before merging — no exceptions.** A red build on a dependency PR is the signal that something needs investigation, not a bypass. +6. **Check all repositories** - dependabot is active in all our repositiories. ## Major version bumps From 890504f306e2f43dcdf500ece750d925099210e1 Mon Sep 17 00:00:00 2001 From: Jamie Strusz <5758031+allthedoll@users.noreply.github.com> Date: Fri, 15 May 2026 09:23:16 +0300 Subject: [PATCH 2/4] Fix formatting and grammar in dependency updates guide --- src/handbook/engineering/dependency-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/handbook/engineering/dependency-updates.md b/src/handbook/engineering/dependency-updates.md index c2e3a4a6f9..4b4b475568 100644 --- a/src/handbook/engineering/dependency-updates.md +++ b/src/handbook/engineering/dependency-updates.md @@ -23,7 +23,7 @@ Work through Dependabot PRs in this order: 3. **Read the release notes for each bump.** Confirm there are no breaking changes that affect how we use the package. Patch and minor bumps still occasionally ship behavior changes worth knowing about. 4. **Merge the safe, small bumps first.** Patch and minor updates with a contained diff and clean release notes go in early. Leave anything with an unusually large diff for closer review. 5. **CI must pass before merging — no exceptions.** A red build on a dependency PR is the signal that something needs investigation, not a bypass. -6. **Check all repositories** - dependabot is active in all our repositiories. +6. **Check all repositories.** - Dependabot is active in all our repositiories. ## Major version bumps From 5d4a1018a770bb27f1475235ce4ee94ed441ba0e Mon Sep 17 00:00:00 2001 From: Jamie Strusz <5758031+allthedoll@users.noreply.github.com> Date: Fri, 15 May 2026 09:43:20 +0300 Subject: [PATCH 3/4] Update layouts documentation to include Immersive layout Added Immersive layout description to the documentation. --- src/handbook/engineering/frontend/layouts.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/handbook/engineering/frontend/layouts.md b/src/handbook/engineering/frontend/layouts.md index 5424e22fe1..0afbf3305c 100644 --- a/src/handbook/engineering/frontend/layouts.md +++ b/src/handbook/engineering/frontend/layouts.md @@ -4,11 +4,12 @@ title: Front-End Layouts # Layouts -The frontend has 4 layouts which can be found in `frontend/src/layouts`: +The frontend has 5 layouts which can be found in `frontend/src/layouts`: - Platform - Plain - Page - Box +- Immersive ## Layout Variants @@ -30,6 +31,11 @@ The plain layout serves as a blank structure primarily used for embedded pages o Has support for alerts and dialog/modals. +### Immersive +The immersive layout serves as the flexbox for the hosted and remoted editor instances. + +Does not have support for left drawers. All drawers are shown as a layout over the expert drawer. + ### Box The box layout is used in the initial Setup phase and consists of a boxed layout which guides you through the required steps in configuring the Flow Fuse Application. From 1e498dcff4efcb9b7a260beb9024136b199d4a6c Mon Sep 17 00:00:00 2001 From: Jamie Strusz <5758031+allthedoll@users.noreply.github.com> Date: Fri, 15 May 2026 09:47:40 +0300 Subject: [PATCH 4/4] Rename GitHub Copilot to Claude Code Updated references from GitHub Copilot to Claude Code. --- src/handbook/engineering/tools.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/handbook/engineering/tools.md b/src/handbook/engineering/tools.md index daaca30fbb..4f60a750a2 100644 --- a/src/handbook/engineering/tools.md +++ b/src/handbook/engineering/tools.md @@ -19,8 +19,6 @@ When using AI tools for development, never share: 2. Company secrets like API keys, private credentials, etc, etc. 3. Customer code or other assets under NDA -### GitHub Copilot +### Claude Code -GitHub Copilot Business is available to team members by raising an [access request issue](https://github.com/FlowFuse/admin/issues/new?template=access-request.md) and assigning it to the CTO. - -Alternatively, individuals can self-purchase Copilot Pro/+ and expense the cost, or qualify for free access due to their role as an Open Source maintainer. +Claude Code is available to team members by raising an [access request issue](https://github.com/FlowFuse/admin/issues/new?template=access-request.md) and assigning it to the CTO.