handbook: Expert Application Building soft-launch access process#4987
Open
dimitrieh wants to merge 9 commits into
Open
handbook: Expert Application Building soft-launch access process#4987dimitrieh wants to merge 9 commits into
dimitrieh wants to merge 9 commits into
Conversation
Documents triage for inbound access requests to the FF 2.30 agentic Node-RED development soft launch. Forks the info ask by Identify outcome so the paid tier note always lands in the first reply, and gates eligibility on use case + reason being on file.
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Unquoted nodes with HTML formatting caused the mermaid block to fail silently on Eleventy/v10. Switching to quoted labels matches the pattern used in sales/engagements.md and engineering/ops/deployment.md.
…alone
The hexagon node syntax {{...}} was being evaluated by Nunjucks as a
template expression before Mermaid ever saw it, producing an empty
diagram. Also change Identify to a plain rect so the diagram is
robust if the raw block is ever removed.
Triage duty (rotation, not a fixed team) owns the customer-facing flow end-to-end. Engineering owns technical activation via a PCR in CloudProject. Product is the escalation path for borderline eligibility. Adds four reply templates (not found, free tier, paid tier, decline) so triage has a starting point per case rather than drafting from scratch.
Renames the handbook page, navTitle, headings, body references, and the prefilled PCR title to FlowFuse Expert Agentic Application Building. The contact form URL parameter (subject=FlowFuse%20Expert%20Application%20Building) is intentionally left alone so the page keeps matching the live release blog and changelog on main. If the marketing copy is updated to use the Agentic name, update the URL parameter here in the same change.
- Adds classDef colors so each step type is visually distinct - New step: triage informs Product as soon as use case is on file - Eligibility step explicitly requires including Product whenever triage has any doubt - PCR URL now prefills change-description and validation-steps via GitHub Issue Forms query parameters; copy-paste fallback included for the case where GitHub doesn't pick up auto-generated field IDs
…in HubSpot - Reduce flow palette to 6 categories: default gray, Product (purple), decision (yellow), decline (red), Engineering handoff (orange), success (green). The three reply asks share the default color. - Drop the 'If the PCR URL pre-fill doesn't populate' section. - Trim the PCR step instruction to only the Production-checkbox note. - Inform Product step uses HubSpot notes (with Product mentioned) rather than a Slack post. Borderline eligibility also loops Product via the same HubSpot thread.
Single use-case ask per template: what they want to build, what they plan to do with it, plus any context they'd like to share. Drops the separate 'reason for the soft launch' bullet, which was redundant with use case. Subject lines and intros trimmed. Decline template strips the unprompted soft-launch positioning sentence.
…plan cases Splits the prior 'Not found' branch into two: 'Not a customer yet' (company has no FlowFuse Cloud presence) and 'Different email, related team exists' (colleague has a team under a different address). Adds an explicit 'plan no longer active' path alongside Free tier. Five reply templates total, one per Identify outcome plus the decline.
Contributor
|
@dimitrieh this is great. Two notes:
|
Contributor
I'm going to vote that this really shouldn't be Engineering's job at all. Only the very last step of enabling a suitable user/organisation should be an engineering responsibility, everything else more likely lives with Sales as potential leads, because nearly (if not all) requests so far have come in from none customers. |
Contributor
|
I agree with Ben on who's responsible. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a handbook page documenting how to triage inbound contact submissions for the FlowFuse Expert Application Building soft launch (FF 2.30, agentic Node-RED development).
Forks the info ask by Identify outcome (not found, found-free-tier, found-paid-tier) so the paid tier note always lands in the first reply, and gates eligibility on use case + reason being on file.
Links the new page from `engineering/ops/index.md`.