Bump primary ingest tools to top of ingest section

[kilfoyle]

As requested by our ingest PM, it'd be very nice to have the Fleet, Integrations, and Logstash docs appear at the top of the Ingest: Add your data section.

[github-actions]

A documentation preview will be available soon.

Help us out by validating the Buildkite preview and reporting issues here.
Please also be sure to double check all images to ensure they are correct in the preview.

• 🔨 Buildkite builds
• 📚 HTML diff: Buildkite - Jenkins
• 📙 Preview: Buildkite - Jenkins
• 🧪 Buildkite vs Jenkins diff

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[bmorelli25]

Hmm. I'm not sure how I feel about this one. I think every PM could make a case for their products being at the top of the list 😄. That's not to say Fleet and Logstash shouldn't be at the top—maybe they should.

Also, IMO the Integrations Developer Guide shouldn't be moved to the top. If anything, I think it should be deprecated as it's not maintained by the dev team. I thought we had an issue somewhere to deprecate it, but I can't seem to find it in the moment.

[KOTungseth]

Over the last year, the Ingest docs with the most traffic include:

• Logstash Reference
• Filebeat Reference
• Fleet
• Metricbeat Reference
• Packetbeat Reference
• Beats Platform
• Winlogbeat Reference
• Heartbeat Reference

A small percent of users visited the Integrations Developer Guide. Looking at the Elastic Docs content inventory, it looks like this entire guide is going to be archived.

We can move the Logstash Reference and Fleet and Elastic Agent Guide to the top of the list, but the Integrations Developer Guide should be deprioritized.

[kilfoyle]

Thanks a lot @bmorelli25 and @KOTungseth!

Do you think this order makes sense? That's in my latest commit, but whatever you think we should change please let me know.

• Fleet and Elastic Agent Guide
• Logstash Reference
• Logstash Versioned Plugin Reference
• Amazon Kinesis Data Firehose Ingest Guide
• Elastic Ingest Reference Architectures
• Elastic Logging Plugin for Docker
• Elastic Serverless Forwarder Guide
• Integrations Developer Guide
• Auditbeat Reference
• Beats Developer Guide
• Beats Platform Reference
• Filebeat Reference
• Heartbeat Reference
• Metricbeat Reference
• Packetbeat Reference
• Winlogbeat Reference

[KOTungseth]

LGTM. Thanks David!

[bmorelli25]

🦕