Skip to content

Commit 21edcaf

Browse files
authored
Merge pull request #3366 from FlowFuse/reorganize-customer-dept
Create sales and marketing departments
2 parents 97cd89a + 3591c77 commit 21edcaf

42 files changed

Lines changed: 59 additions & 80 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

src/handbook/company/strategy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Software plays a key part in education, reducing vendor lock-in, and community b
5656

5757
## The market
5858

59-
We focus on [Ideal Customer Profile (ICP)](https://flowfuse.com/handbook/customer/marketing/messaging/) companies, which are those in manufacturing, logistics, and other data-intensive industrial sectors where operational efficiency is critical to providing value.
59+
We focus on [Ideal Customer Profile (ICP)](https://flowfuse.com/handbook/marketing/messaging/) companies, which are those in manufacturing, logistics, and other data-intensive industrial sectors where operational efficiency is critical to providing value.
6060

6161
Within those companies, we focus our outreach and marketing activities on people who are responsible for improving engineering processes. These individuals are often Architects, Engineering Managers, and specialists in IT or OT.
6262

@@ -81,6 +81,6 @@ The FlowFuse Platform addresses the problems status above by providing our ICP w
8181
1. Visualize and Interact: FlowFuse offers intuitive visualizations, real-time feedback loops, and interactive dashboards that enable engineers to monitor performance, identify trends, and make data-driven decisions.
8282
1. Build Custom Solutions: The low-code platform empowers engineers to create custom applications, dashboards, and automation workflows without extensive coding knowledge.
8383
1. Simplify Complexity: We abstract away the complexities of industrial systems, providing a comprehensive user-friendly interface that allows engineers to focus on solving problems, not wrestling with technology.
84-
See also our [Messaging page](/handbook/customer/marketing/messaging/).
84+
See also our [Messaging page](/handbook/marketing/messaging/).
8585

8686
FlowFuse uses Open-Source technologies like Node-RED and MQTT to help our customers being successful in remedying their problems.

src/handbook/customer/index.md

Lines changed: 0 additions & 45 deletions
This file was deleted.

src/handbook/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,8 @@ To run our company we provide a comprehensive guide outlining policies, procedur
4545

4646
| | |
4747
|:----|:----|
48-
| [Marketing](/handbook/customer/marketing/)<br /><p>How we reach companies that can benefit from FlowFuse.</p>
49-
| [Customer Success](/handbook/customer/customer-success/)<br /><p>Happy customers is what makes FlowFuse a sustainable business.</p>
48+
| [Marketing](/handbook/marketing/)<br /><p>How we reach companies that can benefit from FlowFuse.</p>
49+
| [Customer Success](/handbook/sales/customer-success/)<br /><p>Happy customers is what makes FlowFuse a sustainable business.</p>
5050
| |
5151

5252
### About the Handbook
Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ meta:
77

88
## Blogging Process
99

10-
Content creation and blogging are effective ways to communicate with our community and are tied to our SEO performance and our [Social Media Strategy](/handbook/customer/marketing/social-media/#strategy-for-increasing-reach). The process for publishing a blog is as follows:
10+
Content creation and blogging are effective ways to communicate with our community and are tied to our SEO performance and our [Social Media Strategy](/handbook/marketing/social-media/#strategy-for-increasing-reach). The process for publishing a blog is as follows:
1111

1212
1. Create an initial issue or tie your blog to one of your scheduled issues [here](https://github.com/orgs/FlowFuse/projects/21/views/1).
13-
2. Issues should be assigned a date, which should be posted here in this [Github projects](https://github.com/orgs/FlowFuse/projects/21/views/1). The target date for review should be at least three working days before the planned posting date on social media. Check the [social media planning and posting section](/handbook/customer/marketing/social-media/#planning-and-posting).
13+
2. Issues should be assigned a date, which should be posted here in this [Github projects](https://github.com/orgs/FlowFuse/projects/21/views/1). The target date for review should be at least three working days before the planned posting date on social media. Check the [social media planning and posting section](/handbook/marketing/social-media/#planning-and-posting).
1414
3. Create a PR requests with your Blog Content.
1515
4. Assign yourself as an Assignee.
1616
5. Convert to Draft
@@ -21,7 +21,7 @@ Content creation and blogging are effective ways to communicate with our communi
2121
8. Content will be reviewed first.
2222
9. SEO will be reviewed second.
2323
10. When both reviews are done, the Author or SEO reviewer can merge. In the event of an external author, SEO/content review will merge.
24-
11. Once merged, SEO Reviewer will promote on FlowFuse Social channels. Check the [social media planning and posting section](/handbook/customer/marketing/social-media/#planning-and-posting) for guidance and considerations.
24+
11. Once merged, SEO Reviewer will promote on FlowFuse Social channels. Check the [social media planning and posting section](/handbook/marketing/social-media/#planning-and-posting) for guidance and considerations.
2525

2626

2727
## Blog CMS
@@ -96,7 +96,7 @@ You can also add your own custom tags. While these won't create a new page with
9696

9797
#### Meta Keywords
9898

99-
Additionally, the tags you assign to your content will also be used as [meta keywords](/handbook/customer/marketing/website/#meta-keywords) for each article, alongside the [default keywords](/handbook/customer/marketing/website#default-keywords).
99+
Additionally, the tags you assign to your content will also be used as [meta keywords](/handbook/marketing/website/#meta-keywords) for each article, alongside the [default keywords](/handbook/marketing/website#default-keywords).
100100

101101
### Adding Images
102102

src/handbook/customer/marketing/brand-voice.md renamed to src/handbook/marketing/brand-voice.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ Tone should be:
116116
**Example:**
117117
> Hey, good question! I’ve seen a similar issue when deploying on Docker — it might be worth checking your volume permissions. Let me know if that helps or if you want to try another approach.
118118
119-
For broader principles on interacting with the community as a FlowFuse team member, see our [Community Guidelines](/handbook/customer/marketing/community/community-guidelines.md).
119+
For broader principles on interacting with the community as a FlowFuse team member, see our [Community Guidelines](/handbook/marketing/community/community-guidelines.md).
120120

121121
### Commenting on third-party content (e.g. posts by others)
122122

src/handbook/customer/marketing/community/community-guidelines.md renamed to src/handbook/marketing/community/community-guidelines.md

File renamed without changes.

src/handbook/customer/marketing/community/event-and-webinars.md renamed to src/handbook/marketing/community/event-and-webinars.md

File renamed without changes.

src/handbook/customer/marketing/community/forums-and-support.md renamed to src/handbook/marketing/community/forums-and-support.md

File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)