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

Reserved Page Instances for 404 & 500 Error Pages #9

Open
jonwinton opened this issue Feb 25, 2019 · 2 comments
Open

Reserved Page Instances for 404 & 500 Error Pages #9

jonwinton opened this issue Feb 25, 2019 · 2 comments

Comments

@jonwinton
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We should provide predictable instances that the platform can direct to for 404 & 5xx errors.

Describe the solution you'd like
To "reserve" specific page instances like /_pages/404 that the platform can redirect to when there's missing content/an error.

Describe alternatives you've considered
Currently users must manage their own instance and solution for these pages, usually pushing logic into the CDN or some other self-written middleware

Additional context
Questions:

  • What's the starting data for these pages? Does the platform ship with it?
  • Do we provide affordances in the Kiln menu for getting to those pages directly since they would be known?
@ncbooth
Copy link

ncbooth commented Feb 25, 2019

I think it would be better if clay render the error page in place rather than redirect.

It would be useful for Kiln to have a feature were we could link to arbitrary pages from the menu directly. This would be useful for pretty much any page you would want to administer but wouldn't necessarily go to via navigation alone, such as error pages, as well as utility pages (say managing redirects or tags), and dynamic pages.

@jonwinton
Copy link
Contributor Author

Oh that's an interesting thought on the page management, we'll look at this as the feature pushes forward a little.

And agree with rendering in place 👍

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

2 participants