Move "Configuration files" doc page out of "Fleet server" section

[noahtalerman]

Problem

The "Configuration files" docs page is the reference documentation for all options available in Fleet YAML. These YAML files power GitOps workflows w/ Fleet.

Unlike the options "Fleet server configuration", users use these YAML files to modify Fleet features like teams, queries, policies, profiles, and more. They don't use them to modify the Fleet server.

So, it's potentially confusing to have "Configuration files" sit under the "Fleet server" section.

Solution

- Remove the metatag for the sections under "Configuration." (We'll bring these back as and when we can prioritize breaking up these pages into more easily navigable pieces.)

[mike-j-thomas]

Thanks, @noahtalerman. The original plan was to put this as its own section under configuration, but that would break the current nav setup unless split into separate pages (but some of the pages would be so tiny it would look strange.) Eric suggests listing it separately under Configuration.

[noahtalerman]

Eric suggests listing it separately under Configuration.

@mike-j-thomas and @eashaw makes sense to me.

With this approach, do we need the "FLEET SERVER" and "AGENT" headers?

I think it's clear enough with just the page titles. "Fleet server configuration" and "Agent configuration"

[mike-j-thomas]

@noahtalerman, I had the same thought. For now, if making this change, it makes sense to remove those headers. The eventual goal is to display the h2s in that nav, under the headers, to make those pages more easily navigable.

[mike-j-thomas]

@eashaw I have updated the description above. This change is approved and is ready for you to action.

[eashaw]

@mike-j-thomas, I don't see the updates you made, did they not get saved?
Private Zenhub Image

[fleet-release]

Shifting docs, like leaves,
Fleet's clarity improves,
Guiding with more ease.