Instance admins should be able to change the default route all users arrive on, when unauthenticated. This enables uses such as sending users to the login page automatically.
Add a new property in the [app] configuration section that indicates the default landing page. If none set, default to /. Sample values: login, about
After checking the user session in handleViewHome(), check this config value and redirect user accordingly.
| rWF WriteFreely | |||
| rWF584fe4fb93ff Support changing default landing path | |||
| rWFc95ee0abe10b Support changing default landing path | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | matt | T574 Configurable landing route | ||
| Resolved | matt | T651 Allow changing landing route from admin UI |
So let's say I set default landing page to about. Does it means that when visitor lands, he/she will be redirected to /about, or will stay on / but about page will be rendered there?
I was considering to rewrite landing.tmpl in a way that it would show about page content on top and last posts (pretty much /reader) below.
Mastodon by default redirects to /about page from root /.
I think we'd just redirect people to the correct route -- this would allow instance admins to set it to anything they want without modifying the app itself. For example, they could even choose a default blog to land on if they're running a multi-user instance.
Those landing page changes sound interesting.. We should definitely discuss more, especially to balance it with the customization people will be able to do once T565: Edit landing page is finished.
I'll necrobump this and point out that I think @gytisrepecka is talking about something I'm referencing in T576 (a landing page).