docs: Managing Flags section

[guiwrite]

Thanks for submitting a PR! Please check the boxes below:

• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

• Core management
• Tagging
• Comparison
• Schedule flags
• Feature Health Metrics
• Rollout by attribute
• Rollout by percentage

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Aug 29, 2025 0:49am

[vercel]

@guiwrite is attempting to deploy a commit to the Flagsmith Team on Vercel.

A member of the Team first needs to authorize it.

[matthewelwell]

@guiwrite here are the broken links preventing the docs build:

Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
  Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.
  
  Exhaustive list of all broken links found:
  - Broken link on source page path = /managing-flags/manage-flags/scheduled-flags:
     -> linking to ../feature-health-metrics.md (resolved as: /managing-flags/feature-health-metrics.md)
  
      at throwError (/vercel/path0/docs/node_modules/@docusaurus/logger/lib/logger.js:80:11)
      at reportBrokenLinks (/vercel/path0/docs/node_modules/@docusaurus/core/lib/server/brokenLinks.js:250:47)
      at handleBrokenLinks (/vercel/path0/docs/node_modules/@docusaurus/core/lib/server/brokenLinks.js:282:5)
      at executeBrokenLinksCheck (/vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:91:47)
      at /vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:70:67
      at Object.async (/vercel/path0/docs/node_modules/@docusaurus/logger/lib/perfLogger.js:42:47)
      at buildLocale (/vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:70:31)
      at async runBuildLocaleTask (/vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:93:5)
      at async /vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:74:13
      at async tryToBuildLocale (/vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:70:9)
      at async /vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9
      at async mapAsyncSequential (/vercel/path0/docs/node_modules/@docusaurus/utils/lib/jsUtils.js:21:24)
      at async Command.build (/vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:33:5)
      at async Promise.all (index 0)
      at async runCLI (/vercel/path0/docs/node_modules/@docusaurus/core/lib/commands/cli.js:56:5)
      at async file:///vercel/path0/docs/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3

[robertnorrie]

On this one - I'm not sure the subheader "core management" makes sense here.
Maybe "Basic flag management" as that is consistent with the "basic features" header further down.

[robertnorrie]

Actually, I wonder if the structure would make more sense as:

• Managing Flags
  -- Manage Flags (instead of Core Management)
  -- Tagging
  -- Scheduled Flags
  -- Feature Health Metrics
  -- Rollout

Additionally, we probably need to be consistent when using the term flags vs features. We use Features in the UI, so I think we need to be consistent and use that over flags everywhere, or if it's clearer use "feature flags" everywhere. @matthewelwell what are your thoughts on this?