You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When watching a demo of an application that uses cloudscribe folder-name multi-tenancy, I got to thinking again about how a user finds their way into their own ‘tenant’.
Note that many users will not actually bookmark their tenant address, but they will know they are using “Insights” or “FlyMapper” (or whatever) which they will be able to google.
So the root landing page of the site really has to make it easy for a user to get to their area.
In one such site we made the root site landing page a kind of ‘menu’ with a tile for each customer, for a user to click on to get to their tenant. See https://local-heritage-list.org.uk/
This is completely hand-carved 'content' – which is fine for smallish numbers and low rate of change.
This could be made much easier. with a simple page template component for this: a ‘Tenant site menu page template’.
This could have top content, bottom content, and in the middle it would render the ‘list’ of tenants, making use of the tenant site settings to provide: name, URL, logo image, and potentially other properties such as 'Header Content'.
The actual rendering could then be tiles, like on LHLP, or a simple list, or whatever. There could be some choices in the template.
The text was updated successfully, but these errors were encountered:
When watching a demo of an application that uses cloudscribe folder-name multi-tenancy, I got to thinking again about how a user finds their way into their own ‘tenant’.
Note that many users will not actually bookmark their tenant address, but they will know they are using “Insights” or “FlyMapper” (or whatever) which they will be able to google.
So the root landing page of the site really has to make it easy for a user to get to their area.
In one such site we made the root site landing page a kind of ‘menu’ with a tile for each customer, for a user to click on to get to their tenant. See https://local-heritage-list.org.uk/
This is completely hand-carved 'content' – which is fine for smallish numbers and low rate of change.
This could be made much easier. with a simple page template component for this: a ‘Tenant site menu page template’.
This could have top content, bottom content, and in the middle it would render the ‘list’ of tenants, making use of the tenant site settings to provide: name, URL, logo image, and potentially other properties such as 'Header Content'.
The actual rendering could then be tiles, like on LHLP, or a simple list, or whatever. There could be some choices in the template.
The text was updated successfully, but these errors were encountered: