Skip to content

Conversation

@mintlify
Copy link
Contributor

@mintlify mintlify bot commented Feb 11, 2026

Summary

  • Changed brand name from Mintlify to Applify with apple red color scheme
  • Updated introduction and quickstart pages with apple orchard metaphors
  • Added apple emoji to main documentation heading
  • Modified descriptions to use apple-themed language throughout

Note

Low Risk
Mostly branding and documentation copy changes; the only functional tweak is a small config value rename (add-mcp -> mcp) that could affect the contextual menu option display.

Overview
Updates docs.json to rebrand the site from Mintlify to Applify, swapping the primary color palette to apple-red tones and renaming a contextual menu option from add-mcp to mcp.

Refreshes index.mdx and quickstart.mdx marketing/intro text to an apple-orchard theme (including an 🍎 in the main heading) and adjusts the AI skill command copy to reference Applify instead of Mintlify.

Written by Cursor Bugbot for commit 427cad7. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

"chatgpt",
"claude",
"add-mcp",
"mcp",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Contextual option renamed breaking MCP menu functionality

High Severity

The contextual menu option "add-mcp" was changed to "mcp", but the documented valid option name is add-mcp (as seen in ai/contextual-menu.mdx and ai/model-context-protocol.mdx). This is an unrelated functional change sneaked into a theming PR that will likely cause the "Copy MCP install command" contextual menu item to stop appearing, since "mcp" is not a recognized option value.

Fix in Cursor Fix in Web

Comment on lines +4 to 9
"name": "Applify",
"colors": {
"primary": "#166E3F",
"light": "#26BD6C",
"dark": "#166E3F"
"primary": "#DC143C",
"light": "#FF6B6B",
"dark": "#8B0000"
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This introduces a partial rebrand (name + palette) while the rest of the doc site still references Mintlify (schema, URLs, .mintlify.app, dashboard). If this isn't intended to be a full rebrand, I'd keep the existing values.

Suggested change
"name": "Applify",
"colors": {
"primary": "#166E3F",
"light": "#26BD6C",
"dark": "#166E3F"
"primary": "#DC143C",
"light": "#FF6B6B",
"dark": "#8B0000"
},
"name": "Mintlify",
"colors": {
"primary": "#166E3F",
"light": "#26BD6C",
"dark": "#166E3F"
},

"chatgpt",
"claude",
"add-mcp",
"mcp",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worth double-checking that "mcp" is a supported contextual.options value in the docs.json schema / UI. If the UI expects the old key, this will silently drop the menu item.

Suggested change
"mcp",
"add-mcp",

<div className="relative z-10 px-4 py-16 lg:py-48 lg:pb-24 max-w-3xl mx-auto">
<h1 className="block text-4xl font-medium text-center text-gray-900 dark:text-zinc-50 tracking-tight">
Documentation
Documentation 🍎
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd keep headings emoji-free; it tends to look noisy in nav/search snippets.

Suggested change
Documentation 🍎
Documentation

---
title: "Introduction"
description: "Meet the next generation of documentation. AI-native, beautiful out-of-the-box, and built for developers."
description: "Core documentation, fresh as a crisp apple. AI-native, juicy insights, cultivated for developers."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This frontmatter description reads pretty metaphor-heavy compared to the rest of the docs. If the goal is to keep the intro crisp and consistent, I'd revert to the more literal copy.

Suggested change
description: "Core documentation, fresh as a crisp apple. AI-native, juicy insights, cultivated for developers."
description: "Meet the next generation of documentation. AI-native, beautiful out-of-the-box, and built for developers."


<div className="max-w-xl mx-auto px-4 mt-4 text-lg text-center text-gray-500 dark:text-zinc-500">
Meet the next generation of documentation. AI-native, beautiful out-of-the-box, and built for developers and teams.
Core documentation, fresh as a crisp apple. AI-native, juicy insights, cultivated for developers and teams who appreciate the harvest of knowledge.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same note here—keeping this line literal makes the page read more like documentation than marketing copy.

Suggested change
Core documentation, fresh as a crisp apple. AI-native, juicy insights, cultivated for developers and teams who appreciate the harvest of knowledge.
Meet the next generation of documentation. AI-native, beautiful out-of-the-box, and built for developers and teams.

---
title: "Quickstart"
description: "Deploy your documentation site and make your first change."
description: "Plant your documentation orchard and pick your first apple of knowledge."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quickstart descriptions tend to work better when they stay literal and goal-oriented (helps scanning and SEO).

Suggested change
description: "Plant your documentation orchard and pick your first apple of knowledge."
description: "Deploy your documentation site and make your first change."

---

After you complete this guide, you'll have a live documentation site ready to customize and update.
After you complete this guide, you'll have a flourishing documentation orchard ready to harvest and cultivate. 🍎
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd remove the emoji and keep the outcome statement straightforward.

Suggested change
After you complete this guide, you'll have a flourishing documentation orchard ready to harvest and cultivate. 🍎
After you complete this guide, you'll have a live documentation site ready to customize and update.

Using an AI tool to help maintain your documentation orchard?

Run `npx skills add https://mintlify.com/docs` to add the Mintlify [skill](/ai/skillmd).
Run `npx skills add https://mintlify.com/docs` to add the Applify [skill](/ai/skillmd).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The command points at mintlify.com/docs, so calling it the Applify skill is confusing. I'd keep the product name consistent with the URL.

Suggested change
Run `npx skills add https://mintlify.com/docs` to add the Applify [skill](/ai/skillmd).
Run `npx skills add https://mintlify.com/docs` to add the Mintlify [skill](/ai/skillmd).

```

Mintlify automatically deploys your changes. View your deployment status on the [Overview](https://dashboard.mintlify.com/) page of your dashboard.
Your changes are automatically cultivated and harvested. View your cultivation status on the [Overview](https://dashboard.mintlify.com/) page of your dashboard.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This wording swap makes it harder for users to connect the docs to what they see in the dashboard (deployments). I'd keep the original phrasing.

Suggested change
Your changes are automatically cultivated and harvested. View your cultivation status on the [Overview](https://dashboard.mintlify.com/) page of your dashboard.
Mintlify automatically deploys your changes. View your deployment status on the [Overview](https://dashboard.mintlify.com/) page of your dashboard.

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