🕵️‍♂️ How can we maximize API page discoverability?

[JFWooten4]

I've been working to move some critical core information from the RPC API's getLedgerEntries page in 9de3478. Ideally, this will let us achieve our goals to feature things that are cheaper to deploy than Horizon in #1529.

This has meant a renewed focus on core ledger data, which never did get good specific documentation. But in moving around the information to actual reference pages, I noticed that @overcat and @Shaptic put a lot of really awesome documentation into the spec page.

The challenge is that it's sort of hard to find this page, as it doesn't even show up in the native site search functionality. It's weird because it does show up in Google, but I don't want people to need to leave the site to find things.

I suspect the culprit could be something about how it has hidden or minimal metadata:

stellar-docs/docs/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx

Lines 1 to 4 in c95f060

	---
	hide_title: true
	description: Returns ledger entries
	---

I know there's been a lot of SEO work this last year; what's our approach on endpoint discoverability?¹

Footnotes

1. I think it's important because of what I've found in migrating the DEX docs away from Horizon objects, which is a joy. These pages were some of the only places documenting data semantics off GitHub, which made them a useful reference for my own explanations. ↩