A single Drupal instance with many front-ends (Next.Js applications)

[nikolabintev]

Package

next (Drupal module)

Describe the feature request

Hi team,

First of all, thank you for the effort you've put to deliver such a module!

We are experimenting with Drupal and Next.js to deliver a headless solution that tackles most of the cases related to content editing. In the scenario where we have a single Drupal instance for many front-ends (Next.js apps), we have the "Site" field which allows us to distinguish content between sites when it comes to fieldable entities like nodes, terms, paragraphs, etc. However, if it comes to non-fieldable entities like url aliases, redirect entities, etc., there's no optimal solution that solves such a problem.

For example, imagine that I have two websites, both of which should have an "about us" page. Normally, I'd expect that I can found that page under "/about-us" URL, but currently this is not possible because Drupal does not allows us to have duplicate URL aliases which is absolutely fine if we are running in the context of a single website.

The same issue would appear, if for some reason, we need to expose configuration objects to the front ends. There's no way to distinguish between configurations across different websites.

May team and I have been working on a similar solution for a client, where we have managed to address those issues. My question is are you interested in extend the module in this direction? If so, we can start exploring the options, so we can propose a proper solution?

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Add any other context about the problem here.