diff --git a/.github/ISSUE_TEMPLATE/release-article.md b/.github/ISSUE_TEMPLATE/release-article.md index 67f8ecdf65e6..c8cbb4ea23a1 100644 --- a/.github/ISSUE_TEMPLATE/release-article.md +++ b/.github/ISSUE_TEMPLATE/release-article.md @@ -2,7 +2,7 @@ name: 📰 Release article about: Propose a new feature or enhancement in Fleet. title: 'Release article: vXXX.YYY.ZZZ' -labels: '#g-demand,:improve documentation' +labels: ':help-marketing,:improve documentation' assignees: 'rachaelshaw' --- diff --git a/CODEOWNERS b/CODEOWNERS index c8512f309c58..f58482a050c9 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -93,7 +93,7 @@ go.mod @fleetdm/go /handbook/digital-experience/security.md @sampfluger88 /handbook/digital-experience @sampfluger88 /handbook/customer-success @sampfluger88 -/handbook/demand @sampfluger88 +/handbook/marketing @sampfluger88 #/handbook/engineering 🤡 Covered in custom.js /handbook/sales @sampfluger88 #/handbook/product-design 🤡 Covered in custom.js diff --git a/handbook/company/README.md b/handbook/company/README.md index 706d433bf880..9222c5a25a51 100644 --- a/handbook/company/README.md +++ b/handbook/company/README.md @@ -143,7 +143,7 @@ To provide clarity about decision-making, [responsibility](https://fleetdm.com/h - 🚀 [Engineering](https://fleetdm.com/handbook/engineering): The Engineering department at Fleet is directly responsible for writing and maintaining the code for Fleet's core product, as well as Fleet's Information technology (IT) infrastructure. - 🦢 [Product Design](https://fleetdm.com/handbook/product-design): The Product Design department is directly responsible for defining and prioritizing the changes made to the core product, Fleet API, and reference documentation. - 🌦️ [Customer Success](https://fleetdm.com/handbook/customer-success): The customer success department is directly responsible for ensuring that customers and community members of Fleet achieve their desired outcomes with Fleet products and services. -- 🫧 [Demand](https://fleetdm.com/handbook/demand): The Demand department is directly responsible for growing awareness of Fleet and nurturing the community through participation in events, conversations, and other programs. +- 🫧 [Marketing](https://fleetdm.com/handbook/marketing): The Marketing department is directly responsible for growing awareness of Fleet and nurturing the community through participation in events, conversations, and other programs. - 💸 [Finance](https://fleetdm.com/handbook/finance): The Finance department is directly responsible for accounts receivable including invoicing, accounts payable including commision calculations, expense reporting including Brex memos and maintaining accurate spend projections in "🧮The numbers", sales taxes, payroll taxes, corporate income/franchise taxes, and financial operations including bank accounts and cash flow management. - 🐋 [Sales](https://fleetdm.com/handbook/sales): The Sales department is directly responsible for attaining the revenue goals of Fleet and helping customers deliver on their objectives. - 🌐 [Digital Experience](https://fleetdm.com/handbook/digital-experience): The Digital Experience department is directly responsible for the culture, training, framework, content design, and technology behind Fleet's remote work culture, including fleetdm.com, the handbook, issue templates, UI style guides, internal tooling, Zapier flows, Docusign templates, key spreadsheets, contracts, compliance, receiving and responding to legal notices, SOC2, deal desk, project management processes, human resources, benefits, opening positions, compensation planning, onboarding, and offboarding. diff --git a/handbook/company/communications.md b/handbook/company/communications.md index 6bb305000820..c5b6f30921b7 100644 --- a/handbook/company/communications.md +++ b/handbook/company/communications.md @@ -58,10 +58,10 @@ We track competitors' capabilities and adjacent (or commonly integrated) product | Product marketing (PMM) | _See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ | Brand marketing | _See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ | Public relations | _See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ -| Revenue pipeline | _See [🫧 Demand team](https://fleetdm.com/handbook/demand#team)_ -| Ads | _See [🫧 Demand team](https://fleetdm.com/handbook/demand#team)_ -| Video | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_ -| Social media | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_ +| Revenue pipeline | _See [🫧 Marketing team](https://fleetdm.com/handbook/marketing#team)_ +| Ads | _See [🫧 Marketing team](https://fleetdm.com/handbook/marketing#team)_ +| Video | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/marketing#team)_ +| Social media | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/marketing#team)_ | Guides | _See [🌦️ Customer Success & VP of Customer Success](https://fleetdm.com/handbook/customer-success#team)_ | Release article | _See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_ | Information technology (IT) | _See [🚀 Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_ @@ -141,7 +141,7 @@ Fleet's community programs are rooted in several areas; created to nurture commu Fleet's largest asset is our user community, the people actually using Fleet. Public conversations on social media create valuable opportunities for contributors to answer technical questions and collect feedback. -Fleet [does not self-promote](https://www.audible.com/pd/The-Impact-Equation-Audiobook/B00AR1VFBU). (Great brands are [magnanimous](https://en.wikipedia.org/wiki/Magnanimity).) In fact, conversations are already happening in our social spaces that open up opportunities for Fleet to [engage with the community](https://fleetdm.com/handbook/demand#engage-with-the-community). +Fleet [does not self-promote](https://www.audible.com/pd/The-Impact-Equation-Audiobook/B00AR1VFBU). (Great brands are [magnanimous](https://en.wikipedia.org/wiki/Magnanimity).) In fact, conversations are already happening in our social spaces that open up opportunities for Fleet to [engage with the community](https://fleetdm.com/handbook/marketing#engage-with-the-community). Here are some topics for social media posts: - Fleet the product @@ -155,7 +155,7 @@ Here are some topics for social media posts: #### Fleet on LinkedIn -Original posts on LinkedIn by Fleet employees [can be promoted using the Fleet company page](https://fleetdm.com/handbook/demand#promote-a-post-on-linkedin). If you think your post would make sense in front of a bigger audience, [create an issue on the demand board](https://fleetdm.com/handbook/demand#contact-us) linking the team to your personal LinkedIn post (only original posts please, reposts and quotes of other posts can not be promoted). Include any context in the issue and keep an eye on your inbox, The Demand team will request permission to use the post in a promoted post. +Original posts on LinkedIn by Fleet employees [can be promoted using the Fleet company page](https://fleetdm.com/handbook/marketing#promote-a-post-on-linkedin). If you think your post would make sense in front of a bigger audience, [create an issue on the demand board](https://fleetdm.com/handbook/marketing#contact-us) linking the team to your personal LinkedIn post (only original posts please, reposts and quotes of other posts can not be promoted). Include any context in the issue and keep an eye on your inbox, The Demand team will request permission to use the post in a promoted post. ### Ads @@ -170,7 +170,7 @@ It's important for Fleet to engage at [events](https://docs.google.com/spreadshe #### Event lead follow-up -Eventgoers expect a timely [follow-up from Fleet](https://fleetdm.com/handbook/demand#upload-contacts-to-salesforce-after-an-event) based on the conversations that they had at the event. +Eventgoers expect a timely [follow-up from Fleet](https://fleetdm.com/handbook/marketing#upload-contacts-to-salesforce-after-an-event) based on the conversations that they had at the event. 1. Once a list of badge scans is available, fleeties who attended the event are to add any follow-up notes, including primary buying situation, amount of endpoints, level of interest, and general talking points. 2. Within three business days of returning from the event, attendees will set up a debrief meeting with the demand team to discuss follow-up and provide the list of badge scans uploaded to the ["Events" folder in Google Drive](https://drive.google.com/drive/u/0/folders/1uXf95V6CHKHnqxRc9iQr0a0FnTZk3bXR). diff --git a/handbook/company/handbook.md b/handbook/company/handbook.md index f7d416e9b21d..c7cc924e934b 100644 --- a/handbook/company/handbook.md +++ b/handbook/company/handbook.md @@ -16,7 +16,7 @@ All done! To contribute a new handbook page: 1. Determine where the new page should live in the handbook. That is, nested under either: a. [the "Company" handbook](https://fleetdm.com/handbook/company), or - b. the handbook for a particular division (Engineering, Product Design, Customer Support, Sales, Demand, Finance, Digital Experience) + b. the handbook for a particular division (Engineering, Product Design, Customer Support, Sales, Marketing, Finance, Digital Experience) 2. Locate the appropriate folder for the new page in [the GitHub repository under `handbook/`](https://github.com/fleetdm/fleet/tree/main/handbook). 3. Create a new markdown file (like [one of these](https://github.com/fleetdm/fleet/tree/f90148abad96fccb6c5647a31877fa7e91b5ee57/handbook/digital-experience)). A simple, easy way to do this is by clicking "Add file" on GitHub.com. a. Name your new file the kebab-cased, all lowercase version of your page title, with `.md` at the end. (For example, a page titled "Why this way?" would have the file path: `handbook/company/why-this-way.md`.) diff --git a/handbook/digital-experience/README.md b/handbook/digital-experience/README.md index 464837a84639..65802515f417 100644 --- a/handbook/digital-experience/README.md +++ b/handbook/digital-experience/README.md @@ -183,7 +183,7 @@ Fleet has several brand fronts that need to be updated from time to time. Check ### Update the host count of a premium subscription -When a self-service license dispenser customer reaches out to upgrade a license via the contact form, a member of the [Demand department](https://fleetdm.com/handbook/demand) will create a confidential issue detailing the request and add it to the new requests column of [Digital Experience kanban board](https://github.com/fleetdm/confidential/issues#workspaces/g-digital-experience-6451748b4eb15200131d4bab/board). A member of this team will then log into Stripe using the shared login, and upgrade the customer's subscription. +When a self-service license dispenser customer reaches out to upgrade a license via the contact form, a member of the [Marketing department](https://fleetdm.com/handbook/marketing) will create a confidential issue detailing the request and add it to the new requests column of [Digital Experience kanban board](https://github.com/fleetdm/confidential/issues#workspaces/g-digital-experience-6451748b4eb15200131d4bab/board). A member of this team will then log into Stripe using the shared login, and upgrade the customer's subscription. To update the host count on a user's subscription: diff --git a/handbook/engineering/engineering.rituals.yml b/handbook/engineering/engineering.rituals.yml index 088d0105fb4d..69fe1ed7fac6 100644 --- a/handbook/engineering/engineering.rituals.yml +++ b/handbook/engineering/engineering.rituals.yml @@ -93,7 +93,7 @@ startedOn: "2023-10-02" frequency: "Daily" description: "Check 📃 Planned articles and complete steps in each issue" - moreInfoUrl: "https://fleetdm.com/handbook/demand#review-ongoing-articles" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#review-ongoing-articles" dri: "rachaelshaw" diff --git a/handbook/demand/README.md b/handbook/marketing/README.md similarity index 89% rename from handbook/demand/README.md rename to handbook/marketing/README.md index 4ca5a5a6df16..fb5b4c633bf5 100644 --- a/handbook/demand/README.md +++ b/handbook/marketing/README.md @@ -1,4 +1,4 @@ -# Demand +# Marketing This handbook page details processes specific to working [with](#contact-us) and [within](#responsibilities) this department. @@ -12,16 +12,16 @@ This handbook page details processes specific to working [with](#contact-us) and ## Contact us -- To **make a request** of the Demand department, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%23g-demand&projects=&template=custom-request.md&title=Request%3A+_______________________) and a team member will get back to you within one business day (If urgent, at-mention a [team member](#team) in the [#g-demand](https://fleetdm.slack.com/archives/C01ALP02RB5) Slack channel). +- To **make a request** of the Marketing department, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-marketing&projects=&template=custom-request.md&title=Request%3A+_______________________) and a team member will get back to you within one business day (If urgent, at-mention a [team member](#team) in the [:help-marketing](https://fleetdm.slack.com/archives/C01ALP02RB5) Slack channel). - Please use **issue comments and GitHub mentions** to communicate follow-ups or answer questions related to your request. - - Any Fleet team member can [view the kanban board](https://app.zenhub.com/workspaces/g-demand-64e6c8e2d35c7f001a457b7f/board?sprints=none) for this department, including pending tasks and the status of new requests. + - Any Fleet team member can [view the kanban board](https://app.zenhub.com/workspaces/help-marketing-64e6c8e2d35c7f001a457b7f/board?sprints=none) for this department, including pending tasks and the status of new requests. > To **make a request** related to **product marketing**, **brand**, **press**, **brandfronts**, **pitchfronts**, **featurefronts**, **ideal customer profiles (ICPs)**, **personas**, or **targeting** [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%23g-digital-experience&projects=&template=custom-request.md&title=Product%20marketing%20request%3A+_______________________) (If urgent, at-mention the [CEO](https://fleetdm.com/handbook/digital-experience#team) in the [#help-leadership](https://fleetdm.slack.com/archives/C0600L1TTPY) Slack channel). ## Responsibilities -The Demand department is directly responsible for achieving revenue pipeline targets, increasing awareness and interest in the open-source project, and nurturing the Fleet community through participation in video, sponsored events, and other [programs](https://fleetdm.com/handbook/company/communications#programs). +The Marketing department is directly responsible for achieving revenue pipeline targets, increasing awareness and interest in the open-source project, and nurturing the Fleet community through participation in video, sponsored events, and other [programs](https://fleetdm.com/handbook/company/communications#programs). For responsibilities and rituals directly responsible by an Account Development Representative (ADR), follow [this outline](https://docs.google.com/document/d/1gdjvqE8KGUC1fSWMWgNz8kn_R2i_MBg9ZxNrpnI4zGY/edit?tab=t.0). @@ -51,7 +51,7 @@ Intent signals help measure an individual's current level of engagement with the (a) A contact and/or account needs to be created/updated. -(b) An account should be prioritized for [manual research](https://fleetdm.com/handbook/demand#research-an-account). +(b) An account should be prioritized for [manual research](https://fleetdm.com/handbook/marketing#research-an-account). (c) An account/contact would benefit from a sales conversation. @@ -67,7 +67,7 @@ Intent signals help measure an individual's current level of engagement with the ### Research an account -Follow these steps to research an account and move it toward sales-readiness **after** discovering [relevant intent signals](https://fleetdm.com/handbook/demand#measure-intent-signals). +Follow these steps to research an account and move it toward sales-readiness **after** discovering [relevant intent signals](https://fleetdm.com/handbook/marketing#measure-intent-signals). 1. Create the account in SalesForce if it doesn't already exist. 2. Update any incorrect, mistagged, or incomplete contacts already on the account and merge any duplicates that are found. Verify the following data is current for each existing contact: @@ -109,7 +109,7 @@ The Head of Marketing is the DRI for deploying Fleet's outward-facing content. T ### Settle event strategy - Fleet's [Head of Marketing](https://fleetdm.com/handbook/demand#team) is the DRI for executing Fleet events efficiently, on-brand, and on-strategy within Fleet's event budget. Events are settled significantly in advance to provide ample time for strategy and planning. + Fleet's [Head of Marketing](https://fleetdm.com/handbook/marketing#team) is the DRI for executing Fleet events efficiently, on-brand, and on-strategy within Fleet's event budget. Events are settled significantly in advance to provide ample time for strategy and planning. 1. Using the [event strategy workbook](https://docs.google.com/spreadsheets/d/1YQXAX2Q_WnGkAwMYjMbQpV3nbCj7gOBbv7Y0u4twxzQ/edit#gid=1411322737), propose the events that Fleet will attend in the next 6 months, and the strategy for those events, including: - target buying situation of the audience @@ -137,20 +137,20 @@ The Head of Marketing is the DRI for deploying Fleet's outward-facing content. T ### Book an event -Fleet's Head of Marketing is responsible for booking events that Fleet has chosen to attend and/or sponsor. To book an event, complete the steps in each event issue. Contact the [🫧 Head of Marketing](https://fleetdm.com/handbook/demand#team) as needed with any questions or blockers to booking an event. +Fleet's Head of Marketing is responsible for booking events that Fleet has chosen to attend and/or sponsor. To book an event, complete the steps in each event issue. Contact the [🫧 Head of Marketing](https://fleetdm.com/handbook/marketing#team) as needed with any questions or blockers to booking an event. -> Note: The Demand department [settles all event strategy](https://fleetdm.com/handbook/demand#settle-event-strategy) prior to booking an event. +> Note: The Marketing department [settles all event strategy](https://fleetdm.com/handbook/marketing#settle-event-strategy) prior to booking an event. @@ -244,7 +244,7 @@ To do this: ### Request swag There are many times in which community members, customers, and contributors are in need of some cool Fleet swag. To request swag: -1. [Create an issue](https://app.zenhub.com/workspaces/g-demand-64e6c8e2d35c7f001a457b7f/issues/gh/fleetdm/confidential/new?issueType=issue) on the #g-demand board. +1. [Create an issue](https://app.zenhub.com/workspaces/help-marketing-64e6c8e2d35c7f001a457b7f/issues/gh/fleetdm/confidential/new?issueType=issue) on the :help-marketing board. 2. Provide order details (e.g. expected shirt size, name, and shipping details). 3. Decide if you'd like to include a personalized message and attach it to the issue. @@ -268,9 +268,9 @@ Swag requests are received in the form of issues and will be fulfilled based on ### Run a new ad or change an existing ad Any changes to the current running ads visible to a user, including designs, keywords, or targeting, are approved in 🦢🗣 Design review (#g-digital-experience), which [occurs regularly](https://fleetdm.com/handbook/company/product-groups#design-reviews) and is open to all fleeties. -1. [Digital Marketing Manager](https://fleetdm.com/handbook/demand#team) adds a discussion item about the change to the [website design review agenda](https://docs.google.com/document/d/1Q73ublh9bcIL01JsY--gpZRd3KPT_KCX-F0RaorKJcM/edit) +1. [Digital Marketing Manager](https://fleetdm.com/handbook/marketing#team) adds a discussion item about the change to the [website design review agenda](https://docs.google.com/document/d/1Q73ublh9bcIL01JsY--gpZRd3KPT_KCX-F0RaorKJcM/edit) 2. During the call, they compare existing ads against the planned updates within the corresponding ad platform. ([Google Ads](https://ads.google.com/home/), [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager/), etc.) -3. [Digital Marketing Manager](https://fleetdm.com/handbook/demand#team) makes changes and creates a calendar reminder to check performance either two weeks or four weeks from the date changes were made. +3. [Digital Marketing Manager](https://fleetdm.com/handbook/marketing#team) makes changes and creates a calendar reminder to check performance either two weeks or four weeks from the date changes were made. > **Do changes to keywords or targeting require a design review?** Currently, all changes to these things require discussion with our product marketer. @@ -315,7 +315,7 @@ Fleet invites guests to discuss the future of IT and security on the [ExpedITion ## Rituals - + #### Stubs @@ -341,4 +341,4 @@ Please see [handbook/company/communications#video](https://fleetdm.com/handbook/ - + diff --git a/handbook/demand/demand.rituals.yml b/handbook/marketing/demand.rituals.yml similarity index 78% rename from handbook/demand/demand.rituals.yml rename to handbook/marketing/demand.rituals.yml index 4cce691b16e7..360b3397770f 100644 --- a/handbook/demand/demand.rituals.yml +++ b/handbook/marketing/demand.rituals.yml @@ -2,8 +2,8 @@ task: "Refresh event calendar" startedOn: "2023-12-31" frequency: "Quarterly" - description: "https://fleetdm.com/handbook/demand#refresh-event-calendar" - moreInfoUrl: "https://fleetdm.com/handbook/demand#refresh-event-calendar" + description: "https://fleetdm.com/handbook/marketing#refresh-event-calendar" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#refresh-event-calendar" dri: "Drew-P-drawers" - task: "Prioritize for next sprint" # Title that will actually show in rituals table @@ -19,8 +19,8 @@ task: "Settle event strategy" startedOn: "2024-01-02" frequency: "Quarterly (first Tuesday)" - description: "https://fleetdm.com/handbook/demand#settle-event-strategy" - moreInfoUrl: "https://fleetdm.com/handbook/demand#settle-event-strategy" + description: "https://fleetdm.com/handbook/marketing#settle-event-strategy" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#settle-event-strategy" dri: "Drew-P-drawers" - task: "🫧 Pipeline sync" @@ -34,42 +34,42 @@ startedOn: "2024-02-26" frequency: "Weekly" description: "Remove all but the top 5 perfoming ads in each evergreen campaign. Make sure ABM campaigns are using top performing evergreen ads." - moreInfoUrl: "https://fleetdm.com/handbook/demand#optimize-ads-through-experimentation" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#optimize-ads-through-experimentation" dri: "Drew-P-drawers" - task: "Process pending swag requests from the website" # Title that will actually show in rituals table startedOn: "2023-09-20" # Needs to align with frequency e.g. if frequency is every thrid Thursday startedOn === any third thursday frequency: "Weekly" # must be supported by description: "Complete draft orders." # example of a longer thing: description: "[Prioritizing next sprint](https://fleetdm.com/handbook/company/communication)" - moreInfoUrl: "https://fleetdm.com/handbook/demand#process-pending-swag-requests-from-the-website" #URL used to highlight "description:" test in table + moreInfoUrl: "https://fleetdm.com/handbook/marketing#process-pending-swag-requests-from-the-website" #URL used to highlight "description:" test in table dri: "Drew-P-drawers" # DRI for ritual (assignee if autoIssue) (TODO display GitHub proflie pic instead of name or title) - task: "Engage with the community" startedOn: "2023-09-20" frequency: "Daily" description: "Find relevant conversations with the community and contribute" - moreInfoUrl: "https://fleetdm.com/handbook/demand#engage-with-the-community" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#engage-with-the-community" dri: "Drew-P-drawers" - task: "Publish ☁️🌈 Sprint demos" startedOn: "2023-11-03" frequency: "Triweekly" description: "Every release cycle, upload the ☁️🌈 Sprint demos video to YouTube" - moreInfoUrl: "https://fleetdm.com/handbook/demand#upload-to-youtube" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#upload-to-youtube" dri: "Drew-P-drawers" - task: "Measure intent signals" startedOn: "2024-08-09" frequency: "Daily" description: "Measure intent signals and update Salesforce" - moreInfoUrl: "https://fleetdm.com/handbook/demand#measure-intent-signals" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#measure-intent-signals" dri: "Drew-P-drawers" - task: "Research accounts" startedOn: "2024-08-09" frequency: "Daily" description: "Research any research-ready accounts in this Salesforce report (https://fleetdm.lightning.force.com/lightning/r/Report/00OUG000001PUIT2A4/view) and advance them to 'Ads running'" - moreInfoUrl: "https://fleetdm.com/handbook/demand#research-an-account" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#research-an-account" dri: "Drew-P-drawers" - task: "Check ongoing events" @@ -83,6 +83,6 @@ startedOn: "2023-10-21" frequency: "Weekly" description: "Populate ideas for future events" - moreInfoUrl: "https://fleetdm.com/handbook/demand#settle-event-strategy" + moreInfoUrl: "https://fleetdm.com/handbook/marketing#settle-event-strategy" dri: "Drew-P-drawers" diff --git a/website/config/custom.js b/website/config/custom.js index fcac76cba5cb..b9d76f3f2235 100644 --- a/website/config/custom.js +++ b/website/config/custom.js @@ -274,7 +274,7 @@ module.exports.custom = { 'handbook/engineering': ['sampfluger88','mikermcneil', 'lukeheath'], 'handbook/product-design': ['sampfluger88','mikermcneil','noahtalerman'], 'handbook/sales': ['sampfluger88','mikermcneil'], - 'handbook/demand': ['sampfluger88','mikermcneil'], + 'handbook/marketing': ['sampfluger88','mikermcneil'], 'handbook/customer-success': ['sampfluger88','mikermcneil'], 'handbook/company/testimonials.yml': ['eashaw', 'mike-j-thomas', 'sampfluger88', 'mikermcneil'], diff --git a/website/config/routes.js b/website/config/routes.js index cc845422ab3f..b5499bc036df 100644 --- a/website/config/routes.js +++ b/website/config/routes.js @@ -559,7 +559,7 @@ module.exports.routes = { 'GET /handbook/company/senior-software-backend-engineer': 'https://www.linkedin.com/posts/mikermcneil_in-addition-to-our-product-quality-specialist-activity-7067711903166279680-6CMH', 'GET /handbook/business-operations/ceo-handbook': '/handbook/ceo', 'GET /handbook/business-operations/people-operations': '/handbook/company/communications#hiring', - 'GET /handbook/marketing': '/handbook/demand/', + 'GET /handbook/demand': '/handbook/marketing/', 'GET /handbook/customers': '/handbook/sales/', 'GET /handbook/product': '/handbook/product-design', 'GET /handbook/business-operations': '/handbook/finance',