This guide walks you through the decisions you’ll make as you plan a multi-site JUNO platform.
...
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
An example public site. You can preview pages but must log in once you try to open content.
Private access: Or keep your site privateso that users only see the welcome page before logging in.
...
An example private site. You only see the welcome page before logging in.
Content-specific restrictions: In addition to the above site-wide access options, you can restrict individual pieces of content with an access level tag. It doesn’t matter if the site is public or private. Even if someone is logged in, they can only open the content if they have the correct access level. For example, within an event site, you might create multiple ticket levels. If a user has access to a site, but not that content, they are alerted that they don’t have access and are redirected to the site home pageand can be prompted to upgrade.
For a multi-site platform, public and private sites can be combined in creative ways. In the following examples, imagine that you have a platform with two sites: a 365 site and a single-use site called “Event.”
...