Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple dynamic index files #121

Open
EECOLOR opened this issue Jun 14, 2018 · 2 comments
Open

Allow multiple dynamic index files #121

EECOLOR opened this issue Jun 14, 2018 · 2 comments

Comments

@EECOLOR
Copy link
Member

EECOLOR commented Jun 14, 2018

In some cases you want to serve /index.html and /otherApp/index.html as two separate applications. We currently only support a routable application at the root of the site. This means that we need to load all assets of the whole site even if it's likely a user won't be accessing all parts of the site that use them.

It would be nice if we would walk back from the currently location to the root looking for index.html.js files. As soon as we find one we use it for routing.

The most use case I was first thinking of was having an admin area at /admin. Admins however have a login and thus don't need server-side rendering. So this would not be a valid use case.

I think we only need to solve this once we have a solid use case.

@EECOLOR
Copy link
Member Author

EECOLOR commented Nov 25, 2019

No use case has presented itself. I think that, once we have a use case, we might want to investigate switching to something like next-js.

Closing this issue for now.

@EECOLOR EECOLOR closed this as completed Nov 25, 2019
@EECOLOR EECOLOR reopened this May 6, 2020
@EECOLOR
Copy link
Member Author

EECOLOR commented May 6, 2020

One of the use cases is the Sanity studio in a sub directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant