Restructure service providers pages

Open
#2,156 2 comments 0 reactions 1 assignee View on GitHub

@mollykarcher is already working on this.

Since Jan 23, 2026.

Assessment

This issue has not been assessed yet.

Description

documentation

Ref #2153

After #2055 we now have a few pages for service providers: API, Analytics, Indexers and Oracles.

I had a hard time to find some providers as I was expected them to be in indexers and they ended up being in Analytics. E.g. SonarX, whose description states that it is an indexer. I was also looking for Quasar and saw that there was a specific page for Galexie provider. Same goes with Dune which I also thought would be listed as an indexer.

After discussing with @chadoh and others, we all seem to have varying definitions on what is an indexer, a data provider, something else.

Hence, I would suggest to flatten and simplify the structure to help users find their way. Have a single Analytics-Indexing section (name to be defined) and have a single provider page for it, with sections if we want to separate concerns.

Reviewing this, I also found some other services which could be added: Zettablock (I read there is a SDF partnership even?), Bitwave (had a SCF), BlockEden, 3xpl, Ginco, Bitquery.

Some products seem to also gain capabilities. e.g. Quicknode shows on their page that indexing like features might be coming soon. Same with validationcloud with their new Mavrik Data x Ai.

Dominant language
MDX
Stars
138
Forks
313
Avg merge
3d 11h
Merged PRs (30d)
44

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-docs

All issues in stellar/stellar-docs

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.