Technical limitation of EDS for blog routing with Content Fragments

[mancillaign]

I’ve been testing blog implementations with Edge Delivery Services using Content Fragments exposed through GraphQL.

While pagination and querying work fine (limit/offset on the API side), I’ve hit a wall with routing.

Here’s the challenge:

• GraphQL gives me the Content Fragment path, not the page URL where that blog post should live.

• If I want a clean route structure like /blog/my-first-post, I end up needing to create a custom backend service that maps CFs to routes.

This feels like a big technical limitation: the API is great for retrieving content, but for something as common as blog routing, it doesn’t provide the final URL.

Has anyone solved this elegantly? Did you:

• Build your own routing layer?

• Use metadata inside the CFs to generate URLs?

• Or is there an Adobe-recommended way to bridge this gap?

[arunpatidar]

Hi @mancillaign 

For custom content, EDS provides to override,You can check https://ericvangeem.dev/blog/edge-delivery-byom-content-overlay 

[RajRoy]

Hi @mancillaign can you explain a bit how you're trying to hit the GraphQL API ? Like do you have written some custom JS